Resolve inter-agent conflicts with documented priority hierarchies — case-by-case deliberation defeats the purpose of automation

Why This Is a Rule

As your behavioral agent portfolio grows, agents inevitably conflict. Your "deep work from 9-11 AM" agent conflicts with your "respond to messages within 2 hours" agent when a message arrives at 9:30. Your "exercise every morning" agent conflicts with your "journal before work" agent when morning time is tight. Without a priority hierarchy, each conflict forces ad-hoc deliberation — exactly the cognitive cost that agents were designed to eliminate.

This is Resolve contradictions at the principle level once — re-adjudicating at each tactical decision multiplies decision cost (resolve contradictions at the principle level) applied to your behavioral system. Each conflict resolved ad-hoc multiplies decision cost linearly: 5 conflicts per week × 52 weeks = 260 unnecessary decisions per year. A priority hierarchy resolves the class of conflicts once: "Health agents override productivity agents. Deep work overrides communication." Now the 9:30 message conflict is pre-resolved.

The meta-rule — the priority hierarchy itself — becomes part of the agent system. It's not a guideline; it's a documented resolution mechanism that fires automatically when agents conflict, just like the agents themselves fire automatically when triggers occur.

When This Fires

• When two agents prescribe contradictory actions for the same moment
• When adding a new agent to a system where time or resources are already allocated
• During agent portfolio reviews when mapping potential conflicts
• When you notice recurring deliberation about which commitment to honor

Common Failure Mode

Resolving each conflict in the moment based on how you feel: "Today I'll skip exercise for the meeting." Without a priority hierarchy, the louder, more urgent, or more socially visible agent always wins — regardless of whether it's actually more important. Urgency dominates importance by default. The hierarchy explicitly encodes importance so that it can override urgency when appropriate.

The Protocol

(1) List all active agents. (2) Group by domain: health, productivity, social, learning, etc. (3) Establish inter-domain priority: which domain wins when two domains conflict? Document this explicitly. (4) Within each domain, establish agent priority: which specific agents take precedence? (5) When a conflict occurs, consult the hierarchy: the higher-priority agent wins. No deliberation needed. (6) Review the hierarchy quarterly — priorities shift as life circumstances change. (7) Exception rule: define the conditions (if any) under which the hierarchy can be overridden. This should be rare and specific, not "whenever it feels important."