Classify every behavior as designed or default — the inability to identify when you chose it IS the diagnosis

Why This Is a Rule

The binary classification — designed vs. default — is deceptively simple but diagnostically powerful. A designed behavior is one where you can point to a specific moment when you decided to adopt it: "I started doing morning pages after reading The Artist's Way in March 2024." A default behavior has no identifiable installation decision: "I've always checked my phone first thing in the morning" or "I don't know when I started procrastinating with email." The absence of a decision point is the diagnosis: the behavior was never consciously chosen. It was absorbed from environment, social modeling, or reinforcement accident.

This matters because default behaviors are unexamined automation. They may be serving you well or poorly, but you've never evaluated them — they just happened. The classification act itself forces evaluation: for every behavior you can't trace to a decision, you've identified a candidate for conscious redesign. Many people discover that 60-80% of their daily behaviors are defaults they never chose.

The classification also reveals a subtler pattern: designed behaviors that have become defaults. You installed a meditation practice two years ago (designed) but can no longer articulate why or whether it's still serving its original purpose (defaultified). These hybrid cases need re-examination too.

When This Fires

• During behavioral audits (Audit agents with hourly momentary sampling, not end-of-day recall — memory overweights successes and hides failures) when cataloging observed behaviors
• When you notice a recurring behavior and wonder "why do I do this?"
• During agent inventory when distinguishing consciously installed behaviors from inherited patterns
• When simplifying your behavioral portfolio — defaults with no clear purpose are prime candidates for removal

Common Failure Mode

Retroactively claiming defaults were designed: "I check email first thing because I decided it's important to stay responsive." Did you actually decide that, or did the behavior start before you had a rationale for it? The rationalization test: if you can't name when you made the decision and what alternatives you considered, the behavior is likely a default wearing a post-hoc justification costume.

The Protocol

(1) During a behavioral audit, for each observed behavior, ask: "Can I identify a specific moment when I decided to adopt this behavior?" (2) If yes → designed. Record when and why you installed it. Check: is the original reason still valid? (3) If no → default. Record it as unexamined automation. Ask: if I were designing my behavior from scratch, would I choose this? (4) For defaults you'd keep → convert them to designed agents by explicitly endorsing them (now they have a decision point). (5) For defaults you wouldn't choose → redesign or remove. These are behaviors running on your resources without your conscious authorization.