liveBook · Manning

Intervention

As explained in Architecting for Autonomy

A deliberate runtime control that allows authorized parties or systems to interrupt, restrict, or redirect automated behavior.

Intervention is deliberate runtime control that lets authorized parties or systems interrupt, restrict, or redirect automated behavior. It matters when legacy automation repeats a failed action, such as retrying a blocked payment thousands of times or continuously calling an unavailable service. Rate limits constrain repetition; kill switches can block new actions, revoke tool access, cancel safe in-flight work, or isolate a workflow. Completed actions require separate compensating or recovery actions. section 1.3

A credible intervention boundary transfers control safely when confidence narrows, constraints fail, or conditions change. The design must specify what triggers transfer, where control goes, what context and authority move with it, and what happens if escalation fails or is delayed. section 2.1.5

Operational intervention requires explicit decisions about:

  • Authority boundaries and policy checks that determine when autonomous action remains legitimate. section 2.2
  • Thresholds, escalation triggers, rate limits, hard stops, and observable decision boundaries. section 1.3 section 2.2
  • Named ownership for escalation, intervention, and ongoing stewardship of delegated authority. section 4.6

Containing a runaway payment workflow

When a workflow repeatedly retries a blocked payment, a rate limit constrains further attempts. A broader kill switch can block new actions, revoke tool access, cancel safe in-flight work, or isolate the workflow. Any payment already completed needs a separately designed compensating or recovery action. section 1.3

Intervention makes bounded autonomy governable rather than merely permissive. Architects define the supervised decision space, while operations handle runtime events; accountability remains with the named business owner, and authority must be reviewed so it does not silently expand. section 2.2 section 4.6

How Architecting for Autonomy covers it

How deep it goes
Defines triggers, destinations, context, authority, and failure handling, while deferring completed-action recovery to separate mechanisms.
Examples
Uses blocked-payment retries, unavailable services, kill switches, workflow isolation, and safe human handover as concrete cases.
What it assumes
Assumes delegated autonomy and authority boundaries, while clarifying how systems transfer control when autonomous limits are reached.
What you can do after
Build it from scratch by defining runtime controls, transfer triggers, receiving authority, escalation ownership, and recovery boundaries.
How it connects
Connects bounded autonomy with runtime policy enforcement, rate limits, kill switches, escalation, human oversight, and delegated authority.

Also explained in

Compare how 3 books explain intervention →

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Architecting for Autonomy. The section links point to the parts of the book it draws on.