Multi-Agent Quality Gate | Scenario Switcher

Six roles review one release candidate in order. Switch tabs to see how four synthetic data sets reach different conclusions through the same flow.

Recommended decision

Go | release recommended

QA summary

Ready (recommendation; client decides)

Conclusion

Go recommended, pending client decision

Go / Scoped Go always needs a decision by an authorized client person; agents cannot approve.

Release candidate：RC-101｜demo-shop v2.3.0｜staging-demo｜round 1

State diagram (this scenario's path)

★ dark node + thick solid line = this path; ◆ = where it ends; dashed = transitions not taken.

Six gate results and reasons

Gate	Result	Reason
G1 Change Collector R-COLLECTOR	Pass	Target, full SHA and change list complete
G2 Readiness Checker R-READINESS	Pass	All paths ready
G3 Evidence Reviewer R-EVIDENCE	Pass	SC-01 has valid evidence for this build
G4 Contrarian Reviewer R-CONTRARIAN	Pass	No evidence-backed objections
G5 Risk Gatekeeper R-RISK	Pass	No S1, no open S2, no critical-path Fail
G6 Aggregator R-AGGREGATOR	Pass	G1–G5 all pass and exit criteria met → T-12

LegendPassConcernBlockVetoNot reached

Gate status ≠ Run status：A gate's "Block / Rejected" is a gate result, not the Run status Blocked. Not Run / Skipped apply only to Runs, never to gates.

Four-row summary

Known issues

None

Execution completeness

Pass 3 / Fail 0 / Blocked 0 / Not Run 0 / Skipped 0 (denominator 3)

Exit criteria decision

c1 ✓　c2 ✓　c3 ✓

✓ met

c1 critical path has valid evidence for this build; c2 no unresolved S1, and S2 fixed and retested or risk-accepted; c3 every traced item has a result or a stated untested reason.

Untested

None

Defects Severity definitions: Draft

No defects in this scenario.

Runs

Run	Case	Status
RUN-101	TC-01 ★Critical path	Pass
RUN-102	TC-02	Pass
RUN-103	TC-03	Pass

Execution completeness：Pass 3 / Fail 0 / Blocked 0 / Not Run 0 / Skipped 0 (denominator 3)

Activity log｜RC-101

Filter by gate

ID	Time (Taipei)	Gate	Action	Result	Transition	Message
LOG-001	10:00	G1 R-COLLECTOR	start			G1 check started
LOG-002	10:05	G1 R-COLLECTOR	transition	Pass	T-01 S-G1 → S-G2	Target, full SHA and change list complete
LOG-003	10:10	G2 R-READINESS	start			G2 check started
LOG-004	10:15	G2 R-READINESS	transition	Pass	T-03 S-G2 → S-G3	All paths ready
LOG-005	10:20	G3 R-EVIDENCE	start			G3 check started
LOG-006	10:25	G3 R-EVIDENCE	transition	Pass	T-05 S-G3 → S-G4	SC-01 has valid evidence for this build
LOG-007	10:30	G4 R-CONTRARIAN	start			G4 check started
LOG-008	10:35	G4 R-CONTRARIAN	transition	Pass	T-07 S-G4 → S-G5	No evidence-backed objections
LOG-009	10:40	G5 R-RISK	transition	Pass	T-09 S-G5 → S-G6	No S1, no open S2, no critical-path Fail
LOG-010	10:45	G6 R-AGGREGATOR	start			Aggregation started
LOG-011	10:50	G6 R-AGGREGATOR	check			Building four-row summary and checking conflicts
LOG-012	10:55	G6 R-AGGREGATOR	transition	Pass	T-12 S-G6 → S-GO	G1–G5 all pass and exit criteria met → T-12

Recommended decision

Scoped Go | reduced-scope release recommended (excluding REQ-03)

QA summary

At Risk

Conclusion

Scoped Go recommended, pending client decision

Go / Scoped Go always needs a decision by an authorized client person; agents cannot approve.

Release candidate：RC-102｜demo-shop v2.3.0｜staging-demo｜round 1

State diagram (this scenario's path)

★ dark node + thick solid line = this path; ◆ = where it ends; dashed = transitions not taken.

Six gate results and reasons

Gate	Result	Reason
G1 Change Collector R-COLLECTOR	Pass	Target, full SHA and change list complete
G2 Readiness Checker R-READINESS	Concern	TC-03 sample account not ready (non-critical path)
G3 Evidence Reviewer R-EVIDENCE	Pass	SC-01 has valid evidence for this build
G4 Contrarian Reviewer R-CONTRARIAN	Concern	DEF-001 (S2) and TC-03 is Blocked
G5 Risk Gatekeeper R-RISK	Pass	No S1; DEF-001 (S2) has client risk acceptance
G6 Aggregator R-AGGREGATOR	Pass	Concerns resolved by risk acceptance (all four fields) and excluded scope REQ-03 → T-11

LegendPassConcernBlockVetoNot reached

Gate status ≠ Run status：A gate's "Block / Rejected" is a gate result, not the Run status Blocked. Not Run / Skipped apply only to Runs, never to gates.

Four-row summary

Known issues

Fail 1 (DEF-001, non-critical path REQ-03)

Execution completeness

Pass 1 / Fail 1 / Blocked 1 / Not Run 0 / Skipped 0 (denominator 3)

Exit criteria decision

c1 ✓　c2 ✓　c3 ✓

✓ met

c1 critical path has valid evidence for this build; c2 no unresolved S1, and S2 fixed and retested or risk-accepted; c3 every traced item has a result or a stated untested reason.

Untested

TC-03 (Blocked: sample account; step S1 done; resume when account is provided)

Defects Severity definitions: Draft

DEF-001｜Report export column order is wrong (fictional sample defect)

Final severity: S2
QA suggestion／Client ruling: S2／S2
Status: Deferred
Fix priority: next-release
REQ: REQ-03

Risk acceptance

Decider: demo-client-owner
Reason: Export is not enabled in this release
Owner: demo-pm
Review date: 2026-11-09

Runs

Run	Case	Status	Notes
RUN-201	TC-01 ★Critical path	Pass
RUN-202	TC-02	Fail	DEF-001
RUN-203	TC-03	Blocked	Step S1 done; sample account not ready; resume when provided

Execution completeness：Pass 1 / Fail 1 / Blocked 1 / Not Run 0 / Skipped 0 (denominator 3)

Activity log｜RC-102

Filter by gate

ID	Time (Taipei)	Gate	Action	Result	Transition	Message
LOG-001	10:00	G1 R-COLLECTOR	start			G1 check started
LOG-002	10:05	G1 R-COLLECTOR	transition	Pass	T-01 S-G1 → S-G2	Target, full SHA and change list complete
LOG-003	10:10	G2 R-READINESS	start			G2 check started
LOG-004	10:15	G2 R-READINESS	transition	Concern	T-03 S-G2 → S-G3	TC-03 sample account not ready (non-critical path)
LOG-005	10:20	G3 R-EVIDENCE	start			G3 check started
LOG-006	10:25	G3 R-EVIDENCE	transition	Pass	T-05 S-G3 → S-G4	SC-01 has valid evidence for this build
LOG-007	10:30	G4 R-CONTRARIAN	start			G4 check started
LOG-008	10:35	G4 R-CONTRARIAN	transition	Concern	T-07 S-G4 → S-G5	DEF-001 (S2) and TC-03 is Blocked
LOG-009	10:40	G5 R-RISK	transition	Pass	T-09 S-G5 → S-G6	No S1; DEF-001 (S2) has client risk acceptance
LOG-010	10:45	G6 R-AGGREGATOR	start			Aggregation started
LOG-011	10:50	G6 R-AGGREGATOR	check			Building four-row summary and checking conflicts
LOG-012	10:55	G6 R-AGGREGATOR	transition	Pass	T-11 S-G6 → S-SGO	Concerns resolved by risk acceptance (all four fields) and excluded scope REQ-03 → T-11

Recommended decision

Hold | waiting

QA summary

Unknown

Conclusion

Not yet up for decision: waiting for unblock conditions (a new round starts once cleared)

ⓘ Unknown here only because evidence is missing and no defect is confirmed. Not general: a blocked critical path means Blocked, and a confirmed Fail can never be Unknown.

Stopped at: G3 Evidence Reviewer
Transition: T-06
Reason: SC-01 evidence is from an old SHA; cannot be judged yet. Unblock: retest on the new SHA.

⚑ This is a recommended conclusion, not the client's decision.

Release candidate：RC-103｜demo-shop v2.3.0｜staging-demo｜round 1

State diagram (this scenario's path)

★ dark node + thick solid line = this path; ◆ = where it ends; dashed = transitions not taken.

Six gate results and reasons

Gate	Result	Reason
G1 Change Collector R-COLLECTOR	Pass	Target, full SHA and change list complete
G2 Readiness Checker R-READINESS	Pass	Critical path ready
G3 Evidence Reviewer R-EVIDENCE	Rejected: evidence is from an old SHA	SC-01 evidence is from an old SHA and cannot count as completion evidence; unblock: retest on the new SHA
G4 Contrarian Reviewer R-CONTRARIAN	Not reached	Flow stopped at an earlier gate
G5 Risk Gatekeeper R-RISK	Not reached	Flow stopped at an earlier gate
G6 Aggregator R-AGGREGATOR	Not reached	Flow stopped at an earlier gate

LegendPassConcernBlockVetoNot reached

Gate status ≠ Run status：A gate's "Block / Rejected" is a gate result, not the Run status Blocked. Not Run / Skipped apply only to Runs, never to gates.

Four-row summary

Known issues

No confirmed defects; SC-01 evidence is from an old SHA, cannot be judged yet

Execution completeness

Pass 2 / Fail 0 / Blocked 0 / Not Run 1 / Skipped 0 (denominator 3)

Exit criteria decision

c1 ✕　c2 —　c3 ✓

c2 — (cannot be judged yet)

✕ not met

c1 critical path has valid evidence for this build; c2 no unresolved S1, and S2 fixed and retested or risk-accepted; c3 every traced item has a result or a stated untested reason.

Untested

TC-03 (Not Run); SC-01 needs a retest on the new SHA

Defects Severity definitions: Draft

No defects in this scenario.

Runs

Run	Case	Status	Notes
RUN-301	TC-01 ★Critical path	Pass	Evidence from an old SHA; not valid for this build
RUN-302	TC-02	Pass
RUN-303	TC-03	Not Run	To be run with the new-SHA retest

Execution completeness：Pass 2 / Fail 0 / Blocked 0 / Not Run 1 / Skipped 0 (denominator 3)

Activity log｜RC-103

Filter by gate

ID	Time (Taipei)	Gate	Action	Result	Transition	Message
LOG-001	10:00	G1 R-COLLECTOR	start			G1 check started
LOG-002	10:05	G1 R-COLLECTOR	transition	Pass	T-01 S-G1 → S-G2	Target, full SHA and change list complete
LOG-003	10:10	G2 R-READINESS	start			G2 check started
LOG-004	10:15	G2 R-READINESS	transition	Pass	T-03 S-G2 → S-G3	Critical path ready
LOG-005	10:20	G3 R-EVIDENCE	start			G3 check started
LOG-006	10:25	G3 R-EVIDENCE	transition	Block	T-06 S-G3 → S-HOLD	SC-01 evidence is from an old SHA and cannot count as completion evidence; unblock: retest on the new SHA

Recommended decision

No-Go | do not release

QA summary

Blocked

Conclusion

Terminate this release candidate (unresolved S1; no Go recommendation allowed). After fixing, resubmit as a new candidate or new SHA.

Stopped at: G5 Risk Gatekeeper
Transition: T-08
Reason: Unresolved S1: DEF-002 (fictional sample defect), which also fails critical-path TC-01; meets veto conditions (a) and (c).

⚑ This is a recommended conclusion, not the client's decision.

Release candidate：RC-104｜demo-shop v2.3.0｜staging-demo｜round 1

State diagram (this scenario's path)

★ dark node + thick solid line = this path; ◆ = where it ends; dashed = transitions not taken.

Six gate results and reasons

Gate	Result	Reason
G1 Change Collector R-COLLECTOR	Pass	Target, full SHA and change list complete
G2 Readiness Checker R-READINESS	Pass	Critical path ready
G3 Evidence Reviewer R-EVIDENCE	Pass	SC-01 has valid evidence for this build (result: Fail)
G4 Contrarian Reviewer R-CONTRARIAN	Concern	DEF-002 (fictional sample defect): main checkout flow unusable
G5 Risk Gatekeeper R-RISK	Veto	Unresolved S1 DEF-002 (fictional sample defect) → veto
G6 Aggregator R-AGGREGATOR	Not reached	Flow stopped at an earlier gate

LegendPassConcernBlockVetoNot reached

Gate status ≠ Run status：A gate's "Block / Rejected" is a gate result, not the Run status Blocked. Not Run / Skipped apply only to Runs, never to gates.

Four-row summary

Known issues

DEF-002 (S1, unresolved) (fictional sample defect)

Execution completeness

Pass 2 / Fail 1 / Blocked 0 / Not Run 0 / Skipped 0 (denominator 3)

Exit criteria decision

c1 ✓　c2 ✕　c3 ✓

✕ not met

c1 critical path has valid evidence for this build; c2 no unresolved S1, and S2 fixed and retested or risk-accepted; c3 every traced item has a result or a stated untested reason.

Untested

None

Defects Severity definitions: Draft

DEF-002｜Checkout submit does not respond (fictional sample defect)

Final severity: S1
QA suggestion／Client ruling: S1／S1
Status: New
Fix priority: Highest
REQ: REQ-01 (Critical path)

Risk acceptance

None

Runs

Run	Case	Status	Notes
RUN-401	TC-01 ★Critical path	Fail	DEF-002
RUN-402	TC-02	Pass
RUN-403	TC-03	Pass

Execution completeness：Pass 2 / Fail 1 / Blocked 0 / Not Run 0 / Skipped 0 (denominator 3)

Activity log｜RC-104

Filter by gate

ID	Time (Taipei)	Gate	Action	Result	Transition	Message
LOG-001	10:00	G1 R-COLLECTOR	start			G1 check started
LOG-002	10:05	G1 R-COLLECTOR	transition	Pass	T-01 S-G1 → S-G2	Target, full SHA and change list complete
LOG-003	10:10	G2 R-READINESS	start			G2 check started
LOG-004	10:15	G2 R-READINESS	transition	Pass	T-03 S-G2 → S-G3	Critical path ready
LOG-005	10:20	G3 R-EVIDENCE	start			G3 check started
LOG-006	10:25	G3 R-EVIDENCE	transition	Pass	T-05 S-G3 → S-G4	SC-01 has valid evidence for this build (result: Fail)
LOG-007	10:30	G4 R-CONTRARIAN	start			G4 check started
LOG-008	10:35	G4 R-CONTRARIAN	transition	Concern	T-07 S-G4 → S-G5	DEF-002 (fictional sample defect): main checkout flow unusable
LOG-009	10:40	G5 R-RISK	transition	Veto	T-08 S-G5 → S-NOGO	Unresolved S1 DEF-002 (fictional sample defect) → veto

Severity definitions Draft

S1 Critical: The critical path is unusable with no workaround; or data corruption/loss, payment or points errors (double charges, points deducted), or a security or privacy leak. These three categories are always S1, regardless of whether a workaround exists or a refund can remedy it afterward. Representative cases: cannot log in or complete payment; task data overwritten and lost; other people’s data leaked
S2 Major: A main feature is broken or gives wrong results; a difficult workaround exists. Representative cases: report values miscalculated but can be recalculated manually; a main flow can only be completed via a detour
S3 Minor: A secondary feature or boundary error; a simple workaround exists. Representative cases: wrong boundary value in a filter condition; incorrect validation message on a secondary field
S4 Trivial: Text, layout, or appearance; does not affect functionality. Representative cases: typos, misalignment, inconsistent colors

Deferring a fix does not lower severity; QA suggestions and client rulings are recorded separately.