KB-2964

Codex FIX7 Recheck 2 - No Mixed Authority

1 min read Revision 1
fix7codexrecheck-2mixed-authority

04 - No-Mixed-Authority Recheck

Verdict

NO_MIXED_AUTHORITY_NEEDS_FIX

Accepted: S14 is SEALED/STAGED, activation moves after neutralization inside PKG-F, and G-NOMIXED checks routed ACTIVE authority rather than mere manifest existence.

Remaining rollback conflict: the blueprint repeatedly says rollback clears activated_at, while its governing invariant says active/history objects are immutable and post-activation rollback creates and activates a prior-payload candidate with a new epoch/quorum/evidence.

Required T1 fix: remove every clear/edit-active path. Define forward-only atomic supersession/activation of a prior-payload candidate, and prove the route switches without an old+new overlap. The guard must test the authoritative route/activation record, not a mutable cleared timestamp.

Back to Knowledge Hub knowledge/dev/reports/architecture/codex-fix7-blueprint-recheck-2-after-owner-semantics-patch-2026-06-08/04-no-mixed-authority-recheck.md