Directive 79: Identity Does Not Define Scope

Scope creep accelerates when identity is allowed to expand what someone may do. Confidence, seniority, or reputation often substitute for explicit boundaries, leading to unauthorized action and uncontrolled growth.

This directive requires scope to be explicit and identity‑blind.

The Core Principle

Scope is bounded by mandate.

What may be done, changed, or decided must be defined by rules and roles. 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.

Common failures include:

• Letting trusted actors “handle more” without mandate
• Allowing confidence to widen responsibility
• Treating experience as permission
• Ignoring boundary drift

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

1. Define scope explicitly for each role.
2. Enforce boundaries mechanically.
3. Reject actions outside scope.
4. Log and review boundary violations.
5. Escalate repeated scope overreach.

Scope must remain fixed.

Common Errors

• Confusing capability with permission
• Allowing gradual boundary creep
• Avoiding enforcement to preserve trust
• Treating exceptions as growth

Enforcement Rule

If identity defines scope, enforcement must escalate.

Final Order

Enforce the boundary. Ignore reputation.