Put schema reviews on your actual calendar — subjective…
Schedule schema reviews on actual calendars at the assigned cadence rather than relying on subjective feelings of uncertainty to prompt reconsideration.
When This Fires
- After determining review cadences for your schemas (Map review frequency to pace layer, High-dependency schemas need slower revision — each update…, In complex or chaotic domains, review schemas more…)
- When schemas are reviewed "whenever I feel uncertain" (subjective trigger)
- When past schema failures could have been caught by regular scheduled review
- During any setup of epistemic maintenance infrastructure
Common Failure Mode
Scheduling the reviews but not protecting the time: "I'll review quarterly, but only if I have time." The review gets pushed by more urgent work — every quarter. Calendar scheduling only works if the time is protected. Treat schema reviews like dental appointments: scheduled, non-negotiable, and if you skip one, the cost compounds.
The Protocol
(1) For each schema review tier (weekly, monthly, quarterly, annual from Map review frequency to pace layer), create a recurring calendar event. (2) During each event: review all schemas assigned to that cadence. Check: does the schema still predict accurately? Have environmental assumptions changed? Have anomalies accumulated? (3) Protect the time. If the review is consistently skipped → the cadence is wrong (too frequent) or the schema portfolio is too large (needs pruning). Either fix the root cause or accept that unreviewed schemas will silently drift.