Agent control plane
Five agents can read charts, ask payers about members, write into clinical records and transmit authorizations. Somebody has to be able to answer, at 2am, on a phone: what are they allowed to do, what have they done, and how do I stop one right now.
#The asymmetry
#States
| State | Meaning |
|---|---|
active | Running normally. |
degraded | Running, but capped below its configured autonomy - usually a failing or stale eval suite. |
paused | Stopped by a person. |
quarantined | Stopped by a guardrail. Nobody was watching and something tripped a wire. |
The distinction between paused and quarantined matters: an operator knows why they stopped something. A guardrail stop means the condition arose unobserved.
#The fleet switch
One lever halts every agent at every practice, immediately. A fleet stop is reported as fleet_stopped, not as a permissions error - it is a platform-level halt and it should not read like a scope problem.
#Autonomy is licensed by evals
An agent may act above L1 only while a passing eval suite says it should, and the licence expires after fourteen days. A lapsed agent drops to proposing rather than stopping - losing the ability to act is not the same as losing the ability to help.
| Condition | Effect |
|---|---|
| No eval run has ever happened | Capped at L1, reason no_eval_run |
| The suite is failing | Marked degraded, capped at L1 |
| The last pass is older than 14 days | Capped at L1, reason eval_stale |
| A never-event occurred | Quarantined immediately, with nobody watching |
#Per-practice control
A practice can decline an agent the rest of the fleet runs, without contacting anyone. Other practices are unaffected.
#Reach
The first question in an incident is not what an agent was configured to do - it is what it could have touched. The console shows, per agent: whether it reads PHI, whether it can write charts, whether it transmits to payers, how many of its tools are gated, and how many ungated writes it has. That last number should always be zero.