Concepts
The irreducible epistemic atoms underlying the curriculum. 4,828 atoms across 8 types
Daily activities need weekly feedback; strategic…
For daily activities, if feedback latency exceeds one week, or for strategic activities if latency exceeds one month, design a leading indicator or checkpoint that shortens the delay before drift compounds.
Instrument before executing — drift detection requires…
Design measurement infrastructure before executing strategies rather than after problems become visible, because drift detection requires baseline instrumentation that must exist before deviation occurs.
Review commitments quarterly (monthly for high-stakes)…
Schedule commitment renewal reviews at fixed intervals (quarterly for most commitments, monthly for high-stakes or rapidly evolving ones) rather than waiting for subjective dissatisfaction, because perceptual thresholds prevent detection of gradual drift.
Write this week's priorities on a blank page without last…
At the start of each week, write your top priorities on a blank page without consulting last week's list, then compare only after fresh selection is complete to detect drift.
Periodically perform automated steps manually — maintain…
Periodically perform automated steps manually as calibration exercises to maintain intervention skill and detect when automation has drifted or is producing incorrect outputs.
Three review altitudes
Review workflows weekly for execution status, monthly for portfolio health, and quarterly for strategic alignment—each altitude catches different kinds of drift.