Incomex AI Portal
KB-703E

GPT Recheck After Drive Upload — IU / 4 Mothers / Event Foundation (2026-05-27)

13 min read Revision 1
reviewgptiu4-mothersevent-foundationdrive-uploadrequirements-patchdesign-patch2026-05-27

GPT Recheck After Drive Upload — IU / 4 Mothers / Event Foundation

Date: 2026-05-27 Reviewer: GPT Council via Web Connector fallback Scope: Re-read uploaded Drive-derived files + KB docs + previous council review, then decide whether Agent's design matches user requirements. Verdict: ACCEPT_AS_BASELINE_WITH_REQUIRED_REQUIREMENT_AND_DESIGN_PATCH

Sources checked

Uploaded current-session files

  • 4 mẹ mở rộng.txt — contains full handoff, 4 Mothers vision, Assembly First candidate strategy, must-not-miss checklist, OSS concerns, next-step governance.
  • Bắt sự kiện của PG(3).docx — contains event-driven architecture 5 logical layers, industry-standard queue/pub-sub/worker/realtime/DLQ concepts, open-source options, governance UI guidance, Benthos/NATS/Hasura/pg-boss/Graphile/Temporal discussion.

Google Drive folder URL was not directly fetchable in this session because Google redirected to login. Therefore, the uploaded files are treated as the accessible Drive-derived content for this review.

KB / Agent Data checked

  • knowledge/dev/requirements/iu-mow-mot-event-foundation-requirements.md
  • knowledge/dev/design/iu-mow-mot-event-foundation-design.md
  • knowledge/dev/design/law-extraction-plan-application-process-workflow-task.md
  • knowledge/dev/implementation/iu-4mothers-event-foundation-roadmap.md
  • knowledge/dev/design/assembly-first-open-source-integration-critique.md
  • knowledge/dev/reports/architecture/iu-4mothers-event-foundation-requirement-design-2026-05-27.md
  • knowledge/dev/reports/architecture/iu-4mothers-event-foundation-council-review-gpt-2026-05-27.md
  • knowledge/dev/reports/architecture/iu-4mothers-event-foundation-council-review-gpt-addendum-2026-05-27.md
  • Relevant law hits: Điều 7 Assembly First, Hiến pháp v4.6.3, Điều 45 PG-native Queue & Task Orchestration Law.

Executive verdict

Agent's rev1 design is directionally correct and should be accepted as a baseline, but it is not yet a complete official requirement/design package.

It should be patched before any implementation macro.

Do not run IU_POST_CUT_AUTOWIRE_SPLIT_MERGE_AND_EVENT_FOUNDATION_PHASE0_6000X yet.

Run a document-only patch first:

IU_4MOTHERS_EVENT_FOUNDATION_REQUIREMENT_DESIGN_PATCH_2000X

Why baseline is acceptable

The design captures the main pillars correctly:

  1. 4 Mothers: MOW / MOT / MOIT / MOUT.
  2. Event foundation: producers / broker-bus / workers-executors / realtime gateway / DLQ-recovery-governance.
  3. Assembly First: PG/DOT/registry is SoT; open-source tools are adapters only.
  4. PG-first approach: event_outbox, event_type_registry, job_queue, job_dead_letter, queue_heartbeat, workflow/task tables, DOT catalog, config gates are all reused.
  5. Future law boundary: new Điều XX — Luật Hạ tầng Ứng dụng Quy trình và Công việc is framed as a framework law, not a duplicate of IU/queue/cut/vector/Directus-Nuxt laws.
  6. Roadmap sequencing is sane: Phase 0 closes IU gaps before platform expansion.

Required patch before continuation

1. Requirement brief must be finalized before design is treated as official

User's current instruction is to complete the official requirement and design package. Therefore rev1 should be reframed:

  • Requirements = official problem statement / đầu bài for user approval.
  • Design = derived from approved requirements, not a parallel artifact.
  • Implementation roadmap = subordinate to both; no macro implementation until user approves requirement+design.

Patch requirement:

Add a front section User Approval Gate:

  • No implementation macro.
  • No law drafting.
  • No tool finalization.
  • No DB/Directus/Qdrant mutation.
  • Requirement/design patch must be reviewed first.

2. Add Old Infrastructure Coverage Matrix

