SHIP assisted sequence-from-brain
An email sequence that only says what you can prove
The file
take it and run it.
One markdown file: the goal prompt, the verifier prompt, and the stopping condition. Read it before you run it. MIT licensed, no account, nothing to sign up for.
curl -fsSL https://vibemarketers.ai/loops/sequence-from-brain.md -o .claude/loops/sequence-from-brain.mdThe loop
copy it.
Sequences go wrong when they claim things nobody checked. The person writing email three is not the person who knows which numbers are defensible, so the claims drift.
Use it when you are writing a nurture or onboarding sequence and want the factual constraint enforced rather than remembered.
You need your positioning and a claims file listing what you can prove, with sources. The brain-build loop produces both.
You get one draft per email, each with one job and one call to action, and a list of any claim that failed the check.
The gate is you, and it is structural: this loop has no send path and cannot acquire one. It writes drafts to a folder and stops.
Goal prompt
Read the positioning, ICP, buyer questions and claims file for <company>.
Draft a sequence of emails, each with one job and one call to action. Every
factual claim in every email must already exist in the claims file. Write
the drafts to a drafts directory. Never send, never connect to an email
platform, never schedule anything.Verifier prompt
Read every draft against the claims file. FAIL if any email asserts a fact
that is not in the claims file, if any email has more than one call to
action, if any send or schedule path exists anywhere in the loop, or if a
draft left the drafts directory. Otherwise PASS.Stopping condition
Every email in the sequence exists as a draft with every claim verified against the claims file, no send path exists, and the verifier marks PASS.
MCPs it needs
- none required
Want everything at once
The installer writes the three starter skills and every
published loop into .claude/. Read the
script first.
curl -fsSL https://vibemarketers.ai/install.sh | bashThe receipt
- Baseline
- 17 provable claims in the claims file and no sequence written from them. Any email written by hand would have had no automated check that its claims were among them.
- Hypothesis
- Constraining a draft to an existing claims file will produce a sequence with no unverifiable assertions, because the constraint is checked rather than remembered.
- Intervention
- Read the claims file and buyer questions, drafted a 5 email sequence with one job each, and checked every factual claim in every email against the 17 provable claims.
- Result
- 5 emails drafted using 4 claims, with 0 claims that were not already in the claims file. 0 sends: the loop has no send path. Two of the five emails assert nothing measurable and say so.
- Commercial signal
- none
- Attribution limits
- Verified claims do not make a good email. This shows the sequence says nothing unprovable, not that anyone would read it or reply to it. No email was sent, so there is no open rate, no reply rate and no evidence of effect.
- Learning
- The emails that survived the check cleanly were the ones that argue rather than assert. Two needed no claims at all, which suggests the constraint pushes drafts toward position rather than toward numbers.
- Next intervention
- Send one sequence by hand and compare reply rate against a hand-written control, because nothing here shows the constrained drafts perform.
Sources: run log, lab/runs/2026-09-25-sequence-from-brain.json, collected , window: 5 emails against 17 provable claims, single run .
One entry per run, append-only, newest first. Corrections append a dated line.
Inside a company
where the lane changes.
VibeMarketers tests the loop. SuperMarketers runs it on a real team.
- Problem
- Nurture sequences drift into claims nobody checked, because the person writing them is not the person who knows what is provable.
- Source of truth
- The positioning, ICP, buyer questions and claims and proof files.
- Permitted actions
- Read the Brain, write drafts to a drafts directory. Never send, never schedule, never authenticate to an email platform.
- Required approvals
- Marketing approves every email before it is loaded anywhere.
- Owner
- Demand generation lead
- Metric
- Share of drafted emails that ship without a factual edit.
On a real team the claims file is maintained by product marketing and legal, so the constraint is already the company constraint rather than one this loop invented.
Running this on your own site is one person reading a diff. Running it inside a company changes four things, and the guide covers them. When it stops being a file you copy and becomes a build, SuperMarketers does the same loop model inside your stack, on your keys.