Kumoss request flow · Phase 10

Kumoss request flow · Phase 10 A sequence diagram generated by Archify. 41 · POST /iac/apply — explicit human action 42 · authenticated · developer role · owner · not blocked, so 202 accepted 43 · 401 / 403 / 409 if locked — answered before the 202 44 · after 202: guard busy means the runner logs and exits · no pinned plan means session FAILED 45 · IaC sidecar runs ONE apply of the pinned plan (no re-plan, no retry) 46a · [success] applied the cloud reaches the requested state 47a · [success] Report Generator produces the apply report 48a · [success] Infrastructure applied · session COMPLETED · the cloud reaches the requested state 46b · [failure] Report Generator produces the apply failure report 47b · [failure] iac.apply.failure to Slack 48b · [failure] session COMPLETED, apply report Failed · no retry · a new generate round is needed 49 · pinned plan discarded · workspace cleaned · in-flight guard released (finally) PHASE 10 · Human-triggered apply — never automatic User / reviewer · Sequence participant User / reviewer Web UI + Core API · Sequence participant Web UI + Core API Control gates · Sequence participant Control gates LLM agents · Sequence participant LLM agents core-db · Sequence participant core-db External · Sequence participant External Legend return security async trace default message