<!-- DOC_STATUS: ACTIVE_NON_AUTHORITY -->

FIX7 — Owner Authority Decision Packet (2026-06-11)

• Audience: OWNER (decision-ready). Authority of this doc: options only. T1 prepared the options and required fields; T1 does not choose, approve, or seal.
• Machine form: fix7-owner-authority-decision-packet-2026-06-11.json (byte-identical to the packet's owner-decision-template.json).
• Default safe decision: NOT_APPROVED_HOLD (stands until the owner explicitly decides).

1. What has been technically ratified (engineering only)

• N-number table → RATIFIED_FOR_BINDING_USE (Codex, 2026-06-11) — now binding as an engineering convention; not a seal.
• N6 d777e87c…b258c → RATIFIED_ENGINEERING_VERIFIED_CANDIDATE — a real engineering candidate, NOT an official seal and NOT an official pin.

2. What has NOT been authorized

N7 approval event · N8 detached seal (Codex-only) · P7 authoritative pin of canonicalizer rev3 · FIX7 blueprint approval · FIX7 implementation (out of scope until after the seal).

3. What you would be approving if you approve later

Supplying the approval-event inputs (A1 id, A2 identity, A3 timestamp, A5 blueprint decision) so Codex can author N7 → N8 → P7. Sealing mutates nothing in production; it pins the rev3 candidate as authoritative. Implementation remains a separate, later, separately-gated decision.

4. Options

Option	Meaning	Consequence
OPT-1 Keep do-not-approve / HOLD	status quo	packet + N6 candidate + N-number table preserved; no seal, no implementation
OPT-2 Authorize Codex/authority seal only	supply A1..A5; Codex authors N7/N8/P7	blueprint becomes sealed; implementation still NOT authorized
OPT-3 Also authorize implementation planning after seal	T1 drafts the implementation macro (paper only)	no mutation; you review before any execution
OPT-4 Authorize implementation macro with no-production gates	T1 executes the implementation lane under the precondition checklist	every mutation gated + rollback-verified; REAL_RUN/QT001/cutover still separate

Options are cumulative (OPT-2 ⊂ OPT-3 ⊂ OPT-4). T1 makes no recommendation — this is an authority decision.

5. What remains blocked / forbidden regardless of option

No production mutation · no PG/Directus/registry/system_issues mutation · no REAL_RUN · no QT001 apply · no permit · no activation · no repoint · no cutover · no registries-pivot · no auto-birth repair · no T1 self-approval · no fabricated N7/N8/P7 seal.

6. Required fields if you approve the seal (OPT-2+)

A1_approval_event_id, A2_approver_identity, A3_approval_event_timestamp, A5_owner_blueprint_decision. Until supplied, ready_to_author = false and no N7/N8/P7 can exist.