SuperBizAgent-java/openspec/changes/archive/2026-07-17-chat-diagnosis-stategraph-real-nodes/specs/chat-diagnosis-stategraph-routing-skeleton/spec.md

MODIFIED Requirements

Requirement: Verifier routing SHALL separate technical retry from evidence retry

Verifier INVALID_OUTPUT and RETRYABLE_FAILED SHALL self-retry once with the same verified input. COMPLETED PASS or REJECT SHALL route to Composer. COMPLETED LOW_CONFID SHALL route to one Evidence Retry only when all frozen guards are true, including at least one critical evidence gap; otherwise it SHALL route to Composer. Other outcomes SHALL fail closed.

Scenario: Verifier first technical failure

• WHEN Verifier first returns INVALID_OUTPUT or RETRYABLE_FAILED
• THEN only Verifier SHALL run again
• AND Gatekeeper, Executor, and tools SHALL NOT rerun

Scenario: Verifier retry is exhausted

• WHEN Verifier returns a technical failure after verifier_retry_count=1
• THEN the Graph SHALL route to Fallback

Scenario: Verifier verdict reaches Composer

• WHEN Verifier completes with effective PASS or REJECT
• THEN Composer SHALL run

Scenario: LOW_CONFID qualifies for evidence retry

• WHEN Verifier completes LOW_CONFID with ceiling PASS, at least one fact having is_critical=true and verification no_evidence or indirect_support, and evidence_retry_count=0
• THEN Evidence Retry SHALL run once and return to a new Planner stage
• AND planner_retry_count SHALL reset to 0
• AND evidence_retry_count SHALL become 1

Scenario: LOW_CONFID does not qualify for evidence retry

• WHEN ceiling is LOW_CONFID, facts contain no critical valid gap, or evidence retry count is already 1
• THEN Composer SHALL run without another Planner cycle