Identity Does Not Define Scope
Scope creep accelerates when identity expands what an operator may do. Confidence or reputation often substitute for explicit boundaries, leading to unauthorized action.
This directive requires scope to be explicit and identity-blind.
The Core Principle
Scope is bounded by mandate.
What may be done must be defined by rules. Identity may influence perception, but it does not widen scope.
A disciplined system enforces scope mechanically.
Why This Fails for Most People
Most people allow scope expansion informally.
They let trusted actors “handle more” without a mandate. They allow confidence to widen responsibility. They treat experience as permission.
Unbounded scope invites failure.
The Gyōji Directive
Do not allow identity to define or expand scope.
If scope changes because of who someone is, the system is invalid.
Implementation Protocol
- Define scope explicitly for each role.
- Enforce boundaries mechanically.
- Reject actions outside scope.
- Log and review boundary violations.
Scope must remain fixed.
Common Errors
- Confusing capability with permission.
- Allowing gradual boundary creep.
- Treating exceptions as growth.
Enforcement Rule
If identity defines scope, enforcement must escalate.
Final Order
Enforce the boundary. Ignore reputation.