H∞P Training module
Refusal as Architecture
Designing systems that can fail safely. Negative power only.
Appears in tracks
Training module
What this module teaches
Refusal is designed as a system capacity: narrowly scoped negative power that blocks unsafe continuation and forces human re-entry.
Participants learn
- Why alerts are not enough when systems need halt authority.
- How negative power differs from automated action.
- How to define refusal triggers without creating arbitrary vetoes.
Practice work
- Identify where a workflow currently cannot stop.
- Draft a refusal trigger and required re-entry path.
- Name who can override and how that override is logged.
Outputs
- Refusal trigger map
- Human re-entry rule
- Override accountability note
Visual prompts
Recognise the failure pattern.
Escaping the sponge
A visual bridge from symbolic oversight to real pause, refusal, and accountable intervention.
Related materials
Open the supporting assets.
Deeper practice
How this module can expand in a workshop
Long-form teaching material should consolidate watchdog paradox, architecture of refusal, and Calvin Convention refusal clauses.
In a live session this can become exercises, review prompts, templates, and team-specific examples.