Constrain Optional Actions
Optional actions expand indefinitely until they consume all available capacity. When secondary tasks are unconstrained, they compete with primary execution.
This directive places strict limits on optional actions to protect execution.
The Core Principle
Constraint prevents bloat.
Optional tasks feel productive but dilute focus. Without limits, they drain energy needed for mandatory execution. Bounding optional actions ensures core requirements are met first.
A disciplined system forces scarcity on optionality.
Why This Fails for Most People
Most people allow secondary tasks to expand. They confuse busyness with execution.
They prioritize easy optional tasks over hard mandatory ones. They fail to set time limits. They let secondary work disrupt focus blocks.
Unconstrained optionality destroys primary execution.
The Gyōji Directive
Strictly bound all optional actions.
If an optional action can delay a mandatory one, the system is misdesigned.
Implementation Protocol
- Identify optional actions.
- Assign strict time limits to them.
- Execute optional actions only after mandatory ones.
- Stop immediately when the time limit expires.
Optional work must be contained.
Common Errors
- Treating optional tasks as urgent.
- Allowing optional tasks to consume primary blocks.
- Failing to set hard stopping points.
Enforcement Rule
If optional work displaces mandatory work, the boundary has failed.
Final Order
Constrain the optional. Protect the core.