Action-Ready Blockers (rev2) — after Gap-only Spec repair

Nature: the live blocker list after the rev2 repair. It explicitly does NOT claim "no engineering omissions remain" — that rev1 wording was rejected by Codex (fix 11/H6) and is withdrawn. rev2 carries both authority/owner blockers and build-time guarantee blockers that must be satisfied before the read/report MVP is accepted. Date: 2026-06-09 · Supersedes: checkpoints/action-ready-blockers-after-gap-only-spec-2026-06-09.md (rev1, superseded by Codex review). Production mutation: NO. writes_performed: KB design docs only.

1. Status of "engineering omissions"

NOT claimed clean. rev1 said "engineering/design omissions: NONE" — Codex disagreed and the claim is withdrawn. rev2's position: the read/report design is repaired against the 12 Codex findings, but acceptance of the MVP depends on build-time guarantees that cannot be asserted at design time (capability guards, negative capability tests). Those are tracked below as real blockers, not "done."

2. Blockers gating the read/report-only MVP

• B0′ — Codex RE-review / RE-seal of the rev2 layer (gates the read/report MVP). The rev2 spec/pilot/plan/matrix/ledger are ..._REV2_READY_FOR_CODEX but not yet re-reviewed/re-sealed. The prior single-checkpoint B0 is superseded; a fresh seal of rev2 is required. Next action: route reviews/codex-checkpoint-packet-gap-only-spec-and-fix7-pilot-rev2-2026-06-09.md to Codex (after optional GPT pass). Blocks MVP? Yes — the read/report-only MVP.
• B4 — Capability guards not yet implemented (gates MVP acceptance, not seal). The static guard (capability/dependency lint) and runtime guard (read-only PG role context_pack_readonly, no write credential, no shell, KB-path allowlist) are specified but unbuilt (v0.1 builds nothing). Next action: implement after the seal; they are MVP acceptance gates G4/G5. Blocks MVP? Yes — MVP cannot be accepted until they exist and the negative capability tests (#14–#17) pass.
• B5 — Governed claim-declaration contract does not exist (bounds, does not block, the MVP). Without it, claim_inventory_completeness is normally UNVERIFIED, so dossiers with risky prose cannot reach READ_LEVEL_ACCEPTABLE. This is accepted as honest behavior, not a defect; it caps positive verdicts rather than blocking the build. Next action: none required for v0.1; a future governed declaration contract would raise the completeness ceiling.

3. Blockers gating the execution surface (carried, owner/authority — expected carve-outs)

• B1 — Call / Proof-of-run Contract not sealed. Gates the command-runner with exit codes and the run/pass half of the claim↔evidence binder. Needs owner authorization + Codex review of per-command identity / mode / inputs / exit-code semantics / timeout / lease / audit ledger / non-mutation boundary. Blocks the read/report MVP? No. Blocks the runnable verifier? Yes.
• B2 — iu_core ↔ cutter_governance lineage owner decision. Gates the generic package_manifest schema. Needs owner lineage decision then Codex schema review. Blocks the read/report MVP? No (it uses native KB document_id/revision). Blocks manifest work? Yes.
• B3 — TAC ↔ IU corpus authority unresolved (by design, Domain H). Gates any corpus-canonical / bridge work. Needs owner decree + Codex bridge/resolver review. Blocks the read/report MVP? No (it dual-reports). Blocks bridge work? Yes.

4. Net statement

The read/report-only MVP is blocked on B0′ (fresh Codex re-seal of rev2) and, for acceptance, on B4 (capability guards built + negative tests passing). B5 bounds (does not block) positive verdicts. The execution surface stays blocked on B1/B2/B3 — owner/authority decisions that are expected carve-outs. No "no engineering omissions remain" claim is made.

Cross-references

• rev2 spec / pilot / plan / matrix / fix ledger / checkpoint packet (see those docs).
• Codex review: reviews/codex-review-gap-only-spec-fix7-pilot-mvp-readiness-2026-06-09.md.
• Future contracts: planning/future-contracts-queue-after-v0-1-2026-06-09.md.
• Superseded rev1: checkpoints/action-ready-blockers-after-gap-only-spec-2026-06-09.md.