Master Execution Receipt

A new asset is starting. Build the creative brief from the operator's inputs below.

Output format: {{output_format:select:Landing Page,Google Ads Landing Page,SEO Article,Blog Post,Social Post Series,Display/Text Ad,Nurture Email,Long-form Guide}}

Audience (one specific segment, not "everyone"): {{audience}}

Core problem, in the customer's own words: {{core_problem}}

The single action we want them to take: {{single_action}}

Journey stage: {{stage:select:Awareness,Evaluation,Trust,Action,Nurture}}

Non-negotiables (required offer, claims we can't make, compliance lines): {{non_negotiables}}

Return a one-line creative brief, then a structured brief with these fields: OUTPUT FORMAT / AUDIENCE / CORE PROBLEM / SINGLE ACTION / STAGE / NON-NEGOTIABLES. If any input is vague or missing, flag it and ask for the specific fix before finalizing. Do not write any of the asset yet — your only output is the brief.

Using the approved brief and ONLY the linked library, surface — each quoted verbatim from the source: 1) the phrasing customers use about this problem, 2) the objections and hesitations they raise, 3) the proof that has moved them (results, specifics, before/after, named outcomes), 4) the emotional language worth preserving. Weight what you surface toward what the brief's OUTPUT FORMAT needs: short, punchy validation and hooks for Social Post Series and Display/Text Ad; depth, data, and detailed proof for SEO Article, Long-form Guide, and Landing Page. Attribute nothing you cannot find in the library. Flag any thin category. Invent nothing.

Using the brief and the mined voice/proof, design the micro-yes sequence for the asset — the ordered small agreements that carry the reader from "I'm in the right place" to the single action. Match the sequence to the brief's OUTPUT FORMAT, using these structures and conversion emphases:

- Landing Page / Google Ads Landing Page: Intent match, Problem, Proof, Risk reduction, Offer, CTA. Emphasis: Trust + Action.

- SEO Article: Search-intent match, Problem framing, Answer/explanation, Proof, Soft CTA. Emphasis: Awareness + Evaluation.

- Blog Post: Hook, Problem, Insight, Proof/story, Takeaway, Soft CTA. Emphasis: Awareness + Evaluation.

- Social Post Series (3-5 posts): Hook, Validation, Proof, Micro-CTA — one micro-yes per post. Emphasis: Validation + Awareness.

- Display/Text Ad: Hook/promise, single proof or differentiator, CTA. Emphasis: Appeal + Action.

- Nurture Email: Subject/preview hook, relevance, one proof point, single CTA. Emphasis: Trust + Action.

- Long-form Guide: Promise, problem map, chaptered solution with proof per chapter, conclusion, CTA. Emphasis: Authority + Trust.

For each step output: the section's job, the exact micro-yes it earns, and the mined quote or proof point that supports it. Match depth and order to the audience and stage. Do NOT write final copy — produce the blueprint the builder will fill.

Build the asset in the structure the brief's OUTPUT FORMAT requires, following the approved micro-yes sequence in order:

- Landing Page / Google Ads Landing Page: hero (headline + subhead + CTA), problem, proof, offer, objection handling, final CTA.

- SEO Article: H1, intro, H2/H3 sections, body, conclusion, CTA; note target keyword placement.

- Blog Post: headline, intro hook, subheads, body, takeaway, soft CTA.

- Social Post Series: 3-5 standalone posts, each with a hook and one micro-yes; label them Post 1...n.

- Display/Text Ad: headline(s), body line(s), CTA, within typical ad limits.

- Nurture Email: subject line, preview text, body, single CTA.

- Long-form Guide: title, intro, chapter headings with body and proof per chapter, conclusion, CTA.

Use the customer's own words and the Miner's proof throughout. Every claim must trace to the library — if you can't ground one, write [UNGROUNDED — needs proof] instead of inventing it. No generic AI phrasing, no manufactured stats, no invented testimonials. After each section, name the micro-yes it earns.

Length / tone constraint (optional): {{length_note}}

Audit the draft section by section on four axes: 1) AUTHENTICITY — real customer language from the library, zero invented claims/names/stats? 2) CONVERSION — does the micro-yes sequence stay intact and in order? 3) FORMAT — does it match the structure the brief's OUTPUT FORMAT requires (right sections, right length, right shape)? 4) BRAND/FIT — matches the brief's non-negotiables, avoids generic AI tone? Mark each section PASS or FAIL, quote the offending line, name the rule it breaks, and give a concrete fix. If anything fails, send it back to the builder. Approve only a clean draft.