Capacity-Return vs. Liability Sponge
Interactive model of the capacity-return test: set the automation smoothing, the disagreement allowed, and the interrupt pathway, then watch what six months does to judgment and liability. Resolves the interrupt into three bands — declared, working, used — because a control can function perfectly and still fall out of use.
Capacity-Return vs. Liability Sponge
Adjust the architectural governance parameters below to see how they impact system throughput, human judgment, and overall liability risk over a 6-month operational cycle.
Operator Interrupt Pathway
A control can be declared, work perfectly, and still never be exercised. These four settings resolve into three bands: declared, working, used.
Formal authority and a documented control exist.
The operator can reach it inside the decision window without exceptional access.
The command actually suspends downstream execution and cannot be silently bypassed.
The system reaches a safe state, and the operator can act without retaliation or impossible recovery work.
Month 6 Throughput
Month 6 Judgment
Month 6 Liability Risk
Month 6 Interrupt Use
A companion model to the Capacity-Return Test in Humans in the H∞P, the consolidation of the Humane Loop arc.