Rev1 has reuse coverage, but not formal enough. Add a matrix mapping old to new:

  • IU foundation: source/domain/tree axis; compose; split/merge; trigger in/out; SQL link; post-CUT materialization.
  • Queue/event: event_outbox; event_type_registry; job_queue; job_dead_letter; queue_heartbeat; event/job distinction.
  • DOT: dot_iu_command_catalog; dot_config; config gates; DOT-pair mutation discipline.
  • Cut pipeline: MARK, VERIFY_MARK, APPROVE_VERIFY_MARK, CUT_APPROVED, VERIFY_CUT, COMPLETE, post-CUT autowire gap.
  • Directus/Nuxt: PG → Directus → Nuxt, Directus API/admin, Nuxt render shell only.
  • Vector: no cross-IU vector pollution; Qdrant is projection, no write without policy.
  • IU Fabric prior work: Assembly Contract, IU↔non-IU binding, SQL SSOT, Directus boundary, Text-as-Code upgrade feedback, split/merge/supersede model.

3. Add Constitution and Law Clause Matrix

Rev1 lists constraints but does not prove clause-by-clause review.

Add a matrix:

  • Source law / principle.
  • Binding requirement.
  • Where design satisfies it.
  • Remaining risk.
  • Sentinel test.

Must include at least:

  • Hiến pháp v4.6.3: PG-first, native/config-driven, DOT pair, five-layer sync.
  • Điều 7 Assembly First.
  • Điều 28 display/Nuxt boundary.
  • Điều 30 regression protection.
  • Điều 31 integrity/audit.
  • Điều 32 approval/quorum.
  • Điều 33 PostgreSQL / 3-layer / Directus-Nuxt path.
  • Điều 35 DOT governance.
  • Điều 37 governance organization.
  • Điều 38/39 IU/Text-as-Code/Knowledge Graph.
  • Điều 45 queue/event/task orchestration: §6.6 event vs job, §6.7 minimum work state machine, §11.5 executor boundary, §15.5 heartbeat caller obligation.
  • Điều 34 draft decision path.

4. Add PG Maximization Map

Patch must explicitly lock PG as SSOT for:

  • event_outbox as canonical event ledger.
  • event_type_registry + JSON schema registry.
  • trace_id / correlation_id / parent_span_id shape.
  • idempotency registry.
  • retry policy.
  • job_dead_letter / DLQ.
  • replay ledger / dlq_replay_request.
  • governance state / proposal state.
  • workflow_registry / workflow_step_def / workflows / workflow_steps.
  • task_def / tasks / task_checkpoints.
  • field_registry / input_form_registry.
  • output_table_registry / dot_function_registry.
  • executor_class_registry.
  • DOT catalog and runtime gates.
  • audit evidence and healthcheck.

External tools must explicitly point back to PG registry rows.

5. Correct OSS decision language

Current Agent language is too final in several places. Patch must classify tool decisions as:

  • confirmed_invariant
  • reject_as_core_owner
  • reject_as_primary_substrate_now
  • defer_until_profile_trigger
  • future_adapter_slot_preserved
  • sandbox/reference_only
  • not_a_second_SoT

Specific corrections:

pg-boss / Graphile Worker

Do not say “reject forever”. Say:

  • Not canonical queue substrate now because Điều 45 state machine is authoritative.
  • Keep as pattern reference and possible adapter/library slot if adapter mapping proves safe.
  • Any adapter must map to Điều 45 canonical lifecycle and PG remains SoT.

Temporal / Camunda / Airflow

  • Reject as primary orchestrator owner.
  • Preserve future execution-backend-adapter slot under MOW ownership.
  • Temporal can be reconsidered after Phase 6 if deterministic replay, cross-host orchestration, or >100k active long-running workflows prove native MOW insufficient.
  • Camunda should not own approval because Điều 32 governs approval; at most sandbox/reference or adapter after Council review.
  • Airflow remains wrong paradigm for business workflow; possible later only for batch/data workflows, not MOW core.

Benthos / Redpanda Connect

  • Not domain-event SoT.
  • Valid bounded uses: external table mirroring, high-volume CDC, config-driven change capture when PG trigger/outbox pattern becomes too heavy.
  • Must bridge through register-before-emit; no event taxonomy outside event_type_registry.

NATS / Redis Streams

  • NATS is transport, not SoT; only if multi-host/fanout profile demands.
  • Redis Streams only if Redis is already operational or has independent justification; PG audit remains canonical.

