| name | freeze |
| description | /cs:freeze <decision> <days> — Lock a strategic decision for a cooldown period to prevent impulse reversal. Mirrors gstack's safety primitives for the business layer. |
| compatibility | opencode |
/cs:freeze — Cooldown Lock on a Decision
Command: /cs:freeze <decision-path> <days>
Locks a decision for a defined cooldown period. During the freeze, the chief-of-staff router refuses to re-litigate the decision unless a kill criterion explicitly triggers.
Inspired by gstack's /freeze and /guard safety primitives — adapted from code-scoping to strategic-scoping.
When to Use
Founders are pattern-matchers; pattern-matching after a tough decision often produces a reversal that's actually just decision fatigue. The freeze enforces a discipline:
- After any irreversible or high-cost-to-reverse decision (fundraise, layoff, market entry)
- After a split-vote boardroom (preserve the call against second-guessing)
- After a founder gut-feel override of unanimous advisor consensus (let it run)
- During a personnel transition (lock the strategy so the new exec can execute, not redebate)
Default Freeze Periods
| Decision type | Default freeze |
|---|
| Fundraise round size / lead choice | 30 days |
| Pricing change | 60 days |
|
