KB-19DF

Codex FIX7 Legacy Disposition Amendment - Readme First

2 min read Revision 1
fix7codexdesign-amendmentoption-beta2026-06-08

00 - Readme First

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

Final status

FIX7_LEGACY_DISPOSITION_DESIGN_AMENDMENT_APPROVED_OPTION_BETA

Codex confirms that the approved FIX7 design has no typed home for the proposed five-value legacy-disposition contract. T1 correctly stopped rather than introducing DDL drift or a computed/open-text classifier.

Option Beta is approved with a stricter owner ruling: the standalone disposition enum and every disposition-driven branch are removed from the load-bearing authority path. relkind/prokind may select only the PostgreSQL syntax adapter required to reach one uniform end-state; they must never select policy or different operational outcomes. DO_NOT_TOUCH is not a disposition and is never an automatic exclusion from U_legacy.

Every U_legacy member receives the same authority result: owner isolated to the approved NOLOGIN owner, body unchanged, and actual effective privileges exactly equal the closed-world sealed #21 desired privilege set. Differences such as read-only access exist only because exact #21 rows grant them, not because a label or classifier chooses them.

Implementation, Stage 2.6B, QT001 apply, permit, REAL_RUN, activation, repoint, and cutover remain blocked. T1 must patch the blueprint against this amendment, then Codex recheck 3 is required.

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