← The Evolution

AI · Updated November 11, 2026

Glossary

Every named thing in the system, in plain words, with when it first appeared. Sorted by date, so reading down the list is reading the system being built.

The Master PromptBefore July 27

His first system: a method for building a good prompt for any job, kept as its own document.

The Pull MethodBefore July 27

The steps he used to build a prompt: define the role, gather context in batches, state the task, set the format, test, refine, then move it into a Project.

A ProjectBefore July 27

A workspace in Claude with its own standing instructions and files. Marketing is one. Thinking Better is another.

The instructions (the seed prompt)July 27

The standing document Claude reads at the start of every chat in the Marketing project. It says how the work is done. Called the seed prompt until v1.66.

The instructions field and the pasteJuly 27

The box in the Project where the instructions live. Claude can't write to it, so every new version was copied in by hand.

Version numbersJuly 27

Each change to the instructions gets a number, v1 through v1.78 so far. The first 28 are separate files in Drive. After that it is one document edited in place.

Voice ReferenceBy late July

A document of how he talks and writes, with every line he picked or rejected logged in it, so Claude writes from his voice and not a generic one.

Own WorkBy late July

The Drive folder of his own letters, emails and course notes. It is the authority on his voice. Other people's material informs structure only.

Process VisualsJuly 30

A Drive folder made to hold a picture of how the process works at each version. The first attempt at this log.

No agreement theaterBy August 1

After a correction, Claude states what went wrong mechanically and moves on. No "you're right," no apology.

The belief chainBy September

The numbered list of things a stranger has to believe, in order, to get from where they are to yes. Copy is built on it.

The em dash ruleBy September 10

No em dashes in any copy, ever. Checked as its own step.

A living docBy late September

A document edited in place with its history kept, in place of a new numbered file for each version.

The councilBefore October

A fixed group of named direct-response marketers (Kennedy, Halbert, Brunson and others). Claude writes as each one in turn, so he gets several different takes on one line. A seat is one of them.

The Mastermind RoomOctober 1 to 3

The same people talking to each other about an idea, as a conversation, where the council only writes lines.

Live copy winsOctober 1 to 3

When a saved copy and the live page differ, the live one is the truth.

LockBy October 2

His word that a piece is finished. A locked line is never reworded, only placed.

A buildOctober 9

One thing being made from start to finish: a page, an offer, a deck. Each has its own log.

The decisions logOctober 9

One file per build. Every decision goes in the moment he makes it, so a later chat can read what was settled.

The Screen GateOctober 9

A short line of checks run under every slide before he sees it: numbers traced, nothing overlapping, nothing changed that wasn't asked for.

Closed numbersOctober 9

A number he gives is used as given. Claude does not audit it or ask him to prove it.

On TrialOctober 10

A holding area for new rules. Each has a date, a reason, what to watch for and when to decide.

Metaphor, Analogy, ParableOctober 10

A trial rule: suggest a picture or a comparison wherever an idea stays abstract. Still on trial.

An objectiveOctober 10

A new thing we set out to do. The gate runs once per objective, not once per message.

The Assumptions GateOctober 10

Before any new job starts, Claude lists what it is assuming (who it's for, what it sells, when, where, how much) and he marks each right or wrong.

Dream 100October 10

Chet Holmes's idea: pick the hundred best-fit buyers and go after them again and again, in place of approaching everyone.

An agentOctober 11

A separate copy of Claude started to do one job on its own and report back. Seats, fresh readers and simulated readers all run this way.

The Deep RoomOctober 11

The first brainstorm on a new job. Every seat runs as its own agent and thinks alone first, then the room talks.

The Bias PassOctober 11

Reading a piece for the mental shortcuts it uses on the reader, and the ones it could. Still on trial.

The readoutOctober 11 to 15

The intake flow that came out of the first Deep Room: an AI-made report that shows a business owner how strangers see them, with some findings held back.

The Schwartz DialsOctober 14

Two settings chosen before writing: how aware the reader is of the problem and the product, and how many times they have heard this kind of claim. From Eugene Schwartz.

The five MomentsOctober 15

The instructions reorganized by when a rule applies: when a job opens, before a line is written, before anything is shown, after a correction, at the end of the session.

The standard (How Daegan Judges A Line)Made the center October 15

The document that says how he decides whether a line of copy is good.

The frameworkOctober 15

The known format a piece lives in: sales letter, video sales letter, Invisible Funnel, story email. Named first, because it sets the order.

The provenance lineOctober 15

One line under every piece of copy that names what was read to write it and which settled decisions it touches.

The All-Out PassOctober 15

The five things done before he sees any first draft: 1 read his own work in the same format, 2 read the original source of every story and pull its real details, 3 make every section finish its thought, 4 have two fresh readers go through it, 5 name what was read.

The dictation ruleOctober 15

When he talks through copy, he is giving the idea, not the words. Claude writes it fresh. His words stand only when he says word for word, exactly, or lock it.

A fresh reader (the cold read)October 15

An agent that did not watch the piece being written, reading it as the stranger it is for.

Every example finishes the thoughtOctober 15

A story doesn't stop at the fact. It goes on to the owner's new life, hands the same picture to the reader, then asks.

The handoffOctober 15

A short document written at the end of a session so the next chat can pick up the work.

Ray Edwards's Copy RulebookOctober 17

Ray's rules, pulled from his two books into one working document and read on every copy job.

Own EmailsOctober 19

His own list emails from 2008 to 2015, word for word, mined for stories, subject lines and patterns.

The simulation (the room)By October 22

A made-up crowd of realistic people, 12 or 100 of them, who each read the copy cold and decide. It predicts; it does not prove.

Substance, not accountingOctober 22

Fix what changes the audience's experience. Leave alone the arithmetic nobody in the room is doing.

Revising is not rewritingOctober 25

Before a big rework, Claude says out loud that it is about to write new copy, shows his version beside the new one, and waits.

No parentingOctober 25

Don't remind him to check with, or get sign-off from, the people in his stories. He handles that. In project memory; not found in the current instructions.

DriftNamed October 26

Rules being followed early in a long chat quietly stop being followed later in the same chat.

A tool callUsed as proof from October 26

A visible action Claude takes, like opening a document. It shows on screen, so it either happened or it didn't.

The RAMOctober 26

A one-screen document, per job, of the rules in force right now. Claude reads it as a tool call before every batch of work.

The governing docsOctober 26

The instructions split into three: the instructions, the Doctrine and the Changelog.

The DoctrineSplit out October 26

The craft rules by format: emails, lead capture pages, offers, closes, slides. Read only when writing that kind of piece.

The ChangelogSplit out October 26

The history of every version and why each rule exists. It governs nothing.

The copy loadBy October 26

The reading done the moment a copy job is confirmed: the standard, Ray's rulebook, and the Doctrine sections for that format.

The GRADUATE tagOctober 26

A mark put on a decision in the log when it should become a standing rule, so it gets carried into the instructions at the end of the session.

A skillIn use by October 26

A packaged set of instructions Claude loads only when a job needs it, so it isn't carried in the main instructions.

The four simulation skillsOctober 26

conversion-sim (would they act), price-sim (which price), skeptic-study (why the ones who said no said no), copywriter-contest (other writers take a run at a working version).

The First RuleOctober 31

Make him stronger. His words are the floor: never softened without asking.

The intensity checkOctober 31

A list under the copy of his strongest phrases, each marked kept, sharpened or cut.

The say-backNovember 7 to 8

A reader restates a line in their own words. If it comes back blank, wrong or vague, the line failed.

Ideal conditionsNovember 8

In a simulation, everything outside the copy is set to perfect (the date works, the drive is short), so the result measures the words.

The Second RuleNovember 8

The rules always run, on every job, whether he names them or not.

The rules checklistNovember 8

All the rules that apply to a piece, turned into one list a fresh reader scores it against. 39 points on the home page.

The Third Rule (the verdict)November 8

Purpose over process. Every delivery opens with "Would I sign this?"

The line testNovember 8

Three questions asked of every line: what does it mean to the reader, why do they care, does it follow the line before?

The clean-copy workflowNovember 8

The order a page gets made in: purpose first, write to it, the line test, the verdict, his pass, Ray on top, emphasis last, simulation only to compare versions.

Ray on topNovember 8

After his pass, the copy goes through Ray's rulebook for words and moves, without touching his emphasis or adding facts.

Emphasis lastNovember 8

Bold and highlights go on at the very end, only on results and payoffs, a handful per page.

The repoNovember 10

A private GitHub repository that holds every version of the instructions, skills and core documents in one place.

Lens skillsBy November 10

One skill per copywriter (Halbert, Kennedy, Brunson and others) holding that person's method, loaded when their seat writes.

The talk-throughDate not yet traced

His long spoken runs about slides or copy, saved word for word to a file before anything else is done with them.

Cross-Project LearningsDate not yet traced

A shared document where a lesson from one project is logged so the other projects can use it. Seen once it is an observation. Seen in a second project it is a pattern.