KB-3C8D rev 2

FIX7 Implementation Staging Plan - Corrected

1 min read Revision 2
QT001FIX7stagingT1operator-gated

FIX7 Implementation Staging Plan - Corrected

FIX7a creates isolated constrained manifests/generic engines/control epoch and leaves authority_cutover_complete=false; no repoint or active seal. T1 may author/test; live deployment requires operator-gated approved pipeline.

FIX7b owner/ACL cutover requires exact authority scope, independent activation quorum, rollback snapshots, secure functions, no-go tests, and current apply block. Execution is through Level-B DOT/migration pipeline, never manual SQL.

FIX7c deploys controlled evidence/signoff, generic policy/capability/hash engines, analyzer evidence, zero direct runtime target DML, acceptance-controlled gateway, scheduled scanner, and epoch serialization. Stage 2.6B remains blocked pending independent audit and real scale evidence.

Back to Knowledge Hub knowledge/dev/reports/architecture/codex-fix7-control-plane-immutability-design-plan-2026-06-07/09-implementation-staging-plan.md