Directive 60: Identity Is Not an Exception Path

Exception paths erode discipline. When identity is allowed to create special handling—temporary exemptions, alternate rules, or softer enforcement—systems become subjective and inconsistent.

This directive forbids identity-based exception paths.

The Core Principle

Rules apply uniformly.

Execution must not branch on who someone is, who they believe they are, or the role they claim. Identity is descriptive; rules are operative.

A disciplined system has no identity-based forks.

Why This Fails for Most People

Most people introduce exceptions under pressure.

Common failures include:

• Granting role-based exemptions
• Suspending rules for trusted individuals
• Allowing self-concept to soften enforcement
• Creating temporary passes that become permanent

Exceptions multiply silently.

The Gyōji Directive

Eliminate all identity-based exception paths.

If execution branches based on identity, the system is invalid.

Implementation Protocol

1. Enumerate all execution paths.
2. Remove identity checks and role gates.
3. Enforce the same rules for all actors.
4. Log violations without attribution bias.
5. Audit for hidden exceptions.

Uniformity preserves integrity.

Common Errors

• Confusing trust with exemption
• Allowing seniority-based leniency
• Treating exceptions as compassion
• Failing to retire temporary rules

Enforcement Rule

If any identity creates a special case, the system is invalid.

Final Order

Remove exceptions. Enforce uniformly.