Directive 11: Define Failure Conditions

Discipline fails quietly when failure is undefined. Without explicit failure conditions, drift is reinterpreted as flexibility, and correction is delayed.

This directive forces failure to be named in advance so it can be acted on immediately.

The Core Principle

Unclear failure enables rationalization.

When a system does not define what failure looks like, the brain fills the gap with excuses. Clear failure conditions remove ambiguity and force corrective action.

A disciplined system knows exactly when it has failed.

Why This Fails for Most People

Most people define success vaguely and avoid defining failure at all. They rely on feelings or trends instead of explicit criteria.

Common failures include:

• “I mostly followed it”
• “I slipped a little”
• “I can compensate tomorrow”

These phrases soften failure and delay correction.

The Gyōji Directive

Define failure conditions before execution begins.

If failure is only recognized in hindsight, the system is defective.

Implementation Protocol

1. Define success criteria.
2. Define failure criteria.
3. Specify the immediate corrective action.
4. Record failures as binary events.
5. Apply correction without interpretation.

Failure definitions must be objective and observable.

Common Errors

• Allowing gray areas
• Redefining failure after the fact
• Delaying response to failure
• Treating failure as information only

Enforcement Rule

If failure cannot be identified immediately, the rule is invalid.

Final Order

Name failure early. Correct without delay.