Directive 33: Standardize Recovery Actions

Recovery fails when the response to disruption is improvised. When recovery actions vary, hesitation and overcorrection delay re‑entry. Discipline resumes fastest when recovery is standardized.

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, consider alternatives, or wait to feel ready.

Common failures include:

• Overthinking recovery steps
• Restarting systems entirely
• Delaying re‑entry
• Escalating recovery effort

Variable recovery increases downtime.

The Gyōji Directive

Standardize the recovery action.

If recovery requires choice, it will be delayed.

Implementation Protocol

1. Define a single recovery action.
2. Make it trivially executable.
3. Trigger it immediately after disruption.
4. Resume the normal execution path.
5. 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 the same way every time. Resume immediately.