Hasura / Directus realtime

  • Reject as core owner / direct app realtime path.
  • Hasura can be a reference/sandbox idea only if it does not bypass Directus/Nuxt boundary or create second SoT.
  • Directus realtime may be allowed only for limited admin diagnostics if separately approved, never as user-facing governance event plane.

Watermill

  • Not needed now.
  • Keep only as future Go routing library pattern if routing complexity emerges.

6. Reconcile Bắt sự kiện của PG document

Agent report said the doc was not found in Drive. User has now uploaded it.

Patch must cite/reconcile the doc and update Event 5-layer with these exact lessons:

  • Producers only produce events; no business execution logic.
  • Broker/Event Bus is not the same as job queue.
  • Workers consume and execute; queue does not run scripts by itself.
  • Nuxt must never connect directly to core queue.
  • Realtime gateway is mandatory for safe UI push.
  • DLQ/retry/replay/poison isolation are mandatory.
  • ACK/NACK, timeout, idempotency, and replay are part of consumption, not optional extras.
  • Schema Registry and distributed tracing are governance primitives.
  • Governance UI shows exceptions, summary counts, concise worker/AI status, drill-down; not raw noise.

7. Fix SSE gateway boundary

Rev1 says Nuxt server-route SSE reads outbox tail via LISTEN/NOTIFY. This is risky wording.

Patch to:

  • Nuxt server route may host a lightweight SSE endpoint only as a gateway shell.
  • It must not become direct reader/owner of core queue semantics.
  • It reads a governed realtime projection or calls a backend gateway abstraction.
  • Permission filtering happens backend-side before event leaves trusted boundary.
  • UI receives summaries/deltas, not raw event stream.

8. Add official completeness checklist

The requirement/design must include a checklist that explicitly verifies:

  • 4 Mothers: MOW, MOT, MOIT, MOUT.
  • Event 5 layers.
  • Assembly First.
  • Business hierarchy: Task, Nhiệm vụ, Chuyên môn, Phòng ban, Công ty, Lĩnh vực.
  • JFT: right task, right person/agent, right time, deadline, escalation.
  • Trigger types: time schedule, previous output, manual human, composite AND/OR.
  • MOW UI: normal mode, proposal mode, add/edit/delete, governance queue, backend permission filter, same UI pattern across roles.
  • MOT layout: header, MOIT input, MOUT reference, instruction, metadata/state/deadline/escalation.
  • MOIT: approved field registry, direct vs staging/queue by config, no rogue form.
  • MOUT: read-only output/reference/report, live data, realtime gateway, permission filter.
  • Governance UI: problems only, aggregate counts, AI/worker concise status, drill-down, DLQ replay/rescue.
  • Scale: millions of docs/IUs, tens of thousands workflows, hundreds of thousands tasks, 2–3 step workflows, 100+ step workflows, year-long workflows, nested subworkflow.
  • IU compatibility: source/domain/tree axis, compose, split/merge with review, trigger in/out, SQL link, event hooks, post-CUT materialization.

9. Add open decisions register

Required open decisions before implementation:

  1. Điều 34: promote workflow law vs merge/archive into new framework law.
  2. Generic proposal table vs per-domain proposal tables.
  3. executor_class_registry: owned by Điều XX or cross-referenced with Điều 45.
  4. Realtime gateway implementation: Nuxt route SSE shell vs separate Node gateway vs Centrifugo later.
  5. CDC threshold: when to adopt Benthos/NATS.
  6. Temporal/Camunda re-evaluation trigger.
  7. review_decision schema ownership for split/merge.
  8. Source of truth for event schema JSON: event_type_registry shape and compatibility modes.

Run a document-only patch macro:

IU_4MOTHERS_EVENT_FOUNDATION_REQUIREMENT_DESIGN_PATCH_2000X

Must produce:

  1. Patched requirement brief rev2.
  2. Patched master design rev2.
  3. Patched OSS critique rev2.
  4. Patch report with matrix of changes and explicit User Approval Gate.

Forbidden:

  • No PG mutation.
  • No Directus mutation.
  • No Qdrant/vector work.
  • No law enactment.
  • No implementation macro.
  • No final OSS tool selection.

Final decision

Agent designed the direction correctly, but not yet complete enough for seamless continuation into implementation.

We should now complete the official requirement and design package first, then user reviews/approves, then Phase 0 implementation can proceed.

Back to Knowledge Hub knowledge/dev/reports/architecture/iu-4mothers-event-foundation-gpt-recheck-after-drive-upload-2026-05-27.md