KB-5044

Codex FIX7 Legacy Disposition Amendment - Necessity

2 min read Revision 1
fix7codexdesign-amendmentnecessity

01 - Design Amendment Necessity

Verdict

DESIGN_AMENDMENT_REQUIRED_CONFIRMED

T1 is correct:

  • The approved exactly-27-surface design has no typed sink for a five-value legacy-disposition output.
  • #20 does not approve LEGACY_* authority-object semantics or a disposition column.
  • Silently adding columns, catalog families, or semantic rows would be DDL/contract drift.
  • Computing a disposition in CASE/code, free text, item_payload, or an external artifact would be disguised hardcode and non-PG-native authority.
  • T1 was required to stop because eliminating or adding the disposition model changes design meaning.

Three declarations

  1. Permanent: remove the unnecessary classifier and bind the end-state to existing sealed ownership, closure, and privilege contracts.
  2. Impossible to mistake: guards reject any disposition enum, action branch, manual exclusion, or unsealed desired privilege.
  3. Automatic: generic reconciliation derives scope from sealed #20/#11 and converges ACLs to sealed #21 without a human selecting actions per object.
Back to Knowledge Hub knowledge/dev/reports/architecture/codex-fix7-legacy-disposition-design-amendment-2026-06-08/01-design-amendment-necessity.md