Budget 30 min to 2 hours weekly for system maintenance — reject additions that exceed it
Calculate maintenance budget for entire operational system (30 minutes to 2 hours weekly) as binding constraint; reject additional components when aggregate maintenance would exceed sustainable capacity.
Why This Is a Rule
Every component in your operational system has a maintenance cost: automations need verification, documents need updating, habits need reinforcement, tools need configuration. These costs are individually small but aggregate into a significant weekly burden. Without a budget, maintenance grows unbounded — each new tool, automation, or practice adds its maintenance cost to the pile, and the pile eventually exceeds available capacity, causing the entire system to collapse.
The maintenance budget (30 minutes to 2 hours weekly, depending on system complexity) creates a binding constraint: the total maintenance cost of all system components must fit within this budget. When a proposed addition would push aggregate maintenance past the budget, you must either reject the addition or remove an existing component to make room.
This is capacity planning applied to personal infrastructure. Just as a server has finite RAM, your operational system has finite maintenance capacity. You can't run unlimited services on finite hardware, and you can't maintain unlimited tools on finite weekly hours.
When This Fires
- Adding a new tool, automation, habit, or tracking system to your operations
- When existing maintenance feels like it's consuming too much time
- During quarterly reviews of your operational system's complexity
- After a system collapse caused by unmaintained components
Common Failure Mode
Adding components without accounting for maintenance: "This new tool will save me 20 minutes a day!" But it requires 15 minutes of weekly maintenance (data cleanup, sync verification, configuration updates). If your maintenance budget is already at capacity, the tool creates a net deficit — maintenance grows while the budget doesn't.
The Protocol
(1) List every component of your operational system (tools, automations, recurring practices, documentation). (2) Estimate weekly maintenance time for each (most are 2-10 minutes). (3) Sum to get aggregate weekly maintenance. (4) Set budget: 30 min (minimal system) to 2 hours (complex system). (5) If aggregate exceeds budget → simplify: remove components until maintenance fits. (6) For every proposed addition: does adding its maintenance keep the total within budget? If no → reject or trade (remove something to make room).