Directive 22: Define Exit Criteria

Work expands when endings are undefined. Tasks linger, scope creeps, and execution stalls because there is no clear signal to stop. Discipline improves when exit conditions are specified in advance.

This directive enforces explicit completion criteria so work concludes cleanly.

The Core Principle

Endings must be as deliberate as starts.

Without exit criteria, execution has no boundary. Clear endings prevent overwork, protect recovery, and enable reliable scheduling of subsequent actions.

A disciplined system knows when to stop.

Why This Fails for Most People

Most people define what it means to start but not what it means to finish. They rely on feelings of “good enough” or external pressure.

Common failures include:

• Letting tasks run until exhaustion
• Expanding scope mid‑task
• Chasing perfection past utility
• Avoiding completion decisions

Undefined exits turn effort into drag.

The Gyōji Directive

Define exit criteria before execution begins.

If a task cannot end decisively, it will consume excess time.

Implementation Protocol

1. Specify objective completion signals.
2. Limit acceptable outputs.
3. Set maximum time or iterations.
4. Stop immediately when criteria are met.
5. Review only after completion.

Exit criteria should be observable and enforceable.

Common Errors

• Using subjective satisfaction as an endpoint
• Allowing scope to expand during execution
• Ignoring time limits
• Treating stopping as failure

Enforcement Rule

If a task continues without a defined endpoint, the system is invalid.

Final Order

Decide the end in advance. Stop without hesitation.