Weekly cross-check: every stack item has a budget entry, every budgeted commitment has stack representation — no orphans in either system

Why This Is a Rule

Two critical systems — your priority stack (what you're working on) and your commitment budget (what you've committed resources to) — can drift apart silently. The stack might contain items with no corresponding budget allocation (priorities you've identified but haven't actually committed time to). The budget might contain commitments with no stack representation (things consuming your time that aren't in your priority system). Both types of orphans represent system failures.

Stack orphans (priorities without budget) are aspirational — they sit on the stack without receiving actual resources. These create the illusion of progress without the reality. Budget orphans (commitments without stack representation) are invisible resource drains — they consume time and energy but aren't tracked in your priority system, making them impossible to manage consciously.

The weekly cross-reference catches both: every stack item should map to a budgeted commitment (it's actually getting resources) and every budgeted commitment should appear in the stack (it's being managed as a priority). Mismatches reveal system gaps before they compound.

When This Fires

• During weekly planning when aligning execution systems
• When priorities aren't advancing despite feeling busy — budget orphans may be consuming resources
• When commitments feel unmanaged — they may not be represented in the priority stack
• Complements Budget commitments on two dimensions: time cost (hours/week) AND cognitive cost (bandwidth 1-5) — time alone misses the real load (dual-dimension budgeting) with the stack-budget integration check

Common Failure Mode

Separate, unlinked systems: priority stack says "write book, launch product, hire team." Commitment budget shows "weekly team meetings (8 hrs), client calls (6 hrs), admin (4 hrs)." The stack and budget describe different realities. The stack says what's important; the budget shows what's actually consuming resources. Without cross-reference, the gap is invisible.

The Protocol

(1) Each week, list your priority stack items. List your budgeted commitments. (2) For each stack item: does it have a corresponding budget entry with actual hours/energy allocated? If no → it's aspirational, not operational. Either budget time for it or remove it from the stack. (3) For each budget entry: does it appear in or serve an item on the priority stack? If no → it's consuming resources outside your priority system. Either add it to the stack (if it's genuinely important) or eliminate/delegate it (if it isn't). (4) After cross-reference: both systems should describe the same reality — what you're working on and what's consuming your resources should match.