Explainer

What is Stoppability?

Stoppability explains the right to halt automated processes and protect people from forced tunnels.

Glossary anchor

Stoppability

Connect the explainer to the canonical definition for citations and shared language.

Open glossary entry

Definition

Short definition

Two-to-four sentences you can drop into briefs or specs.

Stoppability is the requirement that people can halt an automated process instantly without losing their place or facing penalties. It centers on visible stop controls, state preservation, and the ability to walk away without retribution.

Teams use stoppability to prevent forced tunnels and to prove that systems respect human time and agency.

Example

Example use case

A concrete scenario to ground the term in operations.

A loan application flow includes a persistent “Stop and resume later” control that saves progress, issues a receipt, and confirms the application will not be penalized for pausing.

Implementation

Distinct implementation signals

Unique operational detail to help this concept stand on its own in policy, procurement, and review workflows.

Stop-control criteria

Require always-visible halt controls, no-penalty pause paths, and resumable state snapshots across every critical journey.

Common failure pattern

Flows claim stoppability but invalidate progress after pause; test resume behavior under network loss and session expiry.

Evidence to ship

Share stop-request volumes, successful resume rates, and audit logs proving no punitive flags were attached after halts.

CTAs

Related artifacts

Standards, bindings, and evidence packs to move from concept to adoption.

Standard

STD-01 — The Temporal Bill of Rights

See how Stoppability anchors Article I and the surrounding temporal rights.

Read STD-01

Binding

Binding vectors

Copy procurement and release gates that enforce stoppability controls.

View binding vectors

Evidence pack

STD-01 evidence pack

Collect receipts, UI proofs, and logs that validate stoppability compliance.

Open evidence pack

FAQ

Quick answers

Short replies for common implementation questions.

How is stoppability different from cancellation?

Cancellation ends a process, while stoppability ensures people can pause or halt it immediately without losing state or being penalized for stopping.

What evidence demonstrates stoppability?

UI recordings of the halt control, event logs showing immediate cessation, and receipts proving state preservation are the core proofs.