Design pre-commitments when calm to constrain behavior when stressed — never make rules in hot states

Why This Is a Rule

George Loewenstein's hot-cold empathy gap research shows that people in "cold" cognitive states (calm, rested, fed) systematically underestimate how much "hot" states (anger, hunger, fatigue, stress) will influence their future behavior. You design a budget while well-fed and can't imagine impulse-buying when stressed. You plan a confrontation while calm and can't predict the anger that will override your script. The empathy gap means cold-state planning is always more rational — but it's also always overconfident about hot-state compliance.

Pre-commitment rules bridge this gap by converting cold-state wisdom into structural constraints that operate during hot states regardless of in-the-moment judgment. Odysseus didn't trust hot-state Odysseus to resist the Sirens, so cold-state Odysseus had himself tied to the mast. The constraint works precisely because it removes the decision from the hot state: the rule fires automatically, and compliance doesn't require willpower.

The asymmetry is critical: design in cold, constrain in hot. Rules designed during hot states encode the distorted priorities of the hot state — "I'll never eat carbs again!" during post-binge shame is a hot-state rule that cold-state you won't honor. Pre-commitments must flow from deliberative calm to emotional heat, never the reverse.

When This Fires

• When designing any behavioral constraint intended to override impulse, craving, or emotional reaction
• When you notice yourself making rules during emotional intensity — stop and defer to cold-state design
• When building Ulysses contracts (commitments that remove future choice)
• Complements Emotional trigger actions must be executable while emotional — don't design actions that require the emotion to already be regulated (emotional trigger actions) and Design triggers for your worst cognitive day — if they only work when you're sharp, they fail when you need them most (worst-case design) with the broader cold/hot state principle

Common Failure Mode

Designing rules during hot states: "After this terrible meeting, I'm implementing a rule that I never attend meetings without an agenda!" The rule might be good — but the timing of its design is contaminated by the emotional intensity of the meeting. Wait 24 hours, re-evaluate in a cold state, and design the rule with deliberative clarity rather than reactive frustration.

The Protocol

(1) Pre-commitment rules should only be designed during cold cognitive states: well-rested, fed, calm, not under deadline pressure. (2) During the design, explicitly imagine the hot state: "When I'm stressed and craving junk food at 10 PM, this rule will say..." Does the constraint still seem reasonable when you vividly imagine the hot state? (3) Make the constraint structural, not willpower-dependent: automatic transfers, physical barriers, environmental modification (Subtract unwanted affordances before adding desired ones — elimination beats competition for attention), committed partnerships (Ask 'Did you write for 30 minutes?' not 'Did you finish the chapter?' — process accountability triggers action, outcome accountability triggers anxiety). (4) When you catch yourself designing rules during a hot state → write the rule down but don't commit. Revisit in 24 hours during a cold state. If it still makes sense → implement. If it seems extreme → the hot state was distorting your judgment. (5) Never override cold-state pre-commitments during hot states. That's the whole point of pre-commitment.