After commitment failure, diagnose within 48 hours: identify trigger, locate decision point, match structural support — not more willpower
When a commitment fails, conduct the diagnostic protocol (identify failure trigger, locate decision point, match structural support to vulnerability type, install before next instance) within 48 hours rather than treating failure as evidence of insufficient willpower.
Why This Is a Rule
Commitment failure treated as a willpower problem produces: "I'll try harder next time." Commitment failure treated as a structural problem produces: "What specific structural support was missing at the moment of failure?" The second approach is more effective because it addresses the actual vulnerability rather than amplifying a resource (willpower) that already proved insufficient.
The 48-hour diagnostic window parallels Within 24 hours of an error, write one mechanistic sentence + the incorrect assumption it revealed — before memory reconstructs (24-hour error capture): close enough to the failure that the specifics are fresh, far enough to avoid emotional flooding. The protocol has four steps, each building on the previous: Identify the failure trigger — what specific event or condition activated the competing behavior? (Tiredness? Social pressure? Environment cue?) Locate the decision point — where exactly did the commitment path diverge from the competing path? (When I opened the fridge? When the notification appeared? When they asked for help?) Match structural support to vulnerability type — what support would have maintained the commitment at that decision point? (Upgrade commitment enforcement to Level 3+ (environment, social contract, structural impossibility) when willpower has failed 3 times's enforcement hierarchy: environmental modification, social contract, or structural impossibility) Install before next instance — the structural support must be in place before the trigger recurs, not "sometime soon."
When This Fires
- Within 48 hours of any commitment failure
- When the same commitment keeps failing despite repeated "trying harder"
- When the instinct is self-blame rather than system diagnosis
- Complements Diagnose before redesigning — identify whether trigger, condition, or action broke before changing anything (agent component diagnosis) and Recurring errors with the same root cause need structural fixes, not more effort — process changes beat discipline every time (structural fixes) for commitment contexts
Common Failure Mode
The willpower recommitment: "I broke my diet. I need to be stronger. I will not eat sugar starting tomorrow." This addresses zero structural vulnerabilities while re-applying the same insufficient resource (willpower). The diagnostic approach: "I ate sugar at 3 PM (trigger: afternoon energy crash). The decision point was opening the break room door (where candy is visible). Structural support needed: snack alternatives pre-positioned at my desk (Subtract unwanted affordances before adding desired ones — elimination beats competition for attention environmental design)."
The Protocol
(1) Within 48 hours of commitment failure, conduct the four-step diagnostic: Step 1 — Trigger: "What activated the competing behavior? What condition, event, or state led to the failure?" Step 2 — Decision point: "At what exact moment did I diverge from the commitment? What was the last point where I could have maintained compliance?" Step 3 — Structural match: "What support at that decision point would have maintained the commitment?" Match to Upgrade commitment enforcement to Level 3+ (environment, social contract, structural impossibility) when willpower has failed 3 times's hierarchy: Level 3 (environment), Level 4 (social), or Level 5 (structural impossibility). Step 4 — Install: deploy the matched structural support before the trigger recurs. Not "I'll think about it" — installed and active before the next trigger instance. (2) Do not add "try harder." If willpower was sufficient, the commitment wouldn't have failed.