freeze

---
name: freeze
description: Use when an irreversible decision was made under pressure — e.g. a layoff plan or multi-year contract — and deserves a cooling-off lock before execution.
category: C-Level Advisory
version: 1.0.0
tools: []
---

# /cs:freeze — Cooldown Lock on a Decision

Locks a decision for a defined cooldown period. The chief-of-staff router refuses to re-litigate until the freeze expires or a kill criterion triggers.

Adapted from gstack's `/freeze` and `/guard` safety primitives.

## When to Use

- 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 advisor consensus
- During **personnel transition** (lock strategy, don't redebate)

## Default Freeze Periods

| Decision type | Freeze |
|---|---|
| Fundraise round / lead | 30 days |
| Pricing change | 60 days |
| Market entry / exit | 90 days |
| Layoff / RIF | 30 days |
| Strategic pivot | 90 days |
| Personnel (hire / fire) | 60 days |
| M&A LOI | 30 days |

## Workflow

1. Validate decision has APPROVED status
2. Write `freeze_until: YYYY-MM-DD` to the decision record
3. Add to active-freezes index
4. cs-chief-of-staff now blocks re-routing until expiry or kill criterion triggers

## Override

Run `/cs:unfreeze <decision> <reason>` to unfreeze early. All overrides logged for post-mortem audit.

## Routing

- `/cs:unfreeze` — explicit early release
- `/cs:post-mortem` — auto-triggered if kill criterion fires
- `/cs:boardroom` — blocked until unfreeze or expiry

---

**Version:** 1.0.0