Concepts
The irreducible epistemic atoms underlying the curriculum. 4,828 atoms across 8 types
Ask four diagnostic questions during weekly review…
During weekly reviews, ask four metacognitive questions—what did I capture well, what did I almost lose, where did I over-capture noise, and what am I avoiding—to monitor system health rather than just processing lists.
Weekly
Add a single recurring check at the end of each weekly review that compares your operational handbook to your actual operations and updates discrepancies immediately.
Read all notes without editing first, then extract themes…
When reviewing notes for patterns, read through all entries without editing or organizing first, then extract recurring themes on a separate page, to prevent premature categorization from filtering out emergent structures.
Quarterly
Schedule quarterly depreciation reviews where you scan captured notes and bookmarks for information that has exceeded its useful life, then either update with current data, archive with context, or delete entirely to prevent outdated information from corrupting current decisions.
Read the original decision context before evaluating…
When reviewing a past decision, read the original context record before evaluating the outcome, because evaluating outcome first allows hindsight bias to contaminate your assessment of whether the reasoning was sound.
Weekly
Audit thinking environments weekly by comparing actual conditions against documented specifications to detect entropy, because environmental decay through accumulated objects, browser tabs, and permission drift is constant and unnoticed without structured review.
Cross-reference domains in weekly review
During weekly reviews, cross-reference externalized domains to detect contradictions—compare stated priorities against time allocation, goals against commitments, assumptions against failure analyses—because isolated review of each domain misses the conflicts that degrade decision quality.
Match review frequency to volatility
Schedule schema reviews at cadences matched to environmental volatility: weekly/biweekly for high-change contexts, monthly/quarterly for stable contexts, plus triggered reviews when surprises occur.
Map review frequency to pace layer
Assign review cadences to schemas based on their pace layer—weekly to monthly for fashion/commerce layers in complex domains, quarterly for infrastructure layer, annually for governance layer, and only on anomaly for culture/nature layers with high dependency depth.
In complex or chaotic domains, review schemas more…
In complex or chaotic Cynefin domains, increase schema review frequency beyond what the pace layer suggests because unpredictability generates more frequent anomalies requiring evaluation.
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.
Keep schema evolution logs minimal (4 fields) and review…
Maintain schema evolution logs with minimum viable entries of four fields - date, schema affected, what changed, and what prompted the change - reviewed weekly, to generate a dataset about cognitive patterns that introspection alone cannot produce.
A schema unreviewed for 6 months is like an unupdated…
Treat any schema that has gone six months without deliberate review the same as a software dependency unupdated for six months - not necessarily broken but requiring verification before continued reliance.
Invest quarterly maintenance in your top 5% most-connected…
Identify your top 5% of notes by connection count and schedule quarterly reviews where you verify each hub note is current, accurate, and well-linked, investing maintenance effort proportional to structural importance.
Add 'Did I use the right framework?' to every decision…
In post-decision review, explicitly add the meta-question 'Did I use the right framework for this decision?' and note framework-decision mismatches (comprehensive analysis on trivial reversible choices, satisficing on irreversible high-stakes decisions) to build your personal routing table.