Refusal-Tolerant Systems — Operational test: Opt-out or decline flows keep core services available without punitive delays.
Operational test "Opt-out or decline flows keep core services available without punitive delays." for Refusal-Tolerant Systems in the Ethotechnic capabilities (what systems must be able to do) glossary category.
Operational test
Opt-out or decline flows keep core services available without punitive delays.
Use this test to validate operational readiness.
Pair this test with the minimum evidence criteria to capture both qualitative and quantitative signals.
- Evidence artifact: Artifact documenting how Human Refusal-Tolerance is expected, enforced, or governed.
- Behavior signal: Observed behavior showing Human Refusal-Tolerance in practice during real use or drills.
- Metric signal: Metric tracked to monitor Human Refusal-Tolerance performance over time.
Context
How this test fits the glossary entry
Category: Ethotechnic capabilities (what systems must be able to do)
The system remains usable when people opt out, are confused, make mistakes, or withdraw cooperation. Refusal tolerance prevents extraction by endurance by treating refusal as a valid input, not a failure state. Called “human” because it protects humans from being turned into the crumple zone when they refuse.
C. Ethotechnic capabilities (what systems must be able to do). Design requirements that keep people safe when systems scale.
Centers refusal as a valid form of agency within system design.