Concepts
The irreducible epistemic atoms underlying the curriculum. 4,828 atoms across 8 types
Expect a second wave of discomfort after initial schema…
Expect a second wave of discomfort after initial schema update when you realize the full implications for past decisions—this delayed recognition is where most people abandon updates and revert to old schemas.
Define observable trigger conditions for schema review…
Define observable trigger conditions for schema review before anomalies accumulate rather than waiting for subjective feelings of uncertainty to prompt reconsideration.
Track prediction accuracy against pre-defined thresholds…
Track prediction accuracy against pre-defined thresholds rather than relying on intuitive assessment of model quality, because humans systematically underweight evidence that contradicts their existing beliefs.
Set calendar-based schema review schedules independent…
Set calendar-based schema review schedules independent of observed performance, because temporal drift occurs whether or not conscious errors are detected.
Accumulate and threshold anomalies rather than evaluate each
Accumulate and threshold anomalies rather than evaluate each contradiction individually, because isolated anomalies can be dismissed while clusters reveal systematic model failure.
Create anomaly logs separate from regular notes, because…
Create anomaly logs separate from regular notes, because anomalies require dedicated collection systems to prevent dismissal through rationalization or burial in routine information.
Assign faster review cadences to schemas in complex…
Assign faster review cadences to schemas in complex or chaotic domains than their pace-layer position alone suggests, because unpredictability generates more frequent invalidating evidence.
Review high-dependency schemas more slowly and deliberately…
Review high-dependency schemas more slowly and deliberately than peripheral schemas, because revising foundational schemas requires updating all dependent schemas in a cascading revision process.
Change shared schemas through shared experiences rather…
Change shared schemas through shared experiences rather than shared information presentations, because behavioral coordination requires updated local models built from practice, not stated agreement.
Create boundary objects that embody new schemas in visible…
Create boundary objects that embody new schemas in visible artifacts, because people adopt schemas they can see and use rather than schemas they were told about.
Map what a shared schema currently supports before proposing
Map what a shared schema currently supports before proposing changes, because schemas embedded in coordination patterns create dependencies that must be managed during transitions.
Distinguish between increasing complexity that improves…
Distinguish between increasing complexity that improves explanatory power and complexity that merely preserves a failing model, because the latter signals the need for architectural replacement rather than parameter tuning.
Replace schemas when the framework cannot formulate…
Replace schemas when the framework cannot formulate questions that reality demands, because inability to express necessary questions reveals incommensurability between model and domain.
Generate multiple alternative frameworks rather than jumping
Generate multiple alternative frameworks rather than jumping to a single replacement, because competitive testing between candidate models produces better selection than loyalty contests.
Write forward-looking predictions from each candidate schema
Write forward-looking predictions from each candidate schema to create testable competition, because prospective prediction testing reveals model quality better than retrospective fit evaluation.
Delayed schema updates impose compounding costs because…
Delayed schema updates impose compounding costs because the gap between your model and a changing reality widens incrementally over time, making each decision progressively less optimal.
When expertise becomes locked into a familiar schema…
When expertise becomes locked into a familiar schema, attentional resources get captured by schema-consistent features, making genuinely better alternatives perceptually invisible even when they are objectively present.
Apply the zero-base test to detect schema rigidity
if you would not adopt the same belief as a newcomer encountering the situation fresh today, the schema persists through inertia rather than current validity.
Use pre-mortem analysis on schemas by imagining…
Use pre-mortem analysis on schemas by imagining they have already failed and working backward to identify plausible failure paths, which increases ability to detect weaknesses by approximately 30%.
Red-team your own schemas by building the strongest possible
Red-team your own schemas by building the strongest possible evidence-based case against them, which either confirms their resilience or reveals upgrade paths before reality forces the update.
Monitor leading indicators of schema drift rather…
Monitor leading indicators of schema drift rather than waiting for catastrophic prediction failures, using statistical shifts in your input environment and changes in decision confidence patterns.
Subject-object shifts—where what was previously invisible…
Subject-object shifts—where what was previously invisible and controlling becomes something you can observe and manage—constitute the mechanism of developmental stage transitions.
Measure the quality of any personal development practice…
Measure the quality of any personal development practice by whether it changed a schema structure or merely added information to an existing one, as only structural change constitutes genuine growth.
Record the source provenance of each schema during inventory
Record the source provenance of each schema during inventory to identify unexamined inherited schemas, as schemas with no traceable origin are most likely outdated.