Concepts
The irreducible epistemic atoms underlying the curriculum. 4,828 atoms across 8 types
Every priority system needs an explicit 'not now' tier…
Include an explicit 'not now' or lowest-tier priority type to prevent deferred items from inflating middle categories and to create visible records of deliberate exclusion.
Priority labels without response protocols are decoration…
Attach specific response protocols (timing, resources, escalation) to each priority type rather than treating them as descriptive labels, making priority actionable.
Assign RACI roles explicitly — every task needs exactly…
For each agent-task pair in collaborative work, assign an explicit role type (Responsible, Accountable, Consulted, Informed) and verify that every task has exactly one Accountable party.
Map prerequisite chains backward before learning — ask…
Before attempting to learn a target skill, map its prerequisite chain backward by repeatedly asking 'what must I be able to do first?' until reaching skills you can perform reliably, then start at the lowest-rated prerequisite rather than the target.
State your purpose in one sentence before writing…
Before beginning any communication, writing, or presentation, state in one sentence what you are trying to accomplish, then use that purpose statement to select the appropriate level of abstraction.
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.
Pre-mortem your critical schemas
Run a pre-mortem on each critical schema by specifying what the early warning signs would look like if that model is becoming obsolete, then check whether you have already seen some of those signs.
Map all downstream dependencies before updating a schema…
When updating a schema, map all downstream dependencies (habits, commitments, tools, relationships, routines) before implementation and migrate high-friction dependencies first.
High-dependency schemas need slower revision — each update…
When a schema has many downstream dependencies, apply slower and more deliberate revision cadences than its pace layer alone suggests, because updating foundational schemas requires cascading updates to all dependent schemas.
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.
Schema change scales with group size
Scale your timeline expectations for schema change with group size—weeks for pairs, quarters for 50-person orgs, years for industries—and measure progress in behavioral change rather than stated agreement.
Ask 'how long have similar tasks taken?' not 'how long…
When planning task duration, deliberately switch from inside-view scenario construction to outside-view base-rate consultation by asking 'how long have similar tasks taken?' instead of 'how long will this take?'