<!-- DOC_STATUS: ACTIVE_NON_AUTHORITY -->

FIX7 — N7 Envelope N6-Availability Update Report (2026-06-11)

• Host: T1 / Claude Code · Codex consulted: NO · Owner approval: NO · Production mutation: NO
• Closes (engineering doc-hygiene): Codex note that N7 envelope rev4 still carried pre-ratification prose SEAL_REAL_N6_NOT_AVAILABLE.
• Surface: knowledge/dev/laws/tool-kiem-thu/packets/fix7-authority-closure-2026-06-10/n7-approval-event-input-envelope.md and .json → rev4 → rev5.

1. What Codex flagged

…/codex-fix7-n-number-n6-targeted-recheck-2026-06-11/authority-inputs-and-blockers.md (rev1):

"The N7 envelope rev4 still contains pre-ratification prose SEAL_REAL_N6_NOT_AVAILABLE. That statement does not invalidate this Codex N6 ratification, but a later authority-seal phase must instantiate/update the N7 authority event to consume this ratified N6 rather than silently relying on stale pre-ratification prose."

2. The repair (labels/text + one justified metadata field)

Location	Before	After
.md header	rev4	rev5 bullet: N6-availability prose update; text/labels only; digest/encoder/roster/edges/authority UNCHANGED
.md §6 N6 row status	SEAL_REAL_N6_NOT_AVAILABLE	AVAILABLE — RATIFIED_ENGINEERING_VERIFIED_CANDIDATE (d777e87c…b258c, cert 055828db…6b96); NOT a seal/pin; does not alone authorize N7/N8/P7; old text marked superseded/historical
.md §6.2	"path stays blocked SEAL_REAL_N6_NOT_AVAILABLE until a real chain exists"	rev5 paragraph: real ENGINEERING_VERIFIED_CANDIDATE chain now exists + Codex-ratified; remaining blockers = authority inputs; promotion to OFFICIAL_PIN is owner/Codex at seal
.json provenance.active_corpus_sha256_current_class	REHEARSAL	ENGINEERING_VERIFIED_CANDIDATE + value + active_corpus_sha256_ratified_by + cert binding
.json provenance.standing_true_blocker	SEAL_REAL_N6_NOT_AVAILABLE …	AUTHORITY_INPUTS_MISSING …; old token retained under superseded_historical_blocker
.json flags	rehearsal_only: true	rehearsal_only: false, n6_available_as_engineering_candidate: true, n6_is_official_seal: false, n6_authorizes_n7_n8_p7_alone: false, n7_authored: false, codex_sealed_values_present: false

Direct-contradiction justification for the metadata field. Codex ratified the candidate as ENGINEERING_VERIFIED_CANDIDATE, which directly contradicts the JSON's current_class: REHEARSAL; per the macro this is the one case where a metadata update (not just labels) is permitted. The N6 digest, encoder (13344f92…), N7 roster order, byte rule, DAG edges, and authority semantics are UNCHANGED. This is not owner/Codex authoring of any seal.

3. What did NOT change

• N6 digest d777e87c…b258c — unchanged.
• authority_seal_encoder.py (13344f92…957144b8) — untouched; encode_real_n7 still defaults real_n6_available=False and rejects REHEARSAL. Codex sets real_n6_available=True over the ratified candidate at seal time; we do not flip it here.
• N7 roster, order, domain tag, output field, DAG edges (N7 → N2,N3,N4,N5,N6,N1) — unchanged.
• A1/A2/A3/A5 — still MISSING_AUTHORITY_INPUT.

4. Verification

• Executable stale-prose detector over the corrected status snapshot AND the updated envelope .md prose: PASS — no live stale assertion (every SEAL_REAL_N6_NOT_AVAILABLE occurrence is on a line marked superseded/historical/pre-ratification).
• python3 stale_prose_detector.py --scan n7-envelope-n6-status.json --prose <envelope.md> → exit 0.
• Bad-input probe P2 (re-inject SEAL_REAL_N6_NOT_AVAILABLE as a current status) → fail-closed (AUTHINPUT_N6_FALSELY_OFFICIAL / STALE_N6_CURRENT_STATUS).

5. Authority impact

NONE. The N7 envelope remains a provisional-non-authority input assembly. It now references the ratified engineering N6 candidate correctly instead of stale unavailability prose, while keeping N6 an engineering candidate (not a seal/pin) and keeping all authority inputs MISSING. No N7/N8/P7 is authored.