GPT Provisional Review — IU 4 Mothers Event Requirement Rev2

Date: 2026-05-27 Reviewer: GPT Council via Web Connector fallback Basis: Agent final summary only; actual local files not yet read because they are not ingested/uploaded to KB in this session. Files reported by Agent:

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

Verdict

LIKELY_ACCEPT_WITH_FILE_REVIEW_REQUIRED

Based on the Agent summary, the Rev2 brief appears to satisfy the main corrections requested by the user/GPT Council. However, it cannot be fully approved until the actual two markdown files are read directly.

Positive signals from Agent summary

1. IU-centered doctrine was encoded: workflow 2..500 steps assembled from IU brick/bundle; no duplicate text; 4 Mothers as factories around IU.
2. Workflow UI requirement appears included: Standard Process View, Runtime Progress View, 9-state floor, traffic-light semantics, icon/text rule.
3. Governance UI problem-first requirement appears included: DLQ replay, heartbeat/silent worker, event lag.
4. Event 5-layer from Bắt sự kiện của PG(3).docx appears reconciled, including SSE gateway boundary correction so Nuxt does not read outbox/NOTIFY directly.
5. Old Infrastructure Coverage Matrix exists with 27 rows.
6. Constitution Matrix and PG Maximization Map exist.
7. OSS strategy is not final tool selection and uses labels/Gates.
8. Điều 34 is treated only as decision path, not enacted or merged.
9. Forbidden compliance appears maintained: no PG/Directus/Qdrant mutation, no migration/DOT/law/implementation/final tool pick, no KB ingest.

Required direct-file checks before approval

The next reviewer must read both files and verify:

1. Requirement vs design boundary

• Requirement Rev2 must remain requirement-first.
• Any technical schema/table/function details must be marked as design implication, not approved design.
• It must not silently approve Master Design Rev2.

2. IU-centered doctrine quality

Verify the document does not merely say iu_unit_id references exist. It must state:

• workflow step is assembled from IU or IU bundle;
• 500-step workflow uses same primitive as 2-step workflow;
• active workflows can pin IU versions;
• future workflows can use newer IU versions;
• task instruction/context/input/output avoids duplicate text/body;
• IU is reusable brick, not executor.

3. Workflow UI/state requirements

Verify the 9 states have clear definitions and traffic-light mapping:

• not_started
• ready
• in_progress
• waiting
• blocked
• overdue
• failed
• cannot_complete
• completed

Check whether waiting is too broad. It may need sublabels in the UI for waiting_dependency vs waiting_human, while the 9-state floor can stay as requirement level.

4. Event 5-layer reconciliation

Verify it explicitly includes:

• queue does not execute scripts;
• workers consume and execute;
• event bus != job queue;
• Nuxt must not read core queue/outbox directly;
• gateway/projection boundary;
• DLQ/retry/replay/poison isolation;
• ACK/NACK/timeout/idempotency;
• schema registry;
• trace_id/correlation_id;
• event payload carries refs, not heavy IU body.

5. Old infra coverage matrix quality

Verify the 27 rows do not overclaim legacy systems that were not verified. Because option 2 allowed codebase/KB traces, the matrix should distinguish:

• verified existing infrastructure;
• documented legacy trace;
• candidate/possible legacy item;
• GAP requiring survey.

Directus flows, pg_cron legacy, and signal/event_outbox legacy must not become assumptions unless evidence is cited.

6. Constitution/law matrix quality

Verify it cites and respects:

• Hiến pháp v4.6.3;
• Điều 7 Assembly First;
• Điều 28 Nuxt/display boundary;
• Điều 30 Regression;
• Điều 31 Integrity/audit;
• Điều 32 Approval;
• Điều 33 PostgreSQL/Directus/Nuxt;
• Điều 35 DOT governance;
• Điều 37 Governance organization;
• Điều 38/39 IU/KG;
• Điều 45 event/job/executor/MOT-not-executor/heartbeat;
• Điều 34 only as draft decision path.

7. PG Maximization Map quality

Verify PG is canonical SSOT for:

• event ledger;
• event schema JSON;
• trace/correlation;
• idempotency;
• retry/DLQ/replay;
• workflow/task/field/form/output/executor registries;
• DOT catalog;
• governance/audit/healthcheck.

External OSS must be adapter/transport/executor/gateway only.

8. OSS labels quality

Verify the seven labels are used to avoid final tool lock-in. pg-boss/Graphile/Temporal/Camunda/Benthos/NATS/Hasura/Directus realtime/Watermill must not be permanently rejected unless as core owner.

Potential remaining patch items

If direct file review confirms gaps, likely small patch items are:

1. Split waiting into UI sublabels while preserving 9-state floor.
2. Add status accessibility rule: color + icon + text + tooltip.
3. Add active workflow version pinning policy explicitly.
4. Add evidence level column to old infra matrix to prevent overclaim.
5. Add requirement vs design implication tag to technical rows.
6. Add User Approval Gate at top and bottom of the brief.
7. Add next step is Master Design Rev2 document-only, not implementation in patch report.

Recommendation

Do not proceed to Master Design Rev2 until one of the following happens:

• the two local files are uploaded/ingested to KB and read directly; or
• the user pastes/uploads the two markdown files into the chat for direct review.

If direct file review passes, next macro can be:

IU_4MOTHERS_EVENT_FOUNDATION_MASTER_DESIGN_REV2_DOCUMENT_ONLY_2000X

No implementation macro yet.