Classify routine elements as load-bearing…

When This Fires

• When auditing your routine for resilience before disruption occurs
• When preparing for travel, schedule changes, or periods of reduced capacity
• When When one routine element fails, execute minimum viable… triggers (partial routine failure) and you need to decide what to execute at minimum viable
• When your routine has grown to the point where full execution takes too long

Common Failure Mode

Everything classified as "essential" because it feels important. If every element is load-bearing, you have no flexibility during disruption and When one routine element fails, execute minimum viable… can't function (there's nothing to sacrifice). In practice, most routines have 2-4 genuinely load-bearing elements and 3-6 cosmetic ones. If your audit produces more than 50% load-bearing, you're probably over-classifying.

The Protocol

(1) List every element in your routine. (2) For each element, apply the downstream degradation test: "When I've skipped this in the past, was my day noticeably worse in terms of mood, energy, focus, or output?" (3) If yes → load-bearing. Design a minimum viable version (When one routine element fails, execute minimum viable…) for degraded conditions. (4) If no → cosmetic. It's nice to include, but it can be the first thing sacrificed during disruption. (5) Verify the classification by actually skipping cosmetic elements for a week. If you notice no degradation, the classification is correct. If something you labeled cosmetic turns out to matter, reclassify it as load-bearing. (6) Aim for 30-40% load-bearing, 60-70% cosmetic. This gives you substantial flexibility during disruption while protecting what genuinely matters.