The irreducible epistemic atoms underlying the curriculum. 4,828 atoms across 8 types and 2 molecules
Design social accountability around process questions ('Did you write for 30 minutes?') rather than outcome questions ('Did you finish the chapter?') because process accountability triggers action while outcome accountability triggers anxiety.
When a trigger has not fired successfully in one week despite being needed, redesign it immediately by changing at least one of: salience, timing, modality, or context specificity.
Make social accountability reporting require near-zero effort (single emoji, shared spreadsheet checkbox, photo) rather than written explanations, because reporting friction kills trigger reliability.
Set your trigger signal-to-noise ratio threshold at 80% actionability minimum — remove any trigger that produces action fewer than 80% of times it fires.
Conduct monthly trigger audits by evaluating each trigger against four questions: Is it still firing? Do you respond when it fires? Is the behavior still relevant? Is calibration still correct?
Design triggers to work at your minimum cognitive state (tired, distracted, depleted) rather than your maximum state, because triggers must function when you need them most.
Convert vicious cycles into virtuous ones by intervening at a single node to reverse signal direction rather than attempting to dismantle the entire loop structure, because loop topology is often more stable than loop content.
When building any recurring system (workflow, habit, routine), design an explicit degraded-mode version that preserves core function at reduced scope before the system encounters its first disruption.
When an error recurs with the same root cause across multiple independent instances, apply structural fixes (process changes, environmental redesign, automated checks) rather than effort-based resolutions (increased attention, more discipline, trying harder).
Design cognitive agents with non-overlapping scopes by defining exactly which situations, resources, or decisions each agent claims authority over, treating scope collisions as architecture problems requiring boundary redefinition rather than willpower failures.
Verify habit automaticity by checking whether the behavior fires from context cues with minimal conscious effort rather than checking execution frequency, because consistency maintained through willpower is not delegation—true automaticity means the cue triggers the routine without deliberation.
Protect the habit formation transfer period (first 2-4 weeks) with environmental supports that make cues more salient and routines easier to initiate, treating these supports as temporary scaffolding to be removed once the delegation completes rather than permanent infrastructure.
When building behavioral chains through habit stacking, automate each link fully before adding the next link to the chain, because stacking unautomatic behaviors creates a pile of effortful tasks that collapses under executive function depletion rather than a self-sustaining sequence.
When a commitment fails, conduct the diagnostic protocol (identify failure trigger, locate decision point, match structural support to vulnerability type, install before next instance) within 48 hours rather than treating failure as evidence of insufficient willpower.
When forming implementation intentions for novel or complex goals, generate multiple if-then plans covering different potential breakdown contexts rather than relying on a single anticipated trigger, because breakdown patterns in unfamiliar domains cannot be predicted accurately from first principles.