Codex FIX7 N7/N8/P7 Authority-Seal Authoring

• Review timestamp: 2026-06-11T15:01:56+07:00 Asia/Ho_Chi_Minh
• Final status: CODEX_FIX7_N7_N8_P7_AUTHORITY_SEAL_REJECTED
• Production mutation: NO
• Implementation execution: NO
• REAL_RUN / QT001 / permit / activation / repoint / cutover: NO
• N7 / N8 / P7 authored: NO / NO / NO

Decision

All governed engineering gates pass, but the exact owner-supplied A5 value cannot be encoded by the ratified authority-seal contract.

Owner supplied:

OPT-3_AUTHORIZE_CODEX_AUTHORITY_SEAL_AND_POST_SEAL_IMPLEMENTATION_PLANNING_ONLY

The pinned encoder 13344f92...957144b8 requires owner_blueprint_decision to match [A-Z0-9_]. The hyphen in OPT-3 causes:

SEAL_FIELD_BAD_ENUM: owner_blueprint_decision=... (decision token [A-Z0-9_])

Codex may not normalize or fabricate an authority input. The chain is therefore rejected atomically, before any official N7, N8, or P7 artifact is emitted.

Ratified Inputs

input	status	source	hash/tree	usable?	limitation
N-number table	RATIFIED_FOR_BINDING_USE	Codex targeted recheck	governed rev1	YES	not a seal
N6	RATIFIED_ENGINEERING_VERIFIED_CANDIDATE	Real-N6 certificate	d777e87c...b258c; cert 055828db...6b96	YES	not official before seal
encoder	byte-exact PASS	alignment packet	13344f92...957144b8	YES	rejects supplied A5
alignment packet	RERUN PASS	governed packet	96d00b9e...83c1	YES	non-authority evidence
authority-input packet	RERUN PASS	governed packet	ac679319...b0d0	YES	candidate inputs only
owner OPT-3	supplied, semantically clear	owner macro	exact A5 above	NO	invalid decision-token grammar

Reality Checks

• Fresh reconstruction: 75/75 required governed documents fetched.
• Authority-input packet: RERUN_RESULT: PASS.
• Alignment packet: RERUN_RESULT: PASS.
• Real-N6 packet: RERUN_RESULT: PASS.
• N8 report set: all 15 documents exist; one candidate revision drifted from 1 to live 2, and Codex recomputed the live digest c42decc79b12779f54e551be7f90cc62e7ed7f4ef8488cc0568cce52d60973b4.
• Codex bad-input probes: 25/25 fail-closed.
• Official seal artifacts emitted: 0.
• Implementation planning allowed next: NO, because the seal was not authored.