Architecture
Failure and Revocation
When a session does not open, closes, or requires a new decision.
This page describes how failure states move between architecture planes. User steps and active-session closure behavior belong to Revocation and evidence.
Failure classes
| Class | Source plane | Architecture result |
|---|---|---|
| Identity or assignment mismatch | Control plane | Launch remains closed. |
| Stale, offline, or quarantined resource | Resource/agent plane | Readiness produces an unusable state. |
| Expired or target-mismatched session context | Session gateway | The work surface stays closed. |
| Conflicting active session | Control plane and session gateway | New launch returns a conflict result. |
| Connection loss during active work | Session gateway | The session moves into closure. |
| Termination dispatch failure | Session gateway | Request and result remain separate events. |
State propagation
A closed result from one plane is not widened by the next plane. When readiness is unsuitable, the control plane keeps launch closed. Without an opened decision, the session gateway creates no work surface. The evidence plane links the closure result to the relevant session.
Retry
A retry creates a new decision from current readiness, assignment, and session state. A past successful session carries no authority into a new launch. Offline resources, session conflicts, and termination-delivery errors remain distinct operator-visible states.
This page covers cross-plane propagation only. User steps for active-session closure, retry, and escalation live in Revocation and evidence; symptom-based checks live in Connection troubleshooting.
Review trail
Architecture review reads decision time, readiness time, session state, termination request, and received result under the same session identity. Evidence plane defines the evidence boundary.