Concepts
The irreducible epistemic atoms underlying the curriculum. 4,828 atoms across 8 types
When reclaiming a non-delegable decision, retain only…
When reclaiming a delegated decision that scored 2+ on the non-delegable filter, restructure by retaining the non-delegable core (judgment, value trade-off, contextual interpretation) while re-delegating execution (research, analysis, implementation) to preserve leverage without losing identity.
The competent stranger test
Test specification completeness by asking whether a competent stranger with relevant skills but zero context could produce an acceptable result from your specification alone—if not, the missing information must be externalized before delegation.
Three verification layers
Design verification as three independent layers—continuous signals (daily metrics), periodic samples (weekly/monthly spot-checks), and infrequent structural audits (quarterly full reviews)—with each layer optimized for different failure detection at different resource costs.
Transparent verification builds trust, hidden monitoring…
Make verification checkpoints transparent to delegates by communicating what you will check, when you will check it, and what standards apply, because hidden monitoring functions as surveillance while transparent verification functions as professional collaboration.
Cascading verification escalation
When a verification signal degrades, escalate to deeper sampling; when sampling reveals a pattern, trigger a structural audit; when an audit reveals a structural problem, modify the delegation itself—this creates a cascading response protocol where each verification layer can activate the next.
Trust is a dynamic variable — extend verification…
Extend verification intervals when a delegate produces consistent quality outputs over time, and tighten intervals when errors surface, treating trust as a dynamic variable calibrated by accumulated evidence rather than a fixed initial condition.
Scale AI output verification to stakes
For high-stakes AI outputs, adopt a three-tier verification intensity: skim for low-stakes brainstorming, spot-check key claims for medium-stakes communications, and verify every substantive claim for high-stakes published or production content.
Classify tool delegations as appropriate, convenient…
Before delegating a cognitive task to a tool, classify whether the delegation is appropriate (tool does it better and verification is easy), convenient (saves time but you could do it), or critical (you cannot perform it without the tool), because critical delegations create capability gaps when tools fail.
Periodically perform critical delegated tasks without…
For critical tool delegations where failure would compromise your effectiveness, maintain periodic unassisted performance of the delegated capability to prevent atrophy of the biological skill, treating the practice as architectural redundancy rather than inefficiency.
Govern your tool use with explicit policies
Design tool-use policies that define which tools you allow for which tasks, under what conditions, and with what fallback behavior when tools fail, treating this as governance of your extended cognitive architecture rather than as tool preferences.
Test habit automaticity by effort level, not frequency…
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.
Add temporary scaffolding during the first 2-4 weeks…
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.
Automate each habit link before adding the next — stacking…
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.
Separate reasoning from credentials
When someone shares expertise or makes a recommendation, separate your evaluation of their reasoning from your evaluation of their credentials by asking 'Would I find this compelling if it came from a low-status source?'
Apply the defense test to AI conclusions
Before acting on AI-generated conclusions, apply the defense test: 'Could I defend this conclusion without the AI's output? Do I understand the reasoning well enough to identify where it might be wrong?'—if not, do the cognitive work before proceeding.
The accountability check
Before adopting anyone else's recommendation, apply the accountability check: 'Am I willing to own this decision as though it were entirely my own?'—if you would deflect blame to the source upon failure, you have not processed the input as influence.
When an objection dissolves from social pressure…
When you notice an objection dissolving before you voice it—not because someone addressed it, but because the social cost seems too high—recognize this as the compliance instinct activating and deliberately externalize the concern in writing before deciding whether to voice it.
Write your position before emotionally charged…
During emotionally charged disagreements in close relationships, write down your actual position before the conversation and return to it afterward to check whether changes were driven by persuasion or anxiety relief.
As the sole dissenter, state your position AND one…
During dissent in group settings, when you are the sole opposing voice, explicitly state both your position and one condition under which you would change your mind to signal intellectual humility alongside independence.
Use 'I think/want/believe' in relationship disagreements…
In close relationships, frame disagreements using 'I think/want/believe' language rather than 'don't you think' or 'most people' formulations to take explicit ownership of your position.
Before difficult relationship conversations, write three…
Before a difficult conversation in a close relationship, externalize your position in writing with three components: what you think, what you're willing to change, and what you're not willing to change.
Voice domain expertise that contradicts authority…
When you possess domain-specific expertise relevant to a decision, voice your dissenting assessment even when it conflicts with hierarchical authority, because withholding situated knowledge creates epistemic fragility and constitutes professional negligence.
Frame professional dissent as questions — questions…
Frame professional dissent as questions rather than assertions when building credibility, because questions activate information-sharing while reducing social cost and allowing decision-makers to reach conclusions themselves.
Build dissent authority through demonstrated competence…
Build authority to dissent through demonstrated competence and calibrated prediction tracking, because self-authority without proven expertise is indistinguishable from arrogance and carries no credible weight.