11 - Direct Blueprint Revisions Applied (recheck-6)

All edits were patch_document / upload_document against the live blueprint KB documents. No production DB object was created/altered/owned/granted/revoked/executed. Read-back results in doc 12 + the checkpoint.

ACTIVE blueprint members patched (load-bearing)

doc	rev before → after	what changed
00-readme-first	18 → 31	FIX7-CANON-V1 Field rejection policy (blocker A); Active-scope/fence/section extractor (B); Record encoding schema + Closed key-classification schema (C); Seal hash dependency graph (acyclic) (D); detached seal anchor contract — acyclic, no self-hash + limitation (E); per-aggregate manifest/seal bullets corrected; envelope YAML rewritten (cycle removed: codex_checkpoint_content_sha256 → diagnostic _excluding_seal; section tokens; SEAL_AT_CODEX_RECHECK_6→_7; parent = recheck-6 checkpoint; recheck-6 notes); fail-closed rule + statuses + guards; self-verdict status → …RECHECK_6_READY_FOR_CODEX_RECHECK_7, guards 54→58
06-test-guard-blueprint	58 → 64	recheck-6 header note; +G-CANONICAL-FIELD-REJECT, +G-ACTIVE-SCOPE-EXTRACTOR, +G-RECORD-ENCODING-CLOSED, +G-SEAL-HASH-GRAPH-ACYCLIC (54→58 rows); guard count bumped in all spots; guard-quality rule 11
07-implementation-package-split	47 → 51	recheck-6 header note; PKG-A preconditions reference the 4 new guards + acyclic anchor; sequencing bullet "Byte-exact, executable, acyclic content-addressing (recheck-6)"; PKG-I "all 54" → "all 58"
12-final-verdict	43 → 54	top status → …RECHECK_6_READY_FOR_CODEX_RECHECK_7; status-history bumped; new "Codex recheck-6 byte-exact-canonicalization patch pass" section (blocker table A–F); asks heading → recheck 7 + asks 15–19; stale "47" → 58; ask 8 checkpoint → recheck-7; blocking status → recheck-6 patched/ready for recheck 7; guard counts 54→58; authority-boundary comment lists the recheck-6 pass

Checkpoints

doc	action
checkpoint-t1-fix7-blueprint-patch-after-codex-recheck-6-byte-exact-envelope-2026-06-09.md	created (this pass's checkpoint)
checkpoint-t1-fix7-existing-system-refactor-execution-blueprint-2026-06-08.md	updated (status, recheck-6 section, guards 54→58)

This report directory (rationale, NON-member)

t1-fix7-blueprint-patch-after-codex-recheck-6-byte-exact-envelope-2026-06-09/00..12 (13 docs).

Editing technique notes (for the next pass)

• Doc 00's envelope YAML has repeated identical lines (SEAL_AT_CODEX_RECHECK_6, active_section_id_or_range: whole, per-doc hash lines) → per-line patches are impossible. Technique: fetch the doc, extract the exact fenced block via python, transform with asserted .replace() (each replace count checked), print old+new raw, transcribe in three contiguous internally-unique chunks. Used here without a failed match.
• Always bump SEAL_AT_CODEX_RECHECK_n → n+1, parent_recheck_checkpoint_id to the just-completed Codex checkpoint, and STAGED_PENDING_CODEX_RECHECK_n together; the status string moves …RECHECK_(n-1)_READY_FOR_CODEX_RECHECK_n → …RECHECK_n_READY_FOR_CODEX_RECHECK_(n+1).