00 - Readme First

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

Final status

FIX7_REFACTOR_BLUEPRINT_CODEX_RECHECK_2_FAIL_HARDCODE_OR_PG_NATIVE_GAP

T1 correctly fixed the prior directus-owner and pre-activation mixed-authority defects. The blueprint remains unapproved because the new patch still contains disguised-hardcode/PG-native authority gaps and an incoherent author/seal order.

Decisive remaining blockers

1. U_legacy is not closed independently: its roots still use “legacy/QT001” resources and sealed DO_NOT_TOUCH exclusions without specifying an independently approved PG-native root set. The denominator can remain circular or manually selected.
2. The five-action computed disposition has no exact PG rule/truth table, sealed rule rows, or source-bound classifier contract. Policy can be hidden in CASE/code.
3. operator_authorization fields such as approved_package_sha256 and authorization_scope live inside an external artifact; no sealed PG adapter/contract exposes them as typed decision inputs.
4. #27 does not directly bind an evidence_registry evidence_id. A hash equality does not uniquely identify a restorable artifact.
5. Rollback says clear activated_at, conflicting with active/history immutability and forward-only supersession.
6. PKG-B/C author/rehearse/seal before PKG-D authors #11/#20/#26/#27. Production S12 seal likewise precedes S13 authoring in the normative order.

Implementation and every live action remain blocked.