BACK TO DIRECTIVES
Directive 78

Identity Does Not Authorize Exceptions

Directive 78: Identity Does Not Authorize Exceptions

Exception paths are where discipline breaks. Identity, seniority, or reputation is often used to justify stepping outside defined rules. This creates hidden branches that bypass enforcement and accumulate risk.

This directive prohibits identity-based exceptions entirely.

The Core Principle

Rules are universal.

Exceptions undermine predictability, fairness, and control. Identity cannot justify deviation without invalidating the system.

A disciplined system has no identity-driven escape hatches.

Why This Fails for Most People

Most people grant exceptions to preserve relationships.

Common failures include:

  • Allowing “one-time” favors for trusted actors
  • Creating informal bypasses for senior roles
  • Treating reputation as a warrant
  • Letting confidence override constraints

Temporary exceptions become permanent structure.

The Gyōji Directive

Do not allow identity to create exceptions.

If an exception exists because of who someone is, the system is invalid.

Implementation Protocol

  1. Enumerate allowed exception paths explicitly.
  2. Prohibit ad hoc deviations.
  3. Enforce rules mechanically.
  4. Log attempted exception requests.
  5. Escalate repeated attempts.

Exceptions must be designed, not granted.

Common Errors

  • Framing exceptions as compassion
  • Allowing silent workarounds
  • Avoiding enforcement to keep peace
  • Forgetting to close exception paths

Enforcement Rule

If identity authorizes an exception, enforcement must escalate.

Final Order

Honor the rule. Reject the exception.

Subscribe to the Protocol