GPT Review — IU b–f Readiness Survey + Next Command

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

Source read directly

• knowledge/dev/reports/architecture/iu-core-process-brick-readiness-and-gap-survey-2026-05-28.md revision 1

Verdict

SURVEY_ACCEPTED_NEXT_STEP_AUTOMATION_PLAN

The survey is accepted. It materially changes the operating view: IU substrate is more live than the Master Design assumed. Tests b/c are high-readiness read paths; f is medium-high; d/e are medium because they require governed gate opening, review_decision wiring, event type registration, and delivery gates.

Do not implement 4 Mothers. Do not run mutating IU tests yet.

Key finding

The next blocker is not mainly missing database substrate. The real blockers are:

1. dot_config runtime gates are OFF:
   • iu_core.composer_enabled=false
   • iu_core.structure_ops_enabled=false
   • iu_core.delivery_enabled=false
   • iu_core.three_axis_auto_refresh_enabled=false
   • iu_core.operator_runtime_enabled=false
   • queue.job_substrate.enabled=false
   • queue.dlq.replay_enabled=false
2. No end-to-end DOT automation harness for tests b–f.
3. Split/merge still requires review_decision_id wiring.
4. Trigger in/out needs IU event type registration and bounded delivery test.
5. SQL link needs DOT-callable create/validate/proof command.
6. Design PG Maximization Map should later be reconciled with live inventory so it does not re-propose live substrate.

Test order

Recommended execution order:

1. b — professional/domain axis filter: read-only, high readiness.
2. c — parent-child-grandchild tree filter: read-only, high readiness.
3. f — SQL link proof: medium-high, likely low mutation if validate/read-only proof first.
4. d — assemble/add/remove/reorder/split/merge: mutating/gated, requires review_decision and gate protocol.
5. e — trigger in/out: mutating/delivery-gated, requires event types and delivery gate protocol.

Next macro

Run document-only planning macro:

IU_TEST_B_TO_F_AUTOMATION_PLAN_DOCUMENT_ONLY_XHIGH

Scope:

• Produce exact test plan and implementation sequence for tests b–f.
• Design bounded gate-flip protocol for test-only operations.
• Define DOT commands/harness needed.
• Separate read-only tests b/c/f-read proof from mutating tests d/e.
• Define exact acceptance criteria and rollback/gate-close procedure.
• No implementation, no PG mutation.

Implementation should not start until this plan is approved

Reason: tests d/e require gates and governance. Starting implementation without a bounded protocol could violate Điều 32/35/45 or leave gates open.

Later macros after the plan

After the plan is approved:

1. Implement/read-only harness for b/c first.
2. SQL link proof and DOT command for f.
3. Split/merge review_decision wiring and bounded structure_ops gate for d.
4. IU event type registration and bounded delivery gate for e.
5. Reconcile design PG Maximization Map to live inventory.
6. Candidate Registry Survey.
7. Event/Queue substrate hardening.

No-go

No 4 Mothers implementation until IU tests b–f and IU substrate readiness are closed or explicitly accepted with known gaps.