Design for Observability
Invisible systems cannot be enforced. If you cannot see execution occurring, you cannot correct drift.
This directive mandates that all systems must broadcast their state clearly and unambiguously.
The Core Principle
Opacity protects malfunction.
When execution is hidden in human memory, ambiguous notes, or private intentions, drift occurs without consequence. Making execution observable forces accountability into the environment.
A disciplined system is entirely visible.
Why This Fails for Most People
Most people hide their execution. They rely on internal tracking because it feels safer. Visible failure is uncomfortable.
They use mental checklists. They track progress vaguely. They hide their metrics from themselves. They avoid logging failures.
Hidden execution is just an intention.
The Gyōji Directive
Design systems so execution state is instantly observable.
If execution cannot be verified externally at a glance, the system is invalid.
Implementation Protocol
- Externalize tracking (dashboards, logs, physical trackers).
- Make the current state binary and obvious.
- Remove all subjective measurements.
- Place the tracker in the path of execution.
- Review the state daily.
Observability removes the option to lie to yourself.
Common Errors
- Relying on memory.
- Using complex, high-friction tracking tools.
- Tracking intention instead of action.
- Hiding the tracker when failing.
Enforcement Rule
If execution is not visible, it did not happen.
Final Order
Expose execution. Make state visible.