# Unvalidated Components Three components are part of the kernel's design vision but sit **outside** the [[Frozen Evidence Baseline]] and are explicitly *not* claimed as proven: - **ACE** — anomaly correlation engine - **MCC** — multi-channel correlation - **Command Validation** — verifying commands against expected control intent > [!failure] Why naming the gaps is a feature > The [[Evidence Hierarchy]] says the reddest flag is when the claimed key differentiator is the least-evidenced capability. By drawing a hard line around what is PROVEN versus aspirational, the program avoids that trap — it lets a technical reviewer trust the proven core *because* the boundary is honest. These components are the natural agenda for the next [[Maturity Levels|maturity step]] and [[Deployment Path|pilot phases]]: a Level 3 → Level 4 transition is largely the work of moving ACE / MCC / Command Validation from design into validated, frozen evidence. --- Related: [[Integrity Kernel MOC]] · [[Frozen Evidence Baseline]] · [[Maturity Levels]] · [[Deployment Path]] · [[Evidence Hierarchy]]