Checkpoint - Codex FIX7 Blueprint Recheck After T1 Patch

Date: 2026-06-08 Mode: READ-ONLY production; blueprint not edited.

Final status

FIX7_REFACTOR_BLUEPRINT_CODEX_RECHECK_FAIL_HARDCODE_OR_PG_NATIVE_GAP

Accepted improvements

• PRE/POST guard concept.
• Five-disposition concept and stub-all contradiction removal.
• ACL snapshot completeness additions.
• Pinned writer-gateway identity.
• operator_authorization versus blocked permit terminology.

Remaining blockers

1. S15 REVOKE cannot remove implicit effective EXECUTE from owner directus; S16 ownership transfer is too late.
2. Legacy set/classification/#27 bindings are authored after S09/S12 seal.
3. Added #20 columns/hash behavior conflict with approved byte-level DDL and PKG-A exact-match rule.
4. G-NOMIXED-AUTHORITY conflicts with S14 ACTIVE manifest while legacy remains executable.
5. live-relevant is not a closed PG-native denominator.
6. Source hashes are not restorable source artifacts.
7. Authoritative hash roll-up and operator authorization lack complete PG-native contracts.
8. Stale operator permit wording remains in doc 08.

Boundaries

Official FIX7 design remains approved. Blueprint and implementation-authoring planning are not approved. Implementation, Stage 2.6B, qt001_backfill_permit, REAL_RUN, QT001 apply, activation, repoint, and ACL cutover remain BLOCKED.

Report: knowledge/dev/reports/architecture/codex-fix7-blueprint-recheck-after-t1-patch-2026-06-08/

Next: T1 correction pass, then Codex recheck.