<!-- DOC_STATUS: ACTIVE_NON_AUTHORITY -->

FIX7 Authority Report-vs-File Consistency Audit (2026-06-11)

Host: T1. Authority: NON_AUTHORITY. Codex consulted: NO. Every load-bearing claim in this lane's reports is tied to an actual governed file + command + exit artifact. No claim rests on prose alone.

claim	governed file	command	exit	evidence artifact
encoder byte-exact 13344f92…	…/fix7-authority-closure-2026-06-10/authority_seal_encoder.py	shasum -a 256	—	sha == governed pin == model JSON S3.encoder_sha256
encoder 48/48 selftest	same (materialized)	python3 authority_seal_encoder.py --selftest	0	selftest.stdout.log
codex probes 19/19 rejected	…/codex_probes.py	python3 codex_probes.py	0	codex_probes.stdout.log
n-node checker 15/15	…/n_node_checker.py	python3 n_node_checker.py	0	n_node_checker.stdout.log
supplemental 10/10	…/sp_align_probes.py	python3 sp_align_probes.py	0	sp_align_probes.stdout.log
packet OVERALL PASS	…/commands.sh	bash commands.sh	0	exit_codes.json (5 gates ok=true)
fresh reconstruction PASS	…/RERUN.sh	bash RERUN.sh (clean dir)	0	RERUN_RESULT: PASS
tamper fails closed	RERUN.sh + HASH_MANIFEST/tree	byte-flip / tree-tamper	1	FAIL (manifest drift) / FAIL (tree mismatch)
collision ceiling = 224	registry JSON	`grep -oE TKT-OBJ-[0-9]+	sort -n`	—
N-node model grounding	…/designs/fix7-n-node-authority-model-design-addendum-2026-06-11.json	batch_read full	—	model JSON quoted

Discrepancies found

• None between report claims and files. Every "PASS"/"REJECTED"/"exit 0" in the reports corresponds to a captured exit code from a real run.
• The one place a report could over-claim — "real N6 / real seal" — is explicitly NOT claimed; the encoder refuses it (SEAL_REAL_N6_NOT_AVAILABLE) and the reports state it as a standing blocker, consistent with the file behavior.

Reality checks

• Any report says PASS but command exited nonzero? NO.
• Any report says evidence exists but file missing? NO.
• Any report-only (prose-only) evidence for a load-bearing claim? NO.