FIX7 P0 Birth-Blueprint — Implementation Planning Packet (PAPER-ONLY)

• Host: T1 / Claude Code / MYTHOS · Date: 2026-06-11
• Final status: FIX7_P0_IMPLEMENTATION_PLANNING_PACKET_READY
• Authority of this packet: PLANNING_NON_AUTHORITY. This packet authorizes nothing. It plans a future implementation; it does not execute one.
• Production mutation: NO · Implementation execution: NO · REAL_RUN / QT001 / permit / activation / repoint / cutover: NO · Codex consulted: NO · Owner approval requested mid-run: NO.

What this packet is

The Codex authority seal N7 → N8 → P7 is authored and verified (packet tree 3890cd34…a234). P7 pins canonicalizer rev3 (49c386a9…b734d0, 38756 bytes) and the Packet V3 tree (b95df0a5…ca6d) as the authoritative FIX7 P0 birth-blueprint identity. The owner gave OPT-3 (authorize seal + post-seal implementation planning only). This packet is that planning step — and nothing more.

P7 alone does not authorize implementation. Implementation execution and all production mutation remain blocked. A separate owner OPT-4 (or explicit equivalent) is required before any execution macro may run, and REAL_RUN / QT001 / cutover each need their own separate authorization beyond that.

How to verify (executable, paper-only)

bash RERUN.sh          # verifies HASH_MANIFEST + packet_tree, then runs the gates
# or just the gates:
python3 planning_packet_validator.py   # -> PLANNING_VALIDATOR_RESULT: PASS, exit 0
python3 bad_input_probes.py            # -> 15/15 fail-closed; any_fail_open=False, exit 0

The validator passes only when every planning gate holds and the packet still declares execution + production blocked. The probes inject one defect at a time (missing/мismatched P7, execution-claimed-now, production-allowed-now, fabricated rollback proof, missing precondition evidence, un-inventoried surface, dry-run command without rollback, unclassified registry mutation, fabricated owner approval, default ≠ HOLD, execution_ready overclaim, …) and prove each fails closed.

Contents

file	role
seal-consumption.json	the official N7/N8/P7/N6 chain consumed read-only; what it does / does not authorize
mutation-inventory.json	10 candidate target surfaces; every one allowed_now=false; forbidden surfaces inventoried
precondition-checklist.json	12 preconditions for a future execution macro; execution_ready=false
dryrun-design.json	a future staging/temp dry-run lane (no production); every step read-only or has a rollback ref
rollback-recovery-design.json	rollback design; rollback_proof_status=NOT_YET_PROVEN (no execution has run)
evidence-audit-plan.json	the evidence a future execution macro must produce
owner-execution-decision-template.json	options for the NEXT owner/operator decision; default HOLD, selected_option=null, UNSIGNED
planning_packet_validator.py	fail-closed validator (exit 0 pass / 1 gate-fail / 2 missing file)
bad_input_probes.py	15 adversarial probes + positive controls
commands.sh / RERUN.sh / exit_codes.json / HASH_MANIFEST.txt / packet_tree.sha256 / manifest.json	run + integrity harness

The decision in front of you

Default is HOLD. If you want to proceed, the options (cumulative) are: AUTHORIZE_DRYRUN_ONLY → AUTHORIZE_IMPLEMENTATION_EXECUTION_NO_PRODUCTION → AUTHORIZE_PRODUCTION_CUTOVER_LATER_SEPARATELY. See owner-execution-decision-template.json. T1 makes no recommendation and will not self-authorize.

Standing blockers (owner/operator only)

• FIX7-P0-PLAN-EXEC-AUTH-1 — owner OPT-4 (execution) not given (only OPT-3 planning).
• FIX7-P0-PLAN-SURFACE-1 — production birth surface (PG/Directus/registry-row/birth pipeline) UNKNOWN; must be scoped by owner/operator, not invented.
• FIX7-P0-PLAN-REALRUN-1 / …-SEPARATE-AUTH-1 — REAL_RUN / QT001 / permit / activation / repoint / cutover each need separate authorization.
• FIX7-P0-PLAN-ROLLBACK-PROOF-1 / …-RECHECK-1 / …-FIRSTSTEP-1 — produced only when a future dry-run/execution actually runs.