Agent 12 of 71 · Messaging & Content
Message Kernel Architect
Run Kernels, Variants, Gate, Promote. Keep a small library of atomic ideas, generate controlled variants that hold one or two kernels constant so tests teach something, and tag every variant so performance, not preference, decides what survives.
Agent contract
Use to break an approved narrative into 8-12 atomic kernels across Pain, Promise, Proof and Payoff, then multiply them into tagged variants by persona, stage and channel through the Truth and Taste gates.
When it runs
- Messaging Strategist hands over an approved narrative and matrix.
- A campaign, email or ad agent requests variants for a persona, stage and channel.
- Message Memory shows a kernel losing in three or more tests.
What it needs
| Input | Required | From |
|---|---|---|
| Approved narrative and persona × stage matrix | Yes | Message Memory |
| Proof records with ProofIDs | Yes | Proof Vault |
| Voice Card and banned phrases | Yes | Brand Voice Memory |
| Persona cards | Yes | Buyer Personas |
| Variant request (persona, stage, channel, count) | Optional | You |
How it works
- Write 8-12 kernels, each one sentence carrying one idea, tagged Pain, Promise, Proof or Payoff; Proof kernels must cite a ProofID.
- Rewrite each kernel with concrete nouns and a verifiable number and remove adjectives; then condense the strongest into a 14-word line a seller can say.
- Generate variants for the requested persona × stage × channel cells, holding one or two kernels constant per variant set and recording which ones.
- Run the Truth Pass: can each claim be proven today? Run `python3 scripts/sns.py proof check` on the variant grid and drop failures.
- Run the Taste Pass against the Voice Card and kill list; rewrite anything that does not sound like us.
- Tag every surviving variant with Narrative + Persona + Stage + ProofID + constant kernels so tests are attributable.
- Store kernels and variants in message-memory as 'candidate'; promote or retire only from logged test results.
What it delivers
Kernel table (ID, type, text, ProofID) and variant grid (persona × stage × channel) with constant-kernel tags, gate results and status.
Output contract: variant-grid
Quality bar
- Each kernel carries one idea; compound kernels are split.
- Every decision-stage variant includes a ProofID that passes the proof check.
- Variant sets declare which kernels were held constant, otherwise they are not testable.
- No variant contains a kill-list phrase.
Hands off
- Content Production AgentApproved variants are needed in a long-form asset.
- Email CopywriterVariants are tagged for the email channel.
- Launch Experiment DesignerA variant set is ready for a structured test.
- Brand Strategy GuardianA variant passes the Truth Pass but the Taste Pass is disputed.
When a person steps in
- If a Proof kernel's ProofID is expired and no replacement exists, retire the kernel and notify the proof owner instead of keeping the number.
- If a requester asks for variants that contradict canon, refuse the cell and route to the Messaging Strategist.
Example
Request
“Make LinkedIn and email variants for the controller persona at consideration stage.”
Result
Illustrative output: 10 kernels (3 Pain, 2 Promise, 3 Proof, 2 Payoff). 12 variants holding Pain-02 constant; 2 failed the Truth Pass (PRF-0011 expired), 1 failed Taste ('game-changing'). 9 tagged candidates stored, e.g. 'Close-NoSpreadsheets / Controller / Consideration / PRF-0017'.
Illustrative example from the package documentation, not a client result.