07 — Next macro package

State at handoff

• Commit 24c2885 on main (parent 39093de); KB commit 5b743c0. 981 tests.
• Production directus DB: migrations 001–018 + runtime through 300 — DOT 113/113, D8 drift 0.
• information_unit 163, iu_piece_collection 3, iu_piece_membership 8, dot_iu_command_run 18, iu_tree_change_log 56, iu_route_attempt 68, dead-letter 0.
• All IU Core write-gates inert: composer_enabled=false, delivery_enabled=false, operator_runtime_enabled=false, structure_ops_enabled=false; routes_master_enabled=true, route_worker_enabled=true (the controlled 500x end-state).

No blocker

Every approved DURABLE branch completed. There is no carried production-apply gap and no unsafe production state.

Open gaps carried forward

1. Qdrant / vector sync connector — the reindex contract is specified (doc 05): one iu-tree/**/*.md manifest → one vector point, drift detected via corpus_digest, gated by a new dot_config iu_core.vector_sync_enabled key, driven by a dot_iu_vector_sync one-command. The connector module + gate + command are unbuilt.
2. Directus/Nuxt operator UI — the read-only v_* views + the dot_commands CLI are the surface; exposing them as a Directus read-only collection or a Nuxt page is a deploy-gated integration task.
3. Worker-driven delivery batch — runtime/300 used the fn_iu_route_deliver primitive directly. A delivery batch driven through fn_iu_route_worker_run (with a controlled cursor reset, writing sent iu_route_attempt rows) is a natural completeness slice.
4. Discovered (non-synthetic) auto-cut — an integrated run over a cut DISCOVERED from a real source document (bounded, birth-gated) — carried from 500x.
5. OperatorRuntime concurrency safety — finding F-960x-1: the gate-window pattern is not concurrency-safe. A future macro should make gate acquisition atomic (a session-scoped advisory lock around the open→apply→close window) so concurrent operator runs cannot race.
6. Text-as-code apply through OperatorRuntime as a single one-command — today build_collection_apply_plan emits N separate one-commands. A dot_iu_apply_manifest command that drives the whole plan atomically (one ledger row, one transaction) would complete the apply surface.
7. Axis-B inferred lane — still 0 inferred rows; needs a deterministic classifier (carried from 120x/240x).

Recommended next macro

IU_CORE_1200X_VECTOR_SYNC_AND_OPERATOR_UI — combine gap #1 (build the gated IU-Core → Qdrant connector + dot_iu_vector_sync one-command + drift check) with gap #2 (expose the read-only v_* views as a Directus read-only collection / Nuxt operator page). Both are additive and build directly on this macro's iu-tree/ manifests + observability views. Fold in gap #5 (OperatorRuntime advisory-lock concurrency fix) as a hardening sub-slice.

Alternative smaller slices: the worker-driven delivery batch (gap #3) or the dot_iu_apply_manifest atomic apply command (gap #6).

Verification gate before 1200x

1200x should start only after GPT/User has verified, via AgentData list_documents + search_knowledge, that this macro's 7 reports are present and searchable, and that production reports DOT 113/113, iu_tree_change_log 56, dot_iu_command_run 18.