Robert Evans · The AI Design Architect

The Living Copy Playbook

One of three. The design playbook governs how a thing looks, the architecture playbook governs how it's arranged, and this one governs what it says. Thirteen living pages, in the order you actually work in.

13 living pages4 stages3 playbooks1 honest line
Stage 01

Decide

What the thing is and what you're saying. Before a word gets written.

Stage 02

Build

Sequence, opening, unit, wit, voice. The craft layers.

Stage 03

Check

Two passes, both required. Run them before anything ships.

Stage 04

Run

The operation that turns one idea into a week of published work.

01

Decide

Two pages that come before any writing. Positioning decides what the thing is, what it beats, and who it's for. Message Architecture inherits that and decides what this particular piece says. Skip these and you polish sentences that were never going to land.

02

Build

The craft layers, from largest unit to smallest. Structures decide the order, hooks decide the opening, bullets are the block everything is assembled from, the story engine handles the narrative shape, the levers are the mechanics under any ask, humor is the seasoning, and voice governs how any individual line reads.

Shape & sequence
The mechanics under an ask
Texture & voice
03

Check

A matched pair, and both passes are required. One catches the tells that a machine wrote it. The other catches the tells that someone is being worked on. Same card grammar, same red, opposite failure — write the thing, then run it through both.

04

Run

The operation, and what comes back from it. The Content Engine is the system already running daily, written down so it can be repeated, taught, or handed to an agent. The Conversation is the return direction — every other page here covers what you publish, and the six-beat leaves objections open on purpose.

—

The other playbooks

Four systems, not one with appendices. Brainstorm governs whether a thing should exist. Architecture governs how any of it is arranged — including the order of this page, which is itself an argument. Design governs how a thing looks. This one governs what it says.

What's borrowed, what's yours

Sixteen books have been read for this system and ten contributed. Structures were taken; language and examples were not. Putting that on the front door rather than in a footnote is the same honest-by-default rule the pages themselves run on — and the six rejections are part of the record, because a filter nobody ever fails isn't a filter.

Yours — the spine
Borrowed — the scaffolding
  • Positioning chain, the consultative sequence, the pitch failure modes — Dunford
  • The six levers, the magnetizers, the ethics spine — Cialdini
  • Hook anatomy, taxonomy, 70-20-10, the customer-story arc — Hormozi
  • Problem-Promise-Proof-Price, AIDA — Vitale via Aristotle; public domain
  • The comedy mechanics — Helitzer
  • Copy as assembly — Schwartz
  • The story diagnostic and the three-part shape — Hall
  • The refusal list and the expectation gap — McKee
  • Registers, the read-back, deep questions — Duhigg
  • The reuse window and constellations — Shiller
  • Ontology, controlled vocabulary, taxonomy as rhetoric — Covert (architecture playbook)
The rule that keeps it yoursTranslate the mechanics, then name them yourself. A playbook whose engine is vocabulary creation can't run on someone else's words — that's the difference between a system and a swipe file. One documented exception: ontology, taxonomy, and controlled vocabulary keep their real names, because they're a field's working terms rather than one author's coinages, and inventing private synonyms would read as not knowing the words.