GPT Roadmap Review — IU after Master Design Rev4

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

User-proposed roadmap

1. Complete and approve the new 4 Mothers + Event 5-layer + Governance Master Design.
2. Review what must be prepared/upgraded to finish Information Unit testing and make IU production-ready.
3. After IU is complete, return to implementation of 4 Mothers / Event 5-layer / Governance, while doing enough event/governance substrate work in parallel to support IU testing.

Verdict

ROADMAP_ACCEPTED_WITH_PARALLEL_INFRA_GATES

The roadmap is correct. Master Design Rev4 can be accepted as a document-only baseline. The next implementation direction should not jump directly into MOW/MOT/MOIT/MOUT. It should return to the Information Unit substrate and finish tests b–f, while surveying/upgrading the minimum event/queue/governance substrate required for those tests.

IU tests to complete

Already partially completed:

• a. Cut texts automatically and reconstruct original source order.

Remaining:

• b. Filter by domain/professional axis from Constitution to cut documents.
• c. Filter by parent-child/grandchild tree axis.
• d. Create a document from scratch by assembling IUs; test add/remove/merge/split/reorder automatically.
• e. Test trigger in/out for each IU.
• f. Test SQL link between IU and current DB data.

All should become DOT-callable, config-driven, and end-to-end automated.

Recommended next phase

Run a document-only readiness macro first:

IU_CORE_PROCESS_BRICK_READINESS_AND_GAP_SURVEY_DOCUMENT_ONLY_3000X

Purpose: determine what IU substrate and event/queue/governance substrate must be ready before tests b–f and before IU production use.

Required survey areas

1. IU substrate current state:

   • information_unit
   • unit_version / iu_version
   • iu_piece_collection / membership
   • three-axis envelope
   • metadata tags
   • lifecycle log
   • SQL links

2. IU process-brick upgrades:

   • iu_process_binding
   • role_in_process
   • assembly_slot
   • precondition_config
   • postcondition_config
   • io_contract_refs
   • executor_class_ref
   • event_contract_ref
   • kg_edge_refs
   • governance_state

3. Test b–f gap map:

   • domain-axis filter
   • parent-child tree filter
   • compose/add/remove/reorder/merge/split
   • trigger in/out
   • SQL link
   • reconstruction/no-vector safety

4. Minimal event/queue/governance required for IU tests:

   • event_type_registry
   • event_outbox
   • event_subscription
   • job_queue
   • job_dead_letter
   • queue_heartbeat
   • idempotency registry
   • retry policy
   • DLQ replay
   • executor_class_registry
   • state_machine_registry
   • trace/correlation
   • audit timeline

5. Existing gaps known from previous reports:

   • post-CUT autowire pending
   • split/merge review_decision_id pending
   • candidate registries survey needed
   • trigger model readiness
   • SQL link proof needs full automation

Sequencing recommendation

1. Approve Master Design Rev4 as document-only baseline.
2. Run IU readiness/gap survey.
3. Produce IU test b–f automation implementation plan.
4. Implement only the minimum event/queue/governance substrate required for IU tests.
5. Run IU tests b–f end-to-end automatically via DOT.
6. Promote IU substrate toward production readiness.
7. Then return to 4 Mothers / Event 5-layer / Governance implementation.

Key constraint

Do not build 4 Mothers on an incomplete IU substrate. If IU is too narrow, later implementation will drift into duplicate workflow body fields, task instruction copies, ad-hoc event payloads, or Nuxt logic.

Final recommendation

The user roadmap is sound. The next concrete macro should be IU readiness, not 4 Mothers implementation.