Kill Switch / Circuit Breaker

Kill Switch / Circuit Breaker An architecture diagram generated by Archify. Guardrail events · flagged calls · Layer 04 Runtime Controls & Observability Guardrail events flagged calls Telemetry · anomaly, threshold · Layer 04 Runtime Controls & Observability Telemetry anomaly, threshold Circuit breaker · tool-call boundary · Layer 04 Runtime Controls & Observability · auto or manual Circuit breaker tool-call boundary auto or manual Agent A · scope revoked · Layer 04 Runtime Controls & Observability Agent A scope revoked Agent B · runs on · Layer 04 Runtime Controls & Observability Agent B runs on Agent C · runs on · Layer 04 Runtime Controls & Observability Agent C runs on Incident record · trip logged · Layer 05 Assurance & Continuous Compliance Incident record trip logged signal revoke scope trip = evidence Layer 04 Runtime Controls & Observability Layer 05 Assurance & Continuous Compliance Legend Backend Database Security External

Autonomy is withdrawable

  • • The breaker sits at the tool-call boundary
  • • It trips on a threshold breach, an anomaly, or a manual pull
  • • An untested kill switch is not a control

Contained to one agent

  • • Each agent is bound to its own identity, so scope is revoked per agent
  • • Revocation halts that agent's tool calls while the fleet keeps running

First step

  • • Design the breaker per agent scope before you need it
  • • Test the trip on a schedule, in staging