Action-Ready Blockers — after Gap-only Scope Spec

Nature: the blocker packet after closing the v0.1 planning layer. Every engineering/design omission is closed (the read/report-only spec, FIX7 pilot, MVP plan, acceptance matrix, and future-contracts queue are written and internally consistent). The blockers that remain are owner / operator / authority blockers only — by design, not omissions. The read/report-only MVP has exactly one gating blocker (the Codex checkpoint); the execution surface has owner/authority blockers that are expected carve-outs. Date: 2026-06-09 Production mutation: NO. Governing authority: Gap-only Scope Spec + Authority Contract v0.1 + Codex seal (BCDGH_SEALED).

---

1. Classification

• Engineering/design omissions: NONE. The planning layer is closed end-to-end.
• Owner/operator/authority blockers: 4 (B0 gating the read/report MVP; B1–B3 gating the execution surface).

2. Blockers

B0 — Single Codex checkpoint not yet routed/sealed (gates the read/report-only MVP only)

• Blocker: the Gap-only Scope Spec + FIX7 pilot are READY_FOR_CODEX_CHECKPOINT but not yet reviewed/sealed. The Reuse Extraction Map's own "minimal next step" was GPT review of the map; this macro consolidates that into one checkpoint packet.
• Why it blocks: MVP build is gated on GAP_ONLY_SPEC_SEALED (MVP plan §8 M1). No build before seal.
• Evidence: reviews/codex-checkpoint-packet-gap-only-spec-and-fix7-pilot-2026-06-09.md (5 questions).
• Owner/authority needed: GPT/User to route the packet; Codex to seal or return blockers.
• Exact next action: route the checkpoint packet to Codex (after optional GPT pass). On GAP_ONLY_SPEC_SEALED, the read/report-only MVP build may start.
• Blocks MVP? Yes — the read/report-only MVP (and only it). It does not block anything already sealed.

B1 — Call Contract not sealed (gates the execution surface)

• Blocker: no per-command Call Contract exists (sealed B/C: v0.1 calls nothing).
• Why it blocks: the command-runner with exit codes (gap #8.1) and the run/pass half of the claim↔test binder (gap #8.2) — the headline FIX7 capability of actually running declared executables — cannot be built or invoked.
• Evidence: Authority Contract §7; Codex seal B/C; Reuse Extraction Map §8.1/§8.2.
• Owner/authority needed: owner authorization + Codex review of a per-command Call Contract (identity, permitted mode, inputs, exit-code semantics, timeout, lease/gate, audit ledger, non-mutation boundary).
• Exact next action: queued — planning/future-contracts-queue-after-v0-1-2026-06-09.md [1]. Open only by explicit owner action.
• Blocks MVP? No for the read/report-only MVP; Yes for the runnable verifier (a later phase, correctly deferred).

B2 — iu_core ↔ cutter_governance lineage owner decision (gates the generic manifest schema)

• Blocker: two deployed cut/verify/manifest lineages; which is canonical is unresolved. Building on neither = a prohibited 3rd lineage.
• Why it blocks: the generic package_manifest envelope + schema (gap #8.3) cannot be designed/built.
• Evidence: Reuse Extraction Map §6.4, §7.11, §9.6.
• Owner/authority needed: owner lineage decision, then Codex schema review.
• Exact next action: queued — future-contracts queue [3-adjacent]; owner picks the canonical lineage.
• Blocks MVP? No for the read/report-only MVP (it uses native KB document_id/revision, not a generic manifest); Yes for any manifest work.

B3 — TAC ↔ IU corpus authority unresolved (gates any corpus-canonical / bridge work)

• Blocker: 0 joining views; corpus authority unresolved by design (Domain H).
• Why it blocks: any bridge/merge/canonical choice between information_unit (219) and tac_logical_unit (102).
• Evidence: Codex seal H; Authority Contract §7; Reuse Extraction Map §9.7.
• Owner/authority needed: owner decree of corpus authority + Codex bridge/resolver review.
• Exact next action: queued — future-contracts queue [5]. v0.1 dual-reports only in the meantime.
• Blocks MVP? No for the read/report-only MVP (it dual-reports); Yes for any corpus-canonical/bridge work.

3. Net statement

• The read/report-only MVP is blocked on B0 only (one Codex checkpoint). All design work for it is complete.
• The execution surface is blocked on B1/B2/B3 — owner/authority decisions that are expected carve-outs, not engineering gaps.
• There are no outstanding engineering/design omissions. (Completion-contract item 9 satisfied.)

---

Cross-references

• Codex checkpoint packet: reviews/codex-checkpoint-packet-gap-only-spec-and-fix7-pilot-2026-06-09.md
• Future contracts queue: planning/future-contracts-queue-after-v0-1-2026-06-09.md
• Gap-only Scope Spec: designs/implementation-package-dot-v0-1-gap-only-scope-spec-2026-06-09.{md,json}
• Authority Contract: contracts/authority-contract-v0-1-2026-06-09.{md,json} · Codex seal: reviews/codex-seal-authority-matrix-bcdgh-2026-06-09.md