Command:

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 and safety primitives — adapted from code-scoping to strategic-scoping.

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:

The decision record is updated in place:

undefined

... Status: FROZEN Frozen until: YYYY-MM-DD Reason for freeze: <text> Override condition: Kill criterion <name> triggers OR founder issues with stated reason

The active-freezes index is updated:

```markdown

Updated: YYYY-MM-DD

undefined

To unfreeze before the period ends, the founder runs:

/cs:unfreeze <decision> <reason>

The unfreeze is logged in the decision history (preserved permanently). Forced overrides create a paper trail that surfaces at post-mortem.

If a kill criterion in the decision triggers, the freeze auto-releases and the chief-of-staff routes immediately to . The freeze does not protect against reality; it protects against impulse.

Founders have authority. Without an explicit lock + log, every wobble produces a "let's discuss this again" — which is exhausting for advisors and erodes the value of the boardroom. The freeze is a process, not a rule; it logs every override so the post-mortem can audit founder discipline.

Version: 1.0.0