Identity Does Not Determine Priority
Directive 77: Identity Does Not Determine Priority
Priority collapses when identity is allowed to reorder work. Seniority, reputation, urgency claims, or personal confidence often distort queues and starve critical tasks.
This directive requires priority to be system‑defined and identity‑blind.
The Core Principle
Priority follows impact, not person.
Work must be ordered by risk, dependency, and system value. Identity introduces bias and noise into sequencing.
A disciplined system prioritizes mechanically.
Why This Fails for Most People
Most people reprioritize under social pressure.
Common failures include:
- Jumping the queue for senior voices
- Treating loud urgency as importance
- Reordering work to satisfy reputation
- Letting confidence distort sequencing
Distorted priority amplifies failure.
The Gyōji Directive
Never allow identity to reorder priority.
If work is reprioritized because of who asked, the system is invalid.
Implementation Protocol
- Define priority rules explicitly.
- Order work by impact and dependency.
- Lock queues during execution.
- Log and review priority changes.
- Escalate repeated priority violations.
Priority must be deterministic.
Common Errors
- Confusing urgency with importance
- Allowing exceptions to feel responsive
- Reordering silently
- Avoiding pushback against influence
Enforcement Rule
If identity determines priority, enforcement must escalate.
Final Order
Respect the queue. Ignore reputation.