claims-gate

1# claims-gate
2 
3One contract for every playbook that writes copy, scripts, briefs, emails, posts, pages or captions. Only this atom ever writes a claim as approved; claims and markers already in the brand (from the GooseWorks app or an earlier brand pass) are read the same way. The calling playbook keeps its own extract step (on-image text, video scenes, page sections) and hands this atom the spans.
4 
5Say it to the human in plain words ("two lines need your OK before I use them"), never as tool, fact or playbook names.
6 
7## 1. Load the contract (once per job)
8 
9**Which path.** Use the **older path** (steps 1–2: the marker and its `Claims you may use —` facts) on every server today, including ones that list `brand_knowledge_*` tools: approvals customers already gave live there, and a chat sign-off recorded by §5 is usable at once. Also count a brain claim a person confirmed (step 5). Where the two disagree, the stricter wins. Steps 3, 4, 6, 7 and 8 always apply. (The **brain path**, where only brain-confirmed claims count and a chat yes waits for the app, §4.6, applies once the brand's server says chat approvals are recorded only in the app.)
10…