<!-- DOC_STATUS: ACTIVE_NON_AUTHORITY -->

FIX7 P0 — Seal-Consumption Report (2026-06-11)

• Authority: PLANNING_NON_AUTHORITY. Read-only consumption of the official seal. Authorizes nothing.
• Machine form: …/fix7-p0-implementation-planning-packet-2026-06-11/seal-consumption.json (byte-identical content).

Official chain consumed

node	digest	meaning	depends_on	must_not_depend_on
N7	efb0c5747ae5f56c0e8b5d99c35438a3d6231253570e6ab4d2658ab9e1853d32	approval-event envelope manifest	N1..N6, A1/A2/A3/A5	N8, P7
N8	daa70c39a91a64696fb1a24ca2d3f620d04049583c9047689902ebf26117e1a1	Codex detached seal (report set c42decc7…73b4, 15 docs)	N2,N5,N6,N7	P7
P7	9ddb27c35a06ca11ee616e3b0399c705d0d97f5b8f284c12045c396f7c034550	authoritative pin of rev3 + Packet V3	N2,N7,N8	self/P7

Supporting engineering identities (all sealed-in, re-read from the seal packet): N6 d777e87c…b258c; canonicalizer rev3 49c386a9…b734d0 (38756 B); Packet V3 tree b95df0a5…ca6d; membership f2bda8…fe251; encoder 13344f92…957144b8.

Verification performed (read-only)

• Each of N7/N8/P7 read back from the seal packet JSON; digests match the macro-supplied chain exactly.
• Seal packet packet_tree.sha256 = 3890cd34…a234 = sha256(HASH_MANIFEST.txt) — matches the macro-supplied seal tree.
• manifest.json of the seal packet is internally consistent (n7/n8/p7/report_documents_digest/encoder all agree).
• Owner decision in n7-approval-event.json: OPT3_AUTHORIZE_CODEX_AUTHORITY_SEAL_AND_POST_SEAL_IMPLEMENTATION_PLANNING_ONLY.

Exact authorized scope

• Post-seal implementation PLANNING only (this paper macro).
• Treating canonicalizer rev3 + Packet V3 tree as the authoritative blueprint identity (the pin).

Exact forbidden scope

Implementation execution; any production mutation; PG; Directus; registry-row; system_issues; REAL_RUN; QT001/apply; permit; activation; repoint; cutover; v0.2 promotion. implementation_authorized_by_p7_alone = false.

Boundary

Implementation planning is allowed. Implementation execution is blocked — it requires a separate owner OPT-4 (or explicit equivalent), and REAL_RUN/QT001/ cutover each require their own separate authorization beyond that.