The irreducible epistemic atoms underlying the curriculum. 4,828 atoms across 8 types and 2 molecules
When you experience confusion, friction, or judgment in a cross-cultural interaction, document three elements before reacting: (1) what you expected, (2) what actually happened, (3) what cultural assumption might explain the gap—treating the collision as diagnostic data about invisible defaults.
For each high-stakes word in decisions or commitments (quality, ownership, alignment, done, strategy), require independent operational definitions from each stakeholder before proceeding, then compare and reconcile the definitions explicitly.
Before sending any consequential text-based message, reread it as a stranger with zero shared context would—no tone, no history, no knowledge of intent—and revise any content that could be misinterpreted in that cold reading.
When emotional content must be conveyed via text, state the emotion explicitly ("I'm frustrated about X") rather than relying on word choice or punctuation to convey tone, because textual cues for emotion fail approximately 45% of the time.
Before sending any important communication, apply the SCQA test—verify the message includes Situation (what reader knows), Complication (what changed), Question (what this raises), and Answer (your point)—adding any missing layer before transmission.
When a commitment cannot be met, communicate the fact proactively before the deadline and renegotiate terms explicitly, as silent dropping versus explicit renegotiation distinguishes reliable commitment systems from internal intention failures.
Before assuming organizational hierarchy makes strategic priorities transitive, verify alignment at each reporting level independently, as 'reports to' relationships do not make 'shares priorities with' transitive.
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.
Before assuming you understand someone's reasoning, externalize your reading of their underlying schema and verify it directly rather than debating conclusions that may stem from invisible schema divergence.
When documenting information longer than one page, structure it in three disclosure layers: single-sentence summary (Layer 1), paragraph-per-section abstracts (Layer 2), and full detail (Layer 3), with each layer independently meaningful.
Position your system prompt's most important instructions in the first 20% of tokens, because transformer attention mechanisms allocate disproportionate processing to early sequence positions through positional encoding and causal masking.
Before explaining your schema to another person, frame your request as 'tell me where this breaks' rather than 'do you agree' to shift the conversation from validation theater to genuine testing.
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.
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.
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.
State boundaries with three explicit components—the specific limit, the consequence of crossing it, and clear communication to the other person—rather than expressing vague preferences.
Frame relational boundaries using the three-part structure: acknowledge the request, state your boundary with the value it protects, and offer an alternative, rather than leading with rejection.
Frame professional boundaries as commitments to work quality rather than confessions of personal weakness ('To protect the architecture review, I'm limiting meetings to 15 hours per week' vs 'I have too many meetings'), because quality-based framing generates respect while capacity-based framing generates sympathy.
When receiving requests that don't map to your top three priorities, use the forced-choice formula 'I can do X or Y this week—which matters more to you?' to surface tradeoffs rather than silently absorbing both demands.
Communicate boundaries using three-component structure: (1) non-judgmental description of situation, (2) impact on you using 'I' language, (3) specific behavioral request the other person can act on—rather than character judgments or vague wishes.
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.
When declining requests, state three components explicitly: what you're declining, why (the priority being protected), and an alternative when appropriate—never just 'I'm busy.'
When priority conflicts arise with stakeholders, present the tradeoff as a forced binary choice with visible costs for each option rather than silently absorbing both demands or refusing without explanation.
When someone makes a request that would conflict with your top priority, name that priority explicitly and ask whether the request can wait or go to someone else with available bandwidth.