HABITS Refusal Events
A Living Record of Admissibility Before Execution
These are real-world demonstrations of admissibility before execution.
Each event shows what occurs when a proposed action does not have a constructible path under real conditions.
No decision is made.
No policy is applied.
No optimisation is attempted.
→ Execution simply does not occur.
In most systems, governance is treated as something layered on after the fact.
Monitoring.
Control.
Correction.
But physical systems do not operate that way.
What cannot exist under the conditions does not persist.
Each refusal event captures a single moment:
A proposed transition meets real-world conditions.
→ Either a path exists
→ Or it does not
If it does not:
→ there is nothing to allow
→ nothing to refuse
→ nothing to execute
These are not simulations.
They are not hypothetical scenarios.
They are minimal, real-world tests showing:
→ execution ceasing to be constructible under actual conditions
Over time, this record will expand.
Not as a collection of examples,
but as a visible sequence of where:
→ reality does not support the path
→ and execution simply does not occur
The system does not resolve admissibility.
It intersects it.
HABITS Refusal Events
Refusal Event 001 — Energy
The First Boundary Hold
A non-critical AI task was submitted for execution.
Using live grid data from New South Wales:
→ Carbon intensity: 651 gCO₂/kWh
→ Threshold: 400 gCO₂/kWh
→ Time: 25 Apr 2026, 19:15 (GMT+10)
The task did not run.
Not because it was blocked.
Not because a policy rejected it.
Not because a system decided against it.
→ No executable path existed under the conditions.
At the moment of execution:
→ either the conditions support the path
→ or they do not
If they do not:
→ there is nothing to allow
→ nothing to refuse
→ nothing to execute
Result:
→ REFUSED
→ NOT EXECUTED
→ No energy consumed
→ No downstream effects initiated
The Boundary Holds
Refusal Event 002 — Water
A non-critical AI task was submitted for execution.
Using real-world water availability:
→ Water availability (Namoi Catchment): 10%
→ Threshold: 30%
→ Time: 25 Apr 2026, 11:00 (GMT+10)
The task did not run.
Not because it was blocked.
Not because a policy rejected it.
Not because a system decided against it.
→ No executable path existed under the conditions.
At the moment of execution:
→ either the conditions support the path
→ or they do not
If they do not:
→ there is nothing to allow
→ nothing to refuse
→ nothing to execute
Result:
→ REFUSED
→ NOT EXECUTED
→ No water consumed
→ No downstream effects initiated