CONSTRAIN / PRECOMMIT

Add a voluntary boundary, delay, or friction before a predictable failure state arrives.

The cart is loaded, the total is $340, and the buy button is glowing. You know from experience that about half your late-night purchases get regretted by Thursday, but that knowledge lives in a calm past self, and the person at the checkout page at 11:40 p.m. is a different administration with different priorities.

Constrain or precommit means adding a voluntary boundary, delay, cap, or friction before a predictable failure state arrives, negotiated between your calm self and your tempted self while the calm one is still in charge. The cue is a failure you can see coming because it has happened before, on a schedule. The operation: name the predictable failure, such as impulse purchases over $100, choose the binding mechanism, like a standing 24-hour rule for any cart above that line, and build in a legitimate exception path for true emergencies so the rule survives contact with reality. When it works, the delay itself does the deciding: Thursday's cart, revisited, is half abandoned. The spec's cautions are about rigidity: a lock that cannot flex becomes its own hazard, as when emergency savings sit in an irreversible product just when circumstances change, and a tactic hardened into a permanent rule, like no contact after every conflict, can block the timely repair it was meant to protect.