KB-4E64

Checkpoint - Codex FIX7 Legacy Disposition Design Amendment

2 min read Revision 1
fix7codexcheckpointdesign-amendmentoption-beta

Checkpoint - Codex FIX7 Legacy Disposition Design Amendment

Date: 2026-06-08 Mode: READ-ONLY production; KB design documents only. Final status: FIX7_LEGACY_DISPOSITION_DESIGN_AMENDMENT_APPROVED_OPTION_BETA

Checks: A DESIGN_AMENDMENT_REQUIRED_CONFIRMED; Alpha OPTION_ALPHA_REJECTED_WITH_REASON; Beta OPTION_BETA_ACCEPTED; hardcode ZERO_HARDCODE_ACCEPTED_FOR_CHOSEN_OPTION; PG PG_NATIVE_DRIVEN_ACCEPTED_FOR_CHOSEN_OPTION; boundary BOUNDARIES_CONFIRMED.

Owner ruling: remove the five-value disposition model and all disposition-driven branches. Do not replace it with relkind/prokind policy. Exact U_legacy comes from sealed #20 roots plus #11 closure. Every member converges to one uniform state: approved unreachable owner, unchanged definition/body, and effective privileges exactly equal complete sealed #21 rows. DO_NOT_TOUCH is descriptive only and never an automatic authority exclusion; collisions fail closed.

Exactly 27 authority surfaces, 11 runtime-evidence non-authority surfaces, 14 readiness gates, and 7 top-level hash contracts remain unchanged. T1 must patch blueprint and submit Codex recheck 3. Implementation, Stage 2.6B, permit, REAL_RUN, QT001 apply, activation, repoint, and cutover remain BLOCKED.

Report: knowledge/dev/reports/architecture/codex-fix7-legacy-disposition-design-amendment-2026-06-08/

Back to Knowledge Hub knowledge/dev/reports/architecture/checkpoint-codex-fix7-legacy-disposition-design-amendment-2026-06-08.md