09 - Direct Blueprint Revisions Applied

All revisions applied directly to the blueprint KB documents under knowledge/dev/reports/architecture/t1-fix7-existing-system-refactor-execution-blueprint-2026-06-08/ via patch_document (targeted, section-level; unchanged regions byte-identical). Production READ-ONLY; no SQL applied.

blueprint doc	rev	what changed
00 readme-first	6 → 10	recheck-4 note on the §Active-authority boundary (markers are necessary but not sufficient; pinned by the envelope); registry doc-06 count 47 → 51; new §Active-authority approval envelope section (prose + seal-timing + normalization spec + the fenced YAML envelope in ENVELOPE:EXCLUDE sentinels + fail-closed rule); self-verdict status → recheck-4-patched / recheck-5-ready, 51 guards
06 test/guard	38 → 49	recheck-4 header note; +4 guard rows (G-ACTIVE-AUTHORITY-APPROVAL-ENVELOPE, -HASH-MATCH, -REVISION-MATCH, -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; total 47 → 51; "non-runtime" note; +recheck-4 negative tests
07 package split	40 → 43	recheck-4 header note (packages consume only the envelope-pinned ACTIVE corpus); sequencing bullet (content-addressed authoring authority; drift → STOP → Codex recheck); PKG-A precondition gated on a SEALED, verified envelope
12 final verdict	29 → 36	DOC_STATUS note + Verdict → ..._AFTER_CODEX_RECHECK_4_READY_FOR_CODEX_RECHECK_5; status-history tail; new Codex recheck-4 approval-envelope patch pass section + "why recheck-5" reasoning; explicit asks → recheck 5 (+ask 8: seal the envelope); track-summary + blocking-status guard count 47 → 51; next = recheck 5
checkpoint (blueprint)	17 → 21	Final status → recheck-4-patched / recheck-5-ready; recheck-4 approval-envelope patch-pass section (with the membership hash + seal-timing + 10-point self-audit); Next → recheck 5 (seals the envelope)

ACTIVE corpus revisions at end of this pass (informational; Codex re-pins at recheck-5 seal)

00 = self-host (exclude-region hash) · 01 = 6 · 02 = 33 · 03 = 6 · 04 = 39 · 05 = 24 · 06 = 49 · 07 = 43 · 08 = 17 · 12 = 36. Corpus-membership hash (stable, computed now) = 916d6e11027ff466ffd4f0ae0f66b15c314fb89601b70ecdb7261ce463c03b87.

Edit-method note

patch_document (exact single-occurrence replace) throughout so the large unchanged majority of each doc stayed byte-identical. Same-doc patches applied sequentially (read-modify-write); the SHA-256 demonstrations (shasum -a 256 rehearsal + membership) were computed via Bash on the local shell, not applied to production. No update_document full-rewrites.