The irreducible epistemic atoms underlying the curriculum. 4,828 atoms across 8 types and 2 molecules
Treat any deviation from established standards as a potential normalization-of-deviance signal requiring documented evaluation rather than silent acceptance, because repeated deviations without consequence train the system to accept the deviation as normal.
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.
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.
Set Recovery Time Objectives (RTO) that define maximum acceptable downtime and Recovery Point Objectives (RPO) that define maximum acceptable data loss before a failure occurs, not during crisis.