The irreducible epistemic atoms underlying the curriculum. 4,828 atoms across 8 types and 2 molecules
When a boundary you've stated clearly is being tested through persistent requests, use the broken record technique: calmly repeat your boundary statement in identical words without adding new arguments, justifications, or escalation—the repetition itself removes footholds for continued negotiation.
When setting a new boundary, predict and document 3-5 specific ways people will test it (who will test, what form tests will take) and pre-write your planned responses before tests arrive, because anticipating tests converts surprise into expected system behavior you've already decided how to handle.
During the first 3-5 days after setting a boundary, maintain absolute consistency without exceptions regardless of pressure, because this initial period is when extinction burst testing is most intense and any capitulation during this window trains others that sufficient escalation will produce the old response.
After each boundary test, log what happened (who tested, how, what you did, how it felt) in an external system to build a dataset revealing patterns invisible from inside—which relationships produce most testing, which test types are hardest for you to withstand, whether your consistency is actually consistent.
When adjusting a boundary for legitimate contextual reasons (genuine emergency, changed circumstances), explicitly state both the adjustment and the return timeline: 'I'll help with this through Friday, and then the original boundary resumes'—to prevent temporary exceptions from becoming permanent erosion.
Structure commitments at enforcement Level 3 or higher (environmental modification, social contract, or structural impossibility) rather than Level 1-2 (intention or implementation intention alone) when the commitment is irreversible, high-stakes, or has failed three or more times on willpower.
When a boundary violation occurs with another person, initiate repair within 24 hours using the three-step sequence: acknowledge the violation explicitly, reassert the boundary without softening, and address the practical or emotional cost the violation created.
After the first boundary violation by the same person, conduct repair with clearly stated consequences; after the second violation, enact the stated consequences rather than issuing new warnings, to distinguish boundary flexibility from boundary erosion.
When you hold positional authority or high status within a group, prioritize modeling boundaries over communicating boundary policies, because your visible behavior establishes the actual permission structure more powerfully than stated rules.
When you notice yourself censoring thoughts or managing another person's emotions during conversations, use that observation as a diagnostic signal that the relationship lacks sufficient boundaries to support honest exchange, then design one boundary that would enable you to speak more freely.
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.
Match the binding strength of commitment devices to the documented severity and frequency of past failures in that domain, using hard pre-commitments (physical impossibility or high cost) only for behaviors with long track records of in-the-moment failure.
Structure public commitments as behavioral specifications with verification mechanisms rather than identity declarations, because identity-based announcements produce premature satisfaction that reduces subsequent effort while behavioral commitments create accountability pressure.
Place written commitments in the physical or digital location where the breakdown typically occurs rather than in convenient filing locations, because visibility at the decision point creates structural friction that memory-based retrieval cannot provide.
For recurring commitments with documented histories of failure, install multiple reinforcing commitment layers (pre-commitment + device + public accountability + implementation intention) rather than relying on any single mechanism, because commitment failures typically result from alignment of multiple weaknesses not single-point vulnerabilities.
Select accountability partners based on their demonstrated willingness to enforce rather than their social proximity, because enforcement capacity (asking hard questions, refusing rationalizations) determines accountability effectiveness while social closeness often reduces willingness to challenge.
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.
Format public commitment check-ins as evidence-based reports ('I did/didn't do X on these specific days') rather than narrative explanations ('I tried hard but...'), because evidence-based formats prevent rationalization at the reporting layer while narrative formats invite it.
Write commitment contracts with all five structural elements (behavior, schedule, completion criteria, duration, signature) and treat any commitment missing one or more elements as a preference rather than a binding commitment.
Limit active implementation intentions to 1-3 simultaneously for novel behaviors, adding additional if-then plans only after existing ones have compiled into automatic execution, because cue-accessibility mechanisms have finite attentional capacity.
When an anchor behavior's context changes (time, location, or sequence), immediately redesign dependent stacked commitments rather than expecting them to survive the anchor disruption.
Stack only one new commitment per month onto existing anchors to prevent chain overload that converts working infrastructure into brittle sequences.
Specify commitment thresholds as clear boundaries that separate 'done' from 'not done' without requiring interpretation, eliminating the space for rationalized partial compliance.
Track both time cost (hours per week) and cognitive cost (mental bandwidth on 1-5 scale) for each active commitment when budgeting capacity.