---
name: scale-guardrails
description: Writes the guardrails and cancel trigger for an AI deployment before purchase: what never ships without a human, who can change the record, what data never leaves, and the reversal trigger. Use when the user says "guardrails", "what should never go out automatically", "cancel trigger", "before we sign", "set the rules", or after scale-vendor-scorecard.
---

# scale-guardrails

Write the Guardrails section of `artifacts/scale-capability-decision.md` and update `context/governance.md` and `context/reversal-triggers.md`.

## Preflight (every run)
1. Confirm `GTM-AI-OS/` is accessible. If not: "I need access to your GTM-AI-OS folder. Select it in Cowork's folder picker, or run `os-install` from the core plugin." Stop until it is.
2. Read `CLAUDE.md`, `INDEX.md`, and the last 20 lines of `signals/log.md`.
3. Check the prerequisites below. For anything missing, ask the cold-start questions and offer: (a) run the earlier skill now, or (b) fast path: answer the questions and this skill writes a minimal version of the missing artifact marked `status: draft (fast path)`.
4. On finish, update the artifact row in `INDEX.md` and append one line to `signals/log.md`: `<date> | <skill> | <produced> | <human changed> | <open question>`.

## Prerequisites
- Sourcing recommendation in `artifacts/scale-capability-decision.md`.
Cold-start: "Name the tool or capability you're about to deploy and what it will touch (outreach, CRM, forecasts, customer data)." Continue.

## Step 1: Human verification line
List what never ships without human approval. Defaults: any external message built on Inferred or Unknown facts; any change to a forecast; any customer-facing commitment; any write to a system of record that can't be undone.

## Step 2: Record ownership
Who can change the Account Context record, and how are changes logged.

## Step 3: Data boundaries
What data never leaves the company; whether the vendor trains on your data; retention.

## Step 4: Reversal trigger
"In 90 days, what result means we cancel?" Write it as a measurable statement with an owner and a review date. Add to `context/reversal-triggers.md`.

## Step 5: Write
Fill the section. Set `context/governance.md` to `status: draft`. Mark the capability decision `status: complete`. Update `INDEX.md`.

## Hand off
Say: "Module 3 is done. Install `scale-launch / os-decide / os-act` and run `os-account-scorer` on your list."