00 - Readme First

Date: 2026-06-09 Author: T1 (production Agent for Agent Data) Macro: PROGRAM_PATCH_T1_FIX7_BLUEPRINT_AFTER_CODEX_RECHECK_4_ACTIVE_AUTHORITY_HASH_ENVELOPE Mode: READ-ONLY production. Blueprint KB-doc direct-revision. NO production mutation.

Final status

FIX7_REFACTOR_BLUEPRINT_T1_PATCHED_AFTER_CODEX_RECHECK_4_READY_FOR_CODEX_RECHECK_5

What this is

A narrow blueprint repair after Codex recheck 4 (codex-fix7-blueprint-recheck-4-final-before-authoring-2026-06-09/, status FIX7_REFACTOR_BLUEPRINT_CODEX_RECHECK_4_NEEDS_T1_FIX). Codex accepted the recheck-3 work (object-only legacy universe, principal separation, entry-vector separation, uniform-end-state scope, PG-native-final, 27/11/14/7 + all execution boundaries) and left one blocker class: the ACTIVE_AUTHORITY corpus was classified only by mutable KB markers/registry/fences and was not pinned to the exact Codex-reviewed revisions/content hashes — a mutable authoring-authority denominator (disguised hardcode). The other three NEEDS_FIX verdicts (no-disposition guard, hardcode- final, authoring-planning) are all downstream of that one root.

The fix — an immutable, content-addressed approval envelope

ACTIVE_AUTHORITY_APPROVAL_ENVELOPE (doc 00 §Active-authority approval envelope): a machine-readable fenced YAML block pinning every ACTIVE document/section + its KB revision + a normalized SHA-256, plus marker-fence / registry / guard-set / membership / manifest hashes, anchored to the Codex recheck checkpoint. Sealed at the Codex recheck. Any later change to content, marker, fence, registry, active section, or guard set → ACTIVE_AUTHORITY_ENVELOPE_MISMATCH → blocks implementation-authoring planning until a fresh Codex recheck; the correct next step on mismatch is never "continue authoring."

• The corpus-membership hash is computed now and stable: 916d6e11027ff466ffd4f0ae0f66b15c314fb89601b70ecdb7261ce463c03b87 (over the 10 ACTIVE doc_ids).
• Per-document content hashes seal at recheck-5: a hash of the approved corpus can only be computed at the approval event; T1 pre-writing "approved" hashes would itself be self-fabricated authority — the anti-pattern this whole chain polices. So Codex computes + seals them at recheck-5 PASS and records the sealed envelope in the recheck-5 checkpoint (the immutable anchor).

Four guards ADDED (47 → 51): G-ACTIVE-AUTHORITY-APPROVAL-ENVELOPE, G-ACTIVE-AUTHORITY-HASH-MATCH, G-ACTIVE-AUTHORITY-REVISION-MATCH, G-ACTIVE-AUTHORITY-CHANGE-FAIL-CLOSED. G-ACTIVE-AUTHORITY-SCOPE, G-NO-SUPERSEDED-CONSUMPTION, G-LEGACY-NO-DISPOSITION-AUTHORITY re-bound to the sealed envelope. Guard-quality rule 9 added.

Non-runtime (Codex's hard constraint)

The envelope is a construction-document content-address that pins the blueprint docs being authored from. It is NOT a runtime authority surface, readiness gate, #20 column, catalog family, or a top-level FIX7 runtime hash contract (H01..H07 stay 7). 27/11/14/7 unchanged.

Document map

Doc	Content
00	This readme
01	Codex recheck-4 failure matrix
02	The ACTIVE_AUTHORITY_APPROVAL_ENVELOPE
03	Revision/hash fail-closed guards
04	No-disposition guard re-bound to the envelope
05	No-superseded-consumption re-bound to the envelope
06	Adversarial self-audit (11 attack scenarios)
07	Hardcode / PG-native self-review
08	Cross-layer boundary self-review
09	Direct blueprint revisions applied
10	Final verdict + self-check

Boundaries (unchanged)

NOT implementation, Stage 2.6B, permit, REAL_RUN, QT001 apply, activation, repoint, or owner/ACL cutover — all remain BLOCKED. Production READ-ONLY throughout; the only writes were blueprint-doc revisions, this report, and the checkpoints. Option Beta, the set separation, STUB/body removal, DO_NOT_TOUCH removal, 27/11/14/7, PG-native-final, and cross-layer boundaries are not reopened. Next is Codex recheck 5 only (which seals the envelope).