Document every pattern with three fields
For each named pattern in your Pattern Dictionary, document three required fields: the pattern name, its observable trigger conditions, and the default behavioral response it produces.
When This Fires
- After naming a new pattern (Name patterns in 2-4 words that compress…) and wanting to make it actionable
- During pattern dictionary creation or maintenance
- When you can recognize a pattern by name but can't articulate its trigger conditions
- Any time you want to move from "I have a pattern" to "I can intervene in this pattern"
Common Failure Mode
Documenting the trigger as an internal state rather than an observable condition. "Trigger: feeling overwhelmed" is too vague for detection — you're always somewhat overwhelmed, so the trigger never stands out. "Trigger: inbox exceeds 50 items + meeting in the next 30 minutes" is observable and specific. The detection reliability of your pattern dictionary depends on trigger specificity.
The Protocol
For each pattern in your dictionary: (1) Name: 2-4 word label (see Name patterns in 2-4 words that compress…). (2) Trigger: describe observable conditions — what would a camera see? What environmental signals are present? What just happened? (3) Default response: what do you automatically do when the trigger fires? Describe the behavior, not the feeling. (4) Store all three in a single, quickly accessible reference. Review monthly to verify triggers are still accurate and add new patterns as they're identified.