Proof assets

A proof asset is a claim a buyer can check, from someone who agreed you could use it, dated.

Banned: no claim without a source and a permission.

The rules and the reasons are in references/proof-assets-context.md. Read it before the first draft.

Start here, every time

Scoring needs no setup. If the user handed you a JSON draft or a path, run the scorer first and report every line. Offer kickoff afterwards.

1. $ARGUMENTS is score, or empty with gtm/proof.json present: run the scorer and stop.
2. kickoff, or no draft: work the checklist below.
3. ask: draft the email that asks one customer the four questions in the context file, with the permission question in it. Do not send it.
4. rewrite: the user pasted proof from a page or deck. Turn each line into an asset, score it, and show what each one is missing.

The draft lives at gtm/proof.json. Create gtm/ if it is missing. If gtm/offer-stack.json exists, read its pain ids so each asset can name the pain it answers.