Require 3 recent decision examples for each schema — fewer…

In your schema inventory, require behavioral proof by identifying three decisions from the last month that each schema governed—if you cannot find three, reclassify the schema as aspirational rather than operational.

When This Fires

During schema inventory construction (Inventory what you actually do — not what you should…)
When you suspect a gap between stated values and actual behavior
After receiving feedback that contradicts your self-description
During any self-assessment where you want to verify operational vs aspirational schemas

Common Failure Mode

Counting vague "I probably used this" moments as decisions: "I think I considered quality when reviewing that PR." Was quality the deciding factor in the review's outcome, or just a thought you had? Behavioral proof requires the schema to have governed the decision's outcome — not just appeared in the deliberation.

The Protocol

For each schema in your inventory: (1) Try to name three specific decisions from the last month that this schema governed. Not "influenced" or "was relevant to" — governed: the schema was the primary factor in the decision's outcome. (2) If 3+ examples → operational schema. It genuinely guides your behavior. (3) If 0-2 examples → aspirational schema. Reclassify it honestly. It's something you want to operate on, not something you currently do. (4) For aspirational schemas you want to become operational: design the implementation (Attach 'When [situation], I will [action]' to every… implementation intentions, Stack behavior change behavior stacking) that would make them govern actual decisions.