# Deployment Path The kernel is designed to enter a live facility along a deliberately de-risked path, never as a day-one controller: > [!abstract] Three stages > **Replay → Advisory → Enforcement** > 1. **Replay** — run the kernel on recorded CSV logs; prove [[Deterministic Detection|reproducible]] detection with zero operational risk. > 2. **Advisory** — run live alongside the plant, surfacing trust state to operators but gating nothing. > 3. **Enforcement** — the [[Fail-Closed Trust Gate]] is allowed to actually block execution. The pilot maps to this as phases **1A / 1B / 1C** (CSV-replay led), so the first commercial engagement carries near-zero process risk — exactly the structure described in [[Renacore/Pilot Structure and KPIs]]. This staged path is what makes the kernel sellable into [[The OT Intelligence Layer|safety-critical OT]] where [[Switching Cost Design|incumbents are entrenched]]: you earn enforcement rights by first proving the system on the customer's own historical data. It is also the bridge across [[Maturity Levels]] — each stage retires a category of risk before the next begins. --- Related: [[Integrity Kernel MOC]] · [[Fail-Closed Trust Gate]] · [[Maturity Levels]] · [[Renacore/Pilot Structure and KPIs]] · [[Deterministic Detection]]