Pre-define allocation rules for contested time blocks — negotiating access in the moment is too late and too costly
Before any contested time block arrives, define the allocation rule (priority ordering, rotation schedule, or time-slice) that resolves contention in advance rather than negotiating access when the block arrives.
Why This Is a Rule
When a time block arrives and multiple agents claim it — deep work wants it, email processing wants it, exercise wants it — the ensuing deliberation consumes the very resource being contested. You spend 20 minutes of a 60-minute block deciding what to do with it, then have 40 minutes of half-committed execution. The deliberation itself is the worst outcome because it wastes the contested resource while producing no productive output.
Pre-defined allocation rules eliminate the deliberation entirely. "Monday 9-11 AM belongs to deep work. Period." When 9 AM Monday arrives, there's no negotiation — the allocation was decided during calm planning time (Design pre-commitments when calm to constrain behavior when stressed — never make rules in hot states), and the contested block has a pre-assigned owner. Email and exercise don't get to contest it because the allocation rule resolved the contention in advance.
Three allocation mechanisms match different contention structures: Priority ordering (Agent priority orderings must be context-specific — which agent wins depends on the time, capacity state, and situation) when agents have genuinely different importance levels. Rotation when agents are equally important and each needs periodic access. Time-slicing when multiple agents need access within the same period (first 30 minutes for X, next 30 for Y).
When This Fires
- When the same time blocks regularly produce "what should I do?" deliberation
- When designing weekly schedules and anticipating where agents will compete for time
- When time block switching happens reactively based on whichever demand feels most urgent
- Complements Agent priority orderings must be context-specific — which agent wins depends on the time, capacity state, and situation (context-specific priorities) with the specific allocation mechanisms
Common Failure Mode
Real-time negotiation: "It's 9 AM, should I do deep work or handle those urgent emails?" This deliberation happens in the contested block, consuming the resource. By the time you decide (deep work wins), the block has lost 15 minutes to deliberation, and the emails are creating background anxiety that undermines focus. Pre-allocation eliminates both the time loss and the psychological cost.
The Protocol
(1) Identify contested time blocks: which blocks regularly produce deliberation about what to do? (2) For each, choose the allocation mechanism: Priority: the highest-priority agent (per context-specific ordering — Agent priority orderings must be context-specific — which agent wins depends on the time, capacity state, and situation) always gets this block. Other agents find different blocks. Rotation: Agent A gets this block on Mon/Wed, Agent B on Tue/Thu, alternating on Fri. Time-slice: first half for Agent A, second half for Agent B. (3) Document the allocation. Write it in your schedule, not just in your head. (4) When the block arrives, execute the allocation without re-deliberating. The decision was made during planning. Trust it. (5) Review allocation effectiveness monthly: is the mechanism producing the right balance?