Agent priority orderings must be context-specific — which…
Build priority orderings that are context-specific rather than global, defining which agent takes precedence during specific time blocks, capacity states, or situational contexts rather than attempting universal rankings.
When This Fires
- When designing the priority hierarchy (Resolve inter-agent conflicts with documented priority…) and finding that a single ranking doesn't cover all situations
- When the "right" priority genuinely varies by time of day, energy level, or situation
- When a global priority ranking keeps producing wrong answers in specific contexts
- When building a complete multi-agent coordination architecture
Common Failure Mode
Attempting universal rankings: "My health is my #1 priority." Always? During a job interview? During a once-in-a-career opportunity? During a team emergency? Universal rankings sound principled but produce rigid behavior that's wrong in predictable contexts. Context-specific rankings are more complex to design but produce correct behavior across varied situations.
The Protocol
(1) Identify the contexts in which your agents' priorities genuinely vary. Common context dimensions: time of day, energy/capacity state, social situation, deadline proximity, and life phase. (2) For each context, define the priority ordering: which agent takes precedence? (3) Format as a routing table: "During [context] → [agent] leads, [other agents] are consulted." (4) Define context transition triggers: how do you know which context you're in? Use observable criteria (Apply the camera test to triggers — if a camera can't…), not subjective assessment. "After 12 PM" not "when I feel like taking a break." (5) When agents conflict, consult the routing table: what context am I in right now? The table resolves the conflict without real-time deliberation.