<!-- DOC_STATUS: ACTIVE_NON_AUTHORITY -->

FIX7 P0 — Owner / Operator Pre-Execution Decision Note (2026-06-11)

• Authority: OPTIONS / STATUS ONLY. This note authorizes nothing and chooses nothing.
• Default decision: HOLD. Execution authorization status: NOT_AUTHORIZED. Owner signature: UNSIGNED.

Where things stand

item	status
T1 dry-run / execution-readiness	PASS (FIX7_P0_DRYRUN_AND_EXECUTION_REVIEW_PACKET_READY; packet tree 02b200e5…94e6)
T2 independent review	PASS (T2_FIX7_P0_DRYRUN_EXECUTION_READINESS_REVIEW_PASS)
Codex anti-duplication / lane-boundary audit	PASS per user-provided result (tree e319da46…a751e) — but CODEX_ANTI_DUP_AUDIT_KB_SYNC_NOT_CONFIRMED (artifact not in KB; recorded local-only)
Codex full content review of the dry-run packet	BLOCKED by access, not content (MCP handshake / workspace evidence access; carried blocker FIX7-P0-CODEX-REVIEW-ROUTE-1)
T2-REC-ROLLBACK-HARDENING-1 (rollback validator hardening)	DONE — hardened validator + 7/7 fail-closed probes; valid evidence still passes; no regression (patch packet tree 59788d04…e20e4)
Governance fold (225..441)	FOLD_READY_PACKET_ONLY — contiguous, collision-free, readable; not applied (owner/GPT-only; live lane race)

What is hardened and required going forward

A future execution macro must adopt hardened_dryrun_validator.py as the rollback gate. It rejects any rollback proof where the applied hash equals the before hash (no real mutation), in addition to all original gates. It does not weaken any existing check.

Remaining execution blockers (owner/operator only — unchanged by this macro)

• FIX7-P0-PLAN-EXEC-AUTH-1 — owner OPT-4 execution authorization not given.
• FIX7-P0-PLAN-SURFACE-1 / -SURFACE-2 — production birth surface + CI surface UNKNOWN; must be scoped, not invented.
• FIX7-P0-PLAN-REALRUN-1 — REAL_RUN separate authorization not granted.
• FIX7-P0-PLAN-SEPARATE-AUTH-1 — QT001/apply/permit/activation/repoint/cutover each separate.
• FIX7-P0-DRYRUN-PROD-ROLLBACK-1 — production rollback proof only possible under a separately authorized production phase.
• FIX7-P0-CODEX-REVIEW-ROUTE-1 — route a fresh Codex content review (access-blocked, not content).
• Governance (non-execution): TKT-BASE-GOV-FOLD-1 / V02-NVSZ-GOV-FOLD-1 — apply canonical fold.

Your options (you choose; nothing here is pre-selected)

1. HOLD (default) — keep everything reviewed/hardened; nothing executes.
2. AUTHORIZE_IMPLEMENTATION_EXECUTION_NO_PRODUCTION — authorize a separately gated KB/governance execution macro, only after OPT-4 (FIX7-P0-PLAN-EXEC-AUTH-1) and production-surface scoping (-SURFACE-1/-2). That macro must use the hardened validator. PG/Directus/registry-row/ system_issues/REAL_RUN/QT001/permit/activation/repoint/cutover still each require their own separate explicit authorization.
3. AUTHORIZE_PRODUCTION_CUTOVER_LATER_SEPARATELY — a later, separate production decision with its own macro and authorization. Not granted by this note, the seal, or the dry-run.

To authorize, supply: selected_option, owner_signature, owner_signature_timestamp, and scope_of_production_surfaces_if_any. Until then: HOLD.