KB-4EBE

FIX7 P0 Codex Review Evidence Bundle — REQUIRED_READ_ORDER

4 min read Revision 1

tool-kiem-thufix7p0codex-review-evidence-bundlenon-authority2026-06-11

Required Read Order — FIX7 P0 Codex Review Evidence Bundle

Authority: EVIDENCE_BUNDLE_NON_AUTHORITY. Read order only; authorizes nothing.
Audience: Codex (independent execution-readiness reviewer). Date: 2026-06-11.

Read top-to-bottom. REQUIRED = needed to re-run the review. OPTIONAL = context. Machine form of this list: EVIDENCE_PATH_MAP.json.

Step 0 — Orient (REQUIRED, this bundle)

README_FOR_CODEX.md — what the block was, what to verify, scope of the re-run.
CODEX_BLOCKED_REVIEW_DIAGNOSIS.md — why the prior review was blocked (access, not content).
EVIDENCE_PATH_MAP.json — the full pointer index (required vs optional).
EXPECTED_HASHES_AND_TREES.json — every tree/digest to verify against.
MISSING_OR_UNREADABLE_PATHS.json — the only not_found paths (blocked-review output only).

Step 1 — Verify integrity before reading content (REQUIRED)

RECONSTRUCTION_COMMANDS.md then run commands.sh (bundle self-check) and, for a full fresh-from-KB reconstruct, RERUN.sh. Confirm the three external packet trees recompute to 02b200e5…, f470d0d0…, 3890cd34… and the N7/N8/P7 digests match.

Step 2 — Authority chain (REQUIRED)

…/codex-fix7-n7-n8-p7-authority-seal-reauthor-with-valid-a5-2026-06-11/00-readme-first.md
.../n7-approval-event.json → .../n8-detached-codex-seal.json → .../p7-authoritative-pin.json
- Confirm: P7 alone does NOT authorize implementation; planning-only boundary holds.

Step 3 — Planning packet (REQUIRED context for the dry-run)

…/checkpoint-fix7-p0-implementation-planning-2026-06-11.md
…/fix7-p0-implementation-planning-packet-2026-06-11/README_FOR_OWNER_AND_OPERATOR.md
.../mutation-inventory.json, .../precondition-checklist.json, .../dryrun-design.json, .../rollback-recovery-design.json, .../evidence-audit-plan.json

Step 4 — Dry-run + execution-readiness packet (REQUIRED — the review target)

…/fix7-p0-dryrun-and-execution-readiness-packet-2026-06-11/README_FOR_OWNER_AND_OPERATOR.md
.../precondition-recheck.json
.../staging-isolation-proof.json
.../dryrun-execution-evidence.json
.../rollback-recovery-proof.json
.../tkt-base-l0-l3-check.json
.../bad-input-probes.json (+ bad_input_probes.py, dryrun_validator.py to re-run)
.../execution-readiness-review.json — the verdict under review (READY_FOR_OWNER_EXECUTION_REVIEW)
.../owner-next-decision-template.json — default HOLD, unsigned
.../governance-objects.json — TKT-OBJ-389..406 reservation

Step 5 — TKT Base normative policy (REQUIRED to judge L0–L3)

…/tkt-base-structural-evidence-governance-pack-2026-06-11/TKT_OUTPUT_LEVEL_POLICY.md
.../TKT_BASE_SCOPE_AND_LIMITS.md and checkers/* as needed
…/support/templates/tkt-base-review-template-for-fix7-dryrun-2026-06-11.md — review scaffold

Step 6 — Cross-check current-states (OPTIONAL)

…/current-state/reports/fix7-p0-dryrun-and-execution-readiness-current-state-2026-06-11.md
…/current-state/reports/fix7-p0-implementation-planning-current-state-2026-06-11.md
…/current-state/reports/tkt-base-structural-evidence-governance-pack-current-state-2026-06-11.md
…/current-state/reports/tkt-parallel-support-preflight-current-state-2026-06-11.md

Re-run question for Codex

Given verified, byte-exact evidence, does the dry-run / execution-readiness packet sustain its own verdict READY_FOR_OWNER_EXECUTION_REVIEW at TKT Base ceiling L3 (no IU/SEMANTIC/RELEASE overclaim), with all remaining blockers being owner/operator execution decisions and production scoping? This bundle does not pre-judge that answer.