Stop-control criteria
Require always-visible halt controls, no-penalty pause paths, and resumable state snapshots across every critical journey.
Stoppability explains the right to halt automated processes and protect people from forced tunnels.
Glossary anchor
Connect the explainer to the canonical definition for citations and shared language.
Jump to
Key sections
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.
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
Unique operational detail to help this concept stand on its own in policy, procurement, and review workflows.
Require always-visible halt controls, no-penalty pause paths, and resumable state snapshots across every critical journey.
Flows claim stoppability but invalidate progress after pause; test resume behavior under network loss and session expiry.
Share stop-request volumes, successful resume rates, and audit logs proving no punitive flags were attached after halts.
Standard
See how Stoppability anchors Article I and the surrounding temporal rights.
Binding
Copy procurement and release gates that enforce stoppability controls.
Evidence pack
Collect receipts, UI proofs, and logs that validate stoppability compliance.
Cancellation ends a process, while stoppability ensures people can pause or halt it immediately without losing state or being penalized for stopping.
UI recordings of the halt control, event logs showing immediate cessation, and receipts proving state preservation are the core proofs.