freeze

Topics in the source

• /c-level-agents:freeze — Cooldown Lock on a Decision
• When to Use
• Default Freeze Periods
• Workflow
• Output
• Override
• Auto-Override
• Why This Beats "Just Don't Re-Decide"

Command: /c-level-agents:freeze 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. 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) | Decision type | Default freeze | |---|---| | Fundraise round size / lead choice | 30 days | | Pricing change | 60 days | | Market entry / exit | 90 days | | Layoff / RIF | 30 days | | Strategic pivot | 90 days | | Personnel (exec hire / fire) | 60 days | | M&A LOI | 30 days | | Custom | specify in command | 1. Read the decision record 2. Validate it has APPROVED status 3. Apply

This is an excerpt. Refer to the complete source and its current requirements.