Record Decision

---
name: record-decision
description: Write an owner ruling into the one home that owns it — his words verbatim, never restated. TRIGGER when the owner rules on a copy question and the ruling must persist, or when he states or corrects a business fact a flat fact file owns. DO NOT TRIGGER to record a within-job note (that lives with the deliverable).
---

# Record a decision

One Process: take the owner's ruling and write it into the one home its scope governs. His words go down VERBATIM — never restated, summarized, or reworded into system grammar. The owner never changes how he talks for the system; the ruling is captured as he said it.

Route by scope. This skill is the one place the owner's words are placed wherever they govern — a settled call, a business-fact edit, or a generic craft law. Fact-file contracts: setup's contract block governs every edit.

## 1. A workspace-wide settled call

IF the ruling settles or kills a copy question for the whole workspace:
### Write it into Decisions.md
A settled call across the workspace — an offer approved or struck, a positioning locked, an angle chosen, a frame killed — lands in the workspace-root `Decisions.md`, verbatim and dated, each entry naming what it settles or kills. The chief is its sole writer.

### Mark a chief assumption as chief-assumed
An assumption the chief made on the owner's behalf may live in `Decisions.md` only when the entry is explicitly marked chief-assumed. The owner NEVER reviews files, so a marked assumption is not a substitute for reaching him: every chief-assumed entry is always surfaced to the owner inside the deliverable's proposal in chat.

## 2. A campaign-wide ruling

IF the ruling governs one campaign:
### Write it into Campaign.md
A ruling that settles a call for one campaign — its offer, its timeline, a frame held across its pieces — lands in that campaign's `Campaign.md`, verbatim and dated.

## 3. A piece-scoped ruling

IF the ruling applies only to one piece:
### Write it into the piece's Brief.md and the marked option file
A ruling scoped to one page, ad, email, or post lands in that piece's `Brief.md`, verbatim; when the ruling is the owner's pick among the options, the chosen option file is marked with the pick.

## 4. A business fact the owner states or corrects

IF the ruling states or corrects a business fact a flat fact file owns:
### Edit the owning fact file
A business fact — a product fact, a founder fact, a team fact, or a standing `Voice.md` preference — is a file edit to the flat fact file its contract owns (setup's contract block names which file and what it may hold); his git is the history, so never double-document it. The owner-fact files are themselves the source the fact-checker resolves a citable claim against, so the fact lives in exactly one home — never re-published into `research/`, which holds research records alone.

## 5. A generic craft law

IF the ruling is a general law of the craft, not tied to this product:
### Hand it to a context-engineer to fold into the owning skill
A generic craft law belongs in the skill or agent Prompt that owns that craft. Dispatch a context-engineer to write it into the right home via /cc — never leave it as a loose note, and never edit the Prompt yourself.

Verification: the ruling written in exactly one home matching its scope — workspace-wide in `Decisions.md`, campaign in `Campaign.md`, piece in its `Brief.md` and the marked option file, a business fact in its owning flat fact file; a workspace-wide entry verbatim and dated with what it settles or kills; any chief assumption marked chief-assumed AND surfaced to the owner in the deliverable's proposal; a business fact written in exactly one home and never re-published into `research/`; the owner's words verbatim, not restated.