Pre-define allocation rules for contested time blocks…
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.
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… (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…) 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?