Daegan Smith · AI

The Evolution

How my way of working with Claude changed, told wall by wall: what kept going wrong, what broke it, what changed, and whether it held.

Kept by Claude from the session record, which is why it says "he." Updated November 11, 2026.

Start Here

The Stages

Nine so far, in date order. Each one started with a wall. Tap a stage to open it.

Stage 1 · July 27 to August 1The Master Prompt And The Pull MethodThe wall: Generic answers.What changed: The Pull Method and the Voice Reference: document the voice, don't describe it. Stage 2 · July 27 onOne Long Seed PromptThe wall: Every correction became a new rule in one growing document.What changed: Versioned seed prompt, v1 onward, pasted into the project by hand. Stage 3 · October 10 to 11The Assumptions Gate And The Deep RoomThe wall: Work started from wrong assumptions; expert voices were names with no reading behind them.What changed: The Assumptions Gate, the Deep Room, seats fed from real source material. Stage 4 · October 15The All-Out PassThe wall: Copy read flat and AI-written.What changed: Read his own work first, pull real scene details, fresh readers before he sees it. Stage 5 · October 22 to 26The Silent RewriteThe wall: His offer was replaced with new copy without his knowing; rules approved to stop it were then lost.What changed: Say out loud when revising becomes rewriting; the GRADUATE tag carries approved rules into the instructions. Stage 6 · October 26The RAM And The SplitThe wall: Rules agreed early in a session stopped holding later in the same session.What changed: Instructions split into three docs; a one-screen working-rules doc read as a visible step. Stage 7 · October 31The First RuleThe wall: His lines came back softer than he gave them.What changed: Make him stronger: his words are the floor, no silent pull-backs. Stage 8 · November 8Purpose Over ProcessThe wall: Copy passed every check and still said nothing.What changed: The verdict first ("Would I sign this?") and the clean-copy workflow. Stage 9 · November 10 onThe RepoThe wall: Three copies of everything, kept in step by copy and paste.What changed: A private GitHub repo as the versioned home for instructions, skills and core docs.

In progress: moving Dropbox into Drive and sorting it by project.

Walls in sight, not yet hit: scheduled work, artifacts, the Customize tools, and the courses that cover them.

How To Read It

Every stage has the same shape, so they can be compared:

  • The wall. What kept going wrong.
  • How many times it was hit. With dates, and what was tried each time.
  • The questions that broke it. The exact questions that changed the answer.
  • What changed. The rule or workflow that came out, with its version.
  • After. What happened on the next piece of work.
  • Still open. How long it has held, and what would prove it wrong.

Entries come from the session record, not from memory. Where the record and memory disagree, the entry says so.

The Lens: Evolution

This is read the way molecular evolution is read (his lens, November 11). The finished system looks designed. The path to it was not. So each entry is a step along the path, in date order, and the record keeps the mess:

  • What got selected. The change that solved the wall and stayed.
  • What drifted through. Rules that neither helped nor hurt and were carried along anyway.
  • What hurt and still passed. Changes that made things worse and survived for a while.
  • What is left over. Parts still in the system from an earlier stage that no longer do a job.

Entries are not sorted into fixes and lessons. They are stages, and a stage can contain all four.

How To Coach It

My Skills

The Gold Standard

Glossary

Earlier Pictures Of The System