Checkpoint — Codex Re-seal Gap-only Scope Spec rev2

Date: 2026-06-09
Final status: GAP_ONLY_SPEC_REV2_PARTIAL_FIX_REQUIRED
Production mutation: NO
MVP implementation authorized: NO
Minimal safe next step: Return to T1 for rev3.

Scope completed

Performed the prompt-bounded adversarial re-seal only. Did not redo the full baseline, redesign the tool, implement code, create schema/tool/runner, resume FIX7, install anything, or mutate PG/Directus/registry/filesystem production state.

Final gate summary

Gate	Verdict
1 — Codex 12-fix ledger	PARTIAL
2 — Article 14	PASS
3 — FIX7 Recheck-8 sufficiency	PARTIAL
4 — Hardcode / fake-green	PARTIAL
5 — PG-first / native / driven	FAIL
6 — No parallel authority	PARTIAL
7 — MVP readiness	FAIL

What rev2 fixed

• Removed READ_REPORT_PASS.
• A reference or prose statement alone cannot create an acceptable verdict.
• Added explicit claim→type→required evidence class→artifact→capability→adequacy→verdict binding.
• Execution-class claims remain Article-14 not-proven without accepted run evidence.
• Claim-extractor completeness fail-closes to UNVERIFIED.
• Removed literal denominator gates and >=2/41/4/219/102 invariants.
• Removed exit-0 fake-green.
• Added resolvable-but-insufficient Fixture C.
• Kept runner/mutation/proof-of-run behavior out of scope.

Remaining blockers

1. Rev2 normative taxonomies/rules have no identified binding PG-driven runtime source; implementation would hardcode them or promote a file to shadow authority.
2. No-run/no-write guard is not structurally coherent: no socket conflicts with allowed remote reads; a PG read driver can also write; no concrete sandbox/connector/role enforcement substrate is named.
3. Actual FIX7 canonicalizer identity/existence resolution through allowed read surfaces is unproven; fail closed to UNVERIFIED unless specified.
4. Authority wording in 00-index.md was normalized during this re-seal, but exact runtime reliance on the review-ready/nonbinding-as-a-whole Authority Contract remains unresolved.
5. Negative capability tests need explicit shell/subprocess, dynamic-import, general-network/credential, and write-via-allowed-PG-client cases.

Article 14

PASS. Rev2 structurally prevents prose-only PASS and evidence-reference-only PASS. No execution claim can look green without accepted run evidence.

Hardcode / fake-green

PARTIAL. Numeric production hardcode and exit fake-green are closed. Authorityless normative taxonomy/action/verdict rules remain a disguised-hardcode risk.

PG-first / native / driven

FAIL for build readiness. Fact reads are PG/native where applicable, but the inspector's governing policy has no sealed PG-driven source.

Parallel authority

PARTIAL. No runner/logger/registry/resolver/bridge/proof-of-run authority is created, but the rev2 file can become a shadow claim/evidence policy authority.

Read-back target

Full reasoning and required rev3 corrections:

knowledge/dev/laws/tool-kiem-thu/reviews/codex-reseal-gap-only-spec-rev2-2026-06-09.md