Kumoss request flow · Phases 1-4

Kumoss request flow · Phases 1-4 A sequence diagram generated by Archify. 1 · Describe infrastructure in natural language (wizard) 2 · Validate OIDC bearer JWT (or dev identity) · role at least developer 3 · 401 / 403 on failure — request stops 4 · Cloud-project preflight (authz sidecar, disabled by default, so authorized without a call) 5 · git ls-remote on repository 6 · 400 if unreachable — request stops 7 · Create / resolve user-owned session · 202 + session id 8 · SSE progress stream starts 9 · Acquire in-flight guard (PostgreSQL CAS) 10 · Clone repo into ephemeral workspace · start tracing 11 · Request Filter Agent — is the request acceptable? (status FILTERING) 12a · [not acceptable] rationale, session UNCOMPLETED 13a · [not acceptable] reformulate the request 12b · [acceptable] Prompt Compositor — pick relevant templates, conventions, guidelines (Phoenix) PHASE 1-2 · Request, identity, session PHASE 3-4 · Filter and compose (small model) 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 default message