The irreducible epistemic atoms underlying the curriculum. 4,828 atoms across 8 types and 2 molecules
For any system you operate, define four components in writing: (1) ideal behavior, (2) minimum acceptable behavior, (3) numeric deviation threshold, and (4) time window before triggering investigation.
When error budget exhaustion occurs in a tracked system, conduct root cause analysis of the pattern rather than investigating individual deviations, because budget exhaustion signals structural problems while individual errors within budget represent normal variance.
Express error budgets as time-bounded numeric thresholds (e.g., 'two missed sessions per week' or '30 minutes downtime per month') rather than vague intentions, and track consumption against the budget as a first-class metric.
For each active goal, define an explicit error budget specifying how many misses, delays, or quality drops per period are acceptable before triggering system review, converting brittle expectations into resilient ones.
Define error budget thresholds in three tiers—green (within budget, no action), yellow (approaching limits, investigate), red (exceeded, halt and redesign)—with pre-committed responses for each zone.