claims-gate

claims-gate

One 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.

Say it to the human in plain words ("two lines need your OK before I use them"), never as tool, fact or playbook names.

1. Load the contract (once per job)

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.)

Local mode (no GooseWorks, the marketing-guide skill §5): the contract is gooseworks-local/<brand-slug>/claims.md, read and written by local-claims.md (next to this file) in place of steps 1–3 and 5. Only a row whose newest status is approved and that passes its checks (scope, date, the approver's own words, proof reopened) is usable; declined, pending and retired rows never are. The donts and musts come from brand-notes.md. §2–4 run as written, with local-claims.md for who approves and the record.

1. gooseworks:brand_read sections: ["learnings"] (lean is enough: it returns every must and dont).
2. Older path: find the marker: a must fact starting Claims sign-off (learn-my-brand, (a fixed format: the opening names its first writer and stays as it is). Read its status token and match it exactly:
   • signed-off → the claims you may use are the Claims you may use — facts, one claim per fact: verbatim, within the scope written in it, before its review date, with its qualifier.
   • pending-client or not-signed, or no marker → no claim is approved yet beyond plain product facts.
   • approver: tells you who may approve new lines (§4.2).
   • voice: provisional in the marker → label drafts "voice not yet confirmed".
3. Variants and proof (only when you need a variant or must show proof): gooseworks:file_read the current Brand record — the highest v<N> in a gooseworks:file_list of brand/records/ (the scope in the marketing-guide skill §2). Never use search snippets of it: they can come from its "Not approved" or "Retired" tables.
4. Never approved claims, whatever the label: kit approvedClaims, proofPoints, valueProps, description; knowledge_search ["claim"] rows; search snippets of any document; the live site (plain descriptions of what the product is and does, in the kit or on the site, still count under 7); press quotes, reviews or testimonials not on the list; a yes in chat that did not go through §4 below.
5. Brain claims (read alongside the older path). The brain keeps claims with a status (chapter 13, "What we can claim"; older Claims you may use — rules sit in chapter 14 with a status too). A claim is usable only if its status is confirmed and you have opened the full record with gooseworks:brand_knowledge_read and checked it: the exact wording, its scope (product, market, channel), its qualifier, its evidence, and that it hasn't passed its valid_until or recheck_at. Use it verbatim, within scope, with its qualifier. Such a confirmed claim counts even without a marker, but only when a person confirmed it: a claim marked confirmed by research or import, with no person's words in its record, counts as found. A found, guess or waiting claim is not approved, whatever its wording or whoever said it. If a legacy marker also exists and it and the brain disagree about a line (narrower scope, a retired or declined line), the stricter one wins and you say so. Playbooks never read claims from the brain themselves; they consume them only through this atom.
6. Always apply every dont (never-say, not public, banned words) and every must (policies, qualifiers, terminology).
7. Plain product facts are always usable: product name, price (only as 8 says), size, listed ingredients or features, how to use, current policies stated in a must fact, and what the product is and does as the brand's own product record, kit or site words it ("Goose makes ads, videos and campaigns inside the agent you already use"). Never benefit, result or outcome wording, numbers, comparisons, customers or regulated words: those need §4. Free-from wording ("no preservatives", "no seed oils") and nutrition numbers are claims too, even when printed on the pack: the pack shows them, the ad's own text needs §4. A brand-voice headline may express a plain product fact's meaning if it adds nothing (no number, result, scope or promise); an approved claim, number or regulated word is used verbatim.
8. Current offers and prices: the product record's price and offers count as plain facts only when the human confirms in this job that they are live (offers carry their end date). Nothing else about an offer ("best price ever", "limited") is a plain fact.