GPT Review — IU-Centered 4 Mothers + Event Foundation Requirement Rev2

Date: 2026-05-27 Reviewer: GPT Council via Web Connector fallback Documents read directly:

• knowledge/dev/requirements/v0.6-iu-4mothers-event-foundation-rev2/00-requirement-brief-rev2.md revision 1
• knowledge/dev/requirements/v0.6-iu-4mothers-event-foundation-rev2/01-patch-report.md revision 1

Verdict

ACCEPT_WITH_MINOR_PATCHES_BEFORE_USER_APPROVAL

Requirement Rev2 substantially meets the agreed direction and is strong enough to become the baseline for Master Design Rev2 after small clarifications. It should not proceed to implementation. Master Design Rev2 remains document-only and should be started only after user accepts the requirement package or after the minor patches below are applied.

What passes

1. IU-centered doctrine is correctly elevated from reference pointer to reusable assembly substrate.
2. Workflow 2-step to 500-step requirement is explicitly stated as the same IU-backed assembly primitive.
3. No duplicate text invariant is present.
4. IU Bundle / Step Pack is included and correctly avoids over-merge.
5. MOW/MOT/MOIT/MOUT are reframed around IU.
6. Event 5-layer has been reconciled with the uploaded PG event document.
7. Realtime boundary was corrected: Nuxt server route may be SSE shell only, not direct outbox/LISTEN reader.
8. Workflow UI requirements include Standard Process View, Runtime Progress View, traffic-light semantics, icon/text labels, and governance problem-first dashboard.
9. Old Infrastructure Coverage Matrix exists and covers IU, event/queue, DOT, cut, Directus/Nuxt, vector, workflows/tasks, governance and legacy traces.
10. Constitution/Law Clause Matrix exists and includes the critical laws and Điều 45 invariants.
11. PG Maximization Map exists.
12. OSS strategy is labels-only, no final tool selection.
13. Điều 34 is limited to decision path and not enacted or merged into Điều 45/Điều 32.
14. Forbidden block is clear and preserved.

Required minor patches

MP1 — Evidence-level column for Old Infrastructure Coverage Matrix

Because the selected scope allowed Rev1 + uploaded files + codebase/KB traces, the matrix must distinguish certainty levels. Add a column:

• verified_live
• KB_reported
• legacy_trace
• candidate_requires_survey
• known_gap

This is especially required for Directus flows, pg_cron legacy, signal/event_outbox legacy, field_registry/input_form_registry/output_table_registry/dot_function_registry, and any inferred legacy objects. Without this, Rev2 risks overclaiming.

MP2 — Raw uploaded source status wording

The brief says the Drive-uploaded sources were reconciled via GPT recheck because raw files were not in Drive search. Now the session has uploaded content and Agent uploaded Rev2 to KB. Patch wording to avoid ambiguity:

• Raw source was available to the discussion via uploaded files.
• Rev2 reconciliation used GPT recheck report as the accessible consolidation source.
• If Council requires direct raw-source audit, attach/upload raw source files to KB in a separate document-only ingestion round.

Do not claim raw source was impossible to access absolutely.

MP3 — Waiting sublabels in UI requirement

The 9-state floor is correct, but waiting should require UI sublabels:

• waiting_dependency
• waiting_human
• waiting_external
• waiting_time_gate

These are sublabels/facets, not additional core states. This preserves the 9-state floor while making UI operationally clear.

MP4 — Accessibility wording for traffic-light UI

The brief says traffic-light + icon/text. Add explicit accessibility requirement:

• never rely on color alone;
• include icon, text label, tooltip/short reason;
• ensure color contrast and color-blind safe palette.

MP5 — Status roll-up principle

The brief says workflow status is roll-up from step states, details deferred. Add requirement-level roll-up principle:

• workflow cannot be green if any mandatory active step is red;
• red overrides yellow, yellow overrides green for summary status;
• skipped/not_applicable must not count as incomplete;
• roll-up rules are config-driven and finalized in Master Design Rev2.

MP6 — User approval gate final line

The brief already has User Approval Gate at the top and forbidden block at the end. Add one final line to §21:

Next macro may begin only after user explicitly approves this Requirement Rev2 or approves a minor-patch version.

Not blockers for requirement approval

These are acceptable to defer to Master Design Rev2:

• Full transition matrix for 9 states.
• Actual state_machine_registry schema.
• executor_class_registry schema.
• dlq_replay_request schema.
• idempotency_registry schema.
• Generic proposal vs per-domain proposal table.
• IU version pinning detailed policy.
• Realtime gateway concrete technology.
• Temporal/Camunda/NATS/Benthos thresholds.

Decision

Do not run implementation.

Recommended next step:

1. Apply a tiny document-only patch to Rev2 (MP1–MP6), or accept Rev2 with these as mandatory amendments for Master Design Rev2.
2. After user approval, run:

IU_4MOTHERS_EVENT_FOUNDATION_MASTER_DESIGN_REV2_DOCUMENT_ONLY_2000X

Forbidden remains:

• no PG mutation;
• no Directus mutation;
• no Qdrant/vector work;
• no migration;
• no DOT command run;
• no law enactment;
• no implementation;
• no final OSS tool selection.