<!-- DOC_STATUS: ACTIVE_NON_AUTHORITY -->

README FOR CODEX — FIX7 P0 Dry-Run / Execution-Readiness Review Evidence Bundle

• Authority: EVIDENCE_BUNDLE_NON_AUTHORITY. This bundle is an evidence index. It authorizes nothing, mutates no production, and does not claim any Codex PASS or any execution authorization.
• Host: T1 / CLAUDE CODE / MYTHOS · Date: 2026-06-11
• Lane: FIX7_P0_CODEX_REVIEW_EVIDENCE_BUNDLE_REPAIR_MACRO_2026_06_11
• Final status: FIX7_P0_CODEX_REVIEW_EVIDENCE_BUNDLE_READY
• Codex re-asked by this macro: NO. Production mutation: NO. Implementation execution: NO. REAL_RUN/QT001/apply/permit/activation/repoint/cutover: NO.

Why this bundle exists

On 2026-06-11 Codex returned CODEX_FIX7_P0_DRYRUN_EXECUTION_READINESS_REVIEW_BLOCKED. Codex did not reject the dry-run content — it was blocked because the planning packet, the dry-run packet, the TKT Base / T2 governance files, and/or the KB listing were missing from its review workspace or unreachable due to an MCP handshake timeout. The block is an evidence-access failure, not a content failure.

This bundle makes all evidence discoverable from one root, with explicit pointers, hashes, read order, and reconstruction commands, so Codex can re-run the independent execution-readiness review without missing workspace artifacts.

What is in this bundle

file	purpose
README_FOR_CODEX.md	this file
REQUIRED_READ_ORDER.md	exact read order; required vs optional
EVIDENCE_PATH_MAP.json	machine pointer index of every artifact + readability
EXPECTED_HASHES_AND_TREES.json	every packet tree + N7/N8/P7 digest to verify against
RECONSTRUCTION_COMMANDS.md	how to fetch-and-verify from KB
CODEX_BLOCKED_REVIEW_DIAGNOSIS.md	root cause of the block + not_found classification
MISSING_OR_UNREADABLE_PATHS.json	the only not_found paths (blocked-review output)
HASH_MANIFEST.txt	per-file sha256 of this bundle
packet_tree.sha256	sha256(HASH_MANIFEST.txt) for this bundle
manifest.json	this bundle's machine manifest + object reservation
commands.sh	self-check: recompute this bundle's tree + verify file hashes
RERUN.sh	fresh-from-KB reconstruct + re-verify external trees/digests
exit_codes.json	recorded exit codes of commands.sh

What this bundle verified (so Codex does not start cold)

All required review inputs were located in KB on 2026-06-11 and re-verified byte-exact:

• Dry-run + execution-readiness packet (21 files) — tree 02b200e5a3c7a21c2e620b293fbf28ccc81731a983430c3e5a202798c05e94e6 — recompute PASS.
• Implementation-planning packet (16 files) — tree f470d0d019f9af63794ce943a64ea08ff31a17906a7857f4124d0b1e14a0fe8f — recompute PASS.
• Codex authority seal (19 files) — tree 3890cd3467720b3f2c105625e2e1dc627fd2e7fdfb74d9059bad95bece12a234; digests:
  • N7 efb0c5747ae5f56c0e8b5d99c35438a3d6231253570e6ab4d2658ab9e1853d32
  • N8 daa70c39a91a64696fb1a24ca2d3f620d04049583c9047689902ebf26117e1a1
  • P7 9ddb27c35a06ca11ee616e3b0399c705d0d97f5b8f284c12045c396f7c034550 — all match.
• TKT Base pack (30 files) + T2 support files — present and readable.
• All 12 standalone dry-run reports + planning/seal/base checkpoints + current-states — readable.

The only not_found paths are the three Codex blocked-review OUTPUT artifacts — they were never published because the review was blocked. They are recorded honestly and not fabricated.

What this bundle does NOT do / does NOT claim

• Does not alter the dry-run verdict (READY_FOR_OWNER_EXECUTION_REVIEW stands unchanged).
• Does not claim Codex PASS or execution authorization.
• Does not re-ask Codex, fold the registry/index, or touch N7/N8/P7.
• Does not execute implementation or mutate production.

The re-run question (for Codex)

Does the dry-run / execution-readiness packet sustain READY_FOR_OWNER_EXECUTION_REVIEW at TKT Base ceiling L3 with no IU/SEMANTIC/RELEASE overclaim, and with all remaining blockers being owner/operator execution decisions plus production scoping? See REQUIRED_READ_ORDER.md §"Re-run question". This bundle does not pre-judge the answer.