Concepts
The irreducible epistemic atoms underlying the curriculum. 4,828 atoms across 8 types
Design a degraded-mode version of every recurring system…
When building any recurring system (workflow, habit, routine), design an explicit degraded-mode version that preserves core function at reduced scope before the system encounters its first disruption.
Design three operating modes for every important process
For every important recurring process, design three explicit operating modes—full, reduced, and minimal—where each preserves progressively less fidelity but never loses continuity.
Define triggers for mode transitions in both directions…
Define transition triggers for each operating mode that specify when to shift from full to reduced, reduced to minimal, and—critically—from degraded back to full operation.
Test degraded modes during calm periods — if they don't…
Test degraded operating modes during periods of abundant resources to verify they preserve core function, because modes that fail under calm conditions will certainly fail under stress.
Occasionally run processes in degraded mode…
Practice running processes in degraded mode occasionally even when not required to rehearse partial failure, making the transition familiar rather than frightening when real constraints force it.
Remove agents gradually — reduce frequency before…
When removing an agent, execute graduated shutdown by reducing frequency or scope before full elimination, monitoring for hidden dependencies during the transition period.
When one routine element fails, execute minimum viable…
When a single element of your routine fails, execute the minimum viable versions of remaining load-bearing elements rather than abandoning the entire routine structure.
Limit checklists to 5-9 items targeting frequent +…
Limit output checklists to five-to-nine items targeting errors that are both frequent and consequential, ordering from most catastrophic to least to enable partial execution under time pressure.