07 — Next macro package

State at handoff

• Commit c16d4a0 on main (parent 5b743c0); KB commit a236ed3. 1020 tests.
• Production directus DB: migrations 001–019 + runtime through 300 — DOT 121/121, 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, iu_vector_sync_point 3 (dryrun), dot_iu_runtime_lease 0.
• All write-gates inert: composer / delivery / operator_runtime / structure_ops / vector_sync = false; routes_master / route_worker = true.

No unsafe state

Migration 019 is additive + reversible (rollback/019). No durable IU mutation. Finding F-960x-1 is closed. No carried production-apply gap.

Open gaps carried forward

1. Qdrant external apply — wire the connector's HttpPoster with the api-key from the VPS deployment secret; add an embedder; open iu_core.vector_sync_enabled for one bounded gated reindex; record indexed points. The connector, gate, registry and drift check are all built — this is the external-write slice only.
2. sandbox/150 self-seeding (finding F-1k-1) — make the delivery probe seed a synthetic structure event inside its BEGIN...ROLLBACK so T4/T6 are deterministic regardless of the live backlog.
3. Directus/Nuxt operator UI — expose the read-only v_* views (incl. v_iu_vector_sync_status) as a Directus read-only collection or a Nuxt page. Deploy-gated integration outside this repo.
4. dot_iu_apply_manifest — an atomic one-command driving a whole build_collection_apply_plan in one transaction / one ledger row.
5. Worker-driven delivery batch — a delivery batch through fn_iu_route_worker_run writing sent iu_route_attempt rows.
6. Discovered (non-synthetic) auto-cut — an integrated run over a cut DISCOVERED from a real source document.
7. Axis-B inferred lane — a deterministic classifier; still 0 inferred rows.

Recommended next macro

IU_CORE_1200X_QDRANT_LIVE_SYNC_AND_OPERATOR_UI — gap #1 (wire the secret + embedder, run one bounded gated Qdrant reindex, prove drift->reindex end-to-end) + gap #3 (the Directus read-only-collection UI exposure). Fold in gap #2 (sandbox/150 self-seeding) as a hardening sub-slice. Both build directly on this macro's vector_sync.py connector + iu-tree/ manifests.

Is IU Core functionally complete?

Nearly — at the production-ready operating-surface boundary. The core (governed IU lifecycle, structure ops, composer, auto-cut, text-as-code apply, internal delivery, operator runtime with concurrency safety, vector sync foundation) is built, DOT-visible (121/121), tested (1020) and reversible. What remains is external integration, not core capability: the live Qdrant write path (secret + embedder) and the Directus/Nuxt UI exposure. Neither is a core gap.

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 121/121, iu_vector_sync_point 3, dot_iu_command_run 18, migration 019 applied.