GPT Direction — Fix IU Technical Gaps Only Before Workflow Design Discussion

Date: 2026-05-29 Reviewer: GPT Council via Web Connector fallback

User decision

User explicitly decided:

• Fix real IU gaps/bugs first.
• Record workflow design / MOWD / process registry ideas for later discussion.
• Do not implement design-heavy workflow/MOWD work now.

Accepted audit result

Audit package: knowledge/dev/reports/architecture/iu-design-live-gap-dot-ops-workflow-design-registry-audit-2026-05-29/

Accepted findings:

1. P0 BUG: post-cut axis autowire is not wired. fn_cut_complete exists but cut functions do not call fn_iu_post_cut_axis_materialize. New cuts may not auto-refresh axes B/C.
2. P1 GAP: IU DOT operational completeness is partial (~68%). Missing/relevant DOT wrappers include reconstruct, emit, capture-in, route-worker, DLQ-replay, IU-relation-write, enact, vector-reindex.
3. P1 GAP: IU DOTs are not sufficiently integrated into dot_tools SSOT / Điều 35 Tier-A pattern.
4. P1 GAP: Vector PG↔Qdrant reconciliation remains unresolved due to missing Qdrant read path; no-cross-IU pollution is structurally proven in PG but greenfield/full reconciliation is not yet complete.
5. P1 workflow substrate IU-binding and MOW/MOWD are design/business-operational questions and must be deferred for discussion.

Next execution policy

Run a technical bugfix campaign only:

IU_TECHNICAL_GAP_FIX_P0_AUTOWIRE_DOT_VECTOR_RECONCILE

Scope:

• Fix P0 post-cut autowire if safe.
• Verify with a governed safe test cut or dry-run/canary.
• Add or prepare missing DOT wrappers for repeated IU operations, prioritizing non-mutating/read wrappers and safe governed wrappers.
• Reconcile vector PG↔Qdrant state using read-only Qdrant API if available; do not write Qdrant.
• Patch stale IU design/live docs to reflect fixed state.

Out of scope:

• MOWD design implementation.
• Workflow design registry creation.
• 4 Mothers runtime.
• UI/Nuxt.
• Directus mutation.
• Qdrant/vector write.

Required final result

The next macro should output:

• exact fixed/not-fixed status for P0 and P1 IU technical gaps;
• live evidence and rollback for any changes;
• before/after tests;
• updated gap board;
• remaining gaps classified as technical vs design/human-decision.