KB-54E5

IU Core 1k+ — 07 Next macro package (1400x Qdrant live + Directus register)

3 min read Revision 1
iu-coredieu44v0.61k-plusnext-macro1400xqdrant-livedirectus-register2026-05-23

07 — Next macro package

State at handoff

  • Commit 00e8cc6 (code) + 8cae3db (KB) on main (parent a236ed3). 1045 tests.
  • Production directus DB: migrations 001–020 + runtime through 300 — DOT 123/123, 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 020 additive + reversible (rollback/020). No durable IU mutation. F-1k-1 closed; F-960x-1 closed.

Open gaps carried forward (external integration only)

  1. Qdrant external apply — wire connector's HttpPoster with QDRANT_LOCAL_API_KEY from VPS env; choose IU Core collection name (separate from agent-data's production_documents); add embedder (OpenAI via OPENAI_API_KEY); open iu_core.vector_sync_enabled for one bounded gated reindex; record indexed points via v2 fn with proper boundary fields. Connector + gate + registry + drift + boundary CHECK all built — external-write slice only.
  2. Directus collection registration — register v_ui_iu_three_axis_envelope as read-only Directus collection (admin action, no schema change). See doc 03 §5 runbook.
  3. Nuxt assembly wiring — point existing Nuxt screen at new Directus collection. No new business logic, no new server route.

IU_CORE_1400X_QDRANT_LIVE_EMBED_AND_DIRECTUS_REGISTER — gap #1 (wire embedder + dedicated IU Core collection, run one bounded gated Qdrant reindex of a small per-IU sample, prove drift→reindex through v2 boundary path end-to-end) + gap #2 (Directus read-only collection registration). Fold in gap #3 as Nuxt assembly sub-slice (deploy-gated).

Alternative smaller slices: dot_iu_apply_manifest (still carried from 960x) or worker-driven delivery batch.

Is IU Core functionally complete?

Yes. Core (governed IU lifecycle, structure ops, composer, auto-cut, text-as-code apply, internal delivery, operator runtime with concurrency safety, vector sync foundation, per-IU vector boundary enforced at three layers, three-axis UI envelope) is built, DOT-visible (123/123), tested (1045) and reversible. What remains is external integration only.

Verification gate before 1400x

1400x 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 123/123, migration 020 applied, iu_vector_sync_point 3, v_ui_iu_three_axis_envelope returns 163 rows.

Back to Knowledge Hub knowledge/dev/laws/dieu44-trien-khai/v0.6-iu-core-1k-plus-vector-ui-assembly-acceptance-open-goal/07-next-macro-package.md