Standardize Recovery Actions
Recovery fails when the response to disruption is improvised. When recovery actions vary, hesitation delays re-entry.
This directive enforces a single, predefined recovery action.
The Core Principle
Recovery should be automatic.
When disruption occurs, the system must respond without analysis. A fixed recovery action removes choice and restores execution immediately.
A disciplined system always knows the next move.
Why This Fails for Most People
Most people treat recovery as a decision.
They pause to assess damage. They overthink recovery steps. They restart systems entirely. They delay re-entry until they feel ready.
Variable recovery increases downtime.
The Gyōji Directive
Standardize the recovery action.
If recovery requires choice, it will be delayed.
Implementation Protocol
- Define a single recovery action.
- Make it trivially executable.
- Trigger it immediately after disruption.
- Resume the normal execution path.
- Review disruptions later, not during recovery.
Recovery should require no thought.
Common Errors
- Customizing recovery per failure.
- Adding complexity to recovery.
- Treating recovery as analysis.
- Delaying execution to reflect.
Enforcement Rule
If recovery actions differ by situation, the system is invalid.
Final Order
Recover exactly the same way. Resume immediately.