You’re not short on AI. You’re short on somewhere to put it.
You ask, it answers, you close the tab. Tomorrow it has forgotten you and you start again from nothing, which is why the tenth assistant feels exactly like the first. There’s another way to do this: one place that holds what you know, so the work that comes back sounds like you instead of like everyone. I’ve spent a while building that, and this is where I teach it.
Start with the writing →You don’t have to give me an email. The method is on this page before I ask you for anything.
The tools are fine. Not one of them remembers a thing about you.
Count what’s open right now. An assistant in the browser, another one inside the editor, a third baked into the notes app, and a folder of saved prompts you have not successfully found since the day you made it. Each one is good. Together they’re a pile. That pile is the shape of what you were sold, and nobody who ended up with it was being lazy.
Every one of them is a dispenser. A question goes in, an answer falls out, and then it goes back to knowing nothing about you. So tomorrow you explain who you are again. Next week you explain it again. The explaining is the work, and you redo it from zero every session, which is why none of this ever compounds.
The little that does get remembered isn’t yours either. It lives on somebody else’s server, in a format you can’t open, under terms that can change on a Tuesday without anyone telling you. You’re renting your memory, and rentals end.
So build a place instead of buying another tool. A folder on your own machine that holds how you work, what you sound like, the decisions you’ve already made, and the things you’ve ruled out. Every tool you point at it reads the same thing. The tool becomes the cheap part. The place doesn’t.
Swap every tool you own tomorrow morning. What still makes the work good is the part you wrote down.
Five moves. All of them work before you buy anything.
Nothing here is held back for a paid version. This is the method, written plainly enough that you can run it yourself this week. A method you can only rent isn’t one I’d trust either.
The folder is the memory
Make one directory. Put plain text files in it: how you write, who you’re for, what you’ve already decided, what you refuse to do. Every session starts by reading it. That’s the whole trick, and it’s boring, which is why almost nobody does it.
Start with one file called how-i-sound.md and paste in three things you’ve written that you liked. You’ll notice it on the first draft that comes back without needing to be rewritten into your own voice.
Name the job, not the worker
Don’t build “an assistant.” Define a job with one output. A researcher that hands back sources. An editor that hands back what’s missing. A designer that hands back three directions. When the result is wrong you know exactly which job to go fix, instead of arguing with a general-purpose fog.
If you can’t say what single thing the job hands back, the job isn’t defined yet. Fix the definition. The prompt is almost never the problem.
Write the judgment down
The second time you correct the same mistake, stop correcting it. Corrections live inside a conversation and die with it. Open the folder and write the rule into a file instead. Ten minutes of that beats a month of patient re-explaining, and it’s the only part of your setup that survives you changing tools.
It looks like this: “Never open with a rhetorical question.” One line, in a file, read every time. Done once.
Show the texture, not the metric
When you can’t prove a number, don’t reach for one. Describe what actually happened at a level of detail nobody could have invented. The reader is checking whether you were really there, and specificity answers that question better than a statistic ever did.
This one pays commercially, which surprises people. Everyone’s screenshots are inflated. Refusing is the single advantage on this list a competitor can’t copy by Friday.
The judgment stays yours
The machine does the labour. It reads, drafts, renders, gathers, builds. Two jobs never go on the list: nobody decides what’s true, and nobody decides what goes in. Those were always yours and they stay yours.
Hold the line at “it works from you, not for you.” The moment that flips, the output stops being worth publishing and you’re the last person to find out.
The long versions are below. There’s no email wall and no part two.
Writing
A five-part series on building quietly — now complete, best read in order on Medium.
Show Up Weekly, Even for Fake Clients
The reps you do before anyone’s watching — even for a client you made up — are the ones that make everything after them possible.
Read on Medium →Clone Your Expertise
Encode what you know once, and let it work without you — how one practitioner becomes many hands.
Read on Medium →Stop Doing the Work — Design Who Does It
Writing down what you know is only half of it. The leverage comes when you build the system that runs it — and step out of the doing.
Read on Medium →Honesty as the Moat
The reps, the encoded expertise, the system that runs it — all of it can be copied. Honesty is the one advantage that can’t.
Read on Medium →A Yoga Teacher Runs a Team of AI Specialists
The credential that’s supposed to disqualify me — I’m a yoga teacher — is the one that taught me to run a team of specialists. Where the whole series has been pointing.
Read on Medium →Field Notes
Shorter dispatches from the same workbench — the builds, the calls, what broke and what held. New ones land here.
What Yoga Did for the Body, AI Can Do for Thinking
But only if we meet it the way the West eventually learned to meet the mat: as a practice, not a product.
Read →I Thought I Was Writing a Book. It Turns Out I Was Learning How to Build Systems.
I set out to write a book. What it actually taught me was how to build a system — a researcher, a writer, an editor, a designer, each with a single job, handing off the way one breath follows the next. The manuscript turned out to be the byproduct.
Read on Medium →Everyone Is Building a Highway. I Am Building a Village.
The industry is racing to lay the roads between all your tools — one layer above everything, wiring every app to every other. Here’s the quieter thing worth building instead: not a highway you merge onto, but a place small enough to stand inside.
Read on Medium →The Village and the City
Almost everything written about building with AI comes from inside a fire at two in the morning — it was all breaking, a tool saved it, now go buy the tool. This is written from the quiet instead: the case for building something human-scale enough to live in, not a city you sprint to keep up with.
Read on Medium →Name the Job, Not the Worker
Give a tool a human name and you start treating it like a person — and three things follow, none of them the team you were hoping for. Name the job instead of the worker: keep each part a function, and the whole thing stays yours to recombine.
Read on Medium →Two Roads to the Same Machine
A friend arrived at the same architecture from the opposite end — the interface, not the repo. Same blueprint, it turns out, isn’t the same machine; the difference is the distance between standing a system up and growing one up.
Read on Medium →You Don’t Have an AI Problem. You Have an Operating System Problem.
Everyone’s collecting tools. Almost nobody builds the thing that makes them compound — the operating system you build for your own thinking.
Read on Medium →The Email That Vanished
An email quietly stopped reaching Gmail. The fix wasn’t a smarter tool — it was finding the one misconfigured record nobody owned, and the system that made it findable.
Read on Medium →AI is the 10%. The 60–30–10 layer framework, audited across three workflows.
Van Clief’s 60–30–10 framework gets reduced to a rule about boundaries. Audited across three real workflows, the boundary turns out to be only the visible edge of the system underneath.
Read on Medium →I Had a Second AI Grade My Work — and It Caught Two Bugs I’d Written
There’s a particular kind of confidence you feel right after you finish building something — and it should make you suspicious.
Read on Medium →The Field That Actually Decides
A monitoring rule paged a team at three in the morning and did exactly what it was told. The gap between following the rule and actually deciding is where the real system has to live.
Read on Medium →The Body Has Four Maps
Why bodyworkers keep losing rigor when they cross between traditions — and the tool built to stop the loss.
Read on Medium →The English Words You Already Know Are Hiding Inside the Thai You Can’t Read
The foothold for reading Thai was hiding in the English I already knew. The fix wasn’t a smarter AI — it was a file.
Read on Medium →The Coach That Refuses: Building an AI for First-Year Yoga Teachers
Most AI coaches answer everything. This one refuses — and the refusal is the feature.
Read on Medium →Why I Stopped Letting Claude Write Design Files in the Same Session as the Prose
Why design files and prose shouldn’t share a session — and what separating them fixed.
Read on Medium →The Quiet Ai · the film · silent
The method, running
Watch a system actually work.
This is ClearMind, free and open in a browser. It came out of the same folder and the same named jobs described above. What you’re reading below really happened; I’m replaying it word for word. One question at a time, then it waits.
ClearMind
you
ClearMind
you
the real question, named
The proof isn’t a client list. It’s one thing, built all the way through.
There’s no portfolio page on this site. One flagship, built with the five moves above, and you can watch it run.
The Quiet Scribe is a team of specialists for every job that surrounds a book. One goes and finds what’s already been said on your subject. One catches your words verbatim when you talk instead of type, and another orders the talking into chapters. There’s one whose whole job is reading the manuscript back and telling you what’s missing, what’s buried, and what you’ve said three times. One designs the cover. The last one builds the page the book lives on.
It does not write your book. It writes from you, not for you. Every line came out of your own hour of talking, nothing arrives from outside, and you keep or cut all of it.
Every pillar above is load-bearing in it. The folder is the memory, so it knows your subject on Monday and still knows it in March. Each worker is a named job with one output, so when something comes back wrong there’s one place to go. And the two decisions that were never on the list — what’s true, what goes in — never left the author.
I published three books the old, expensive way. Paid an editor, paid a designer, chased the layout and built the site myself, about a year on each one. Then I stopped trying to be all of those people and built the team instead. The next five took forty-five days; the last one took three. I was the slow one in that story for thirty years, with the same material in my head the whole time.
Come watch a whole book get built.
Saturday, August 8. Live and free. A real book goes from a folder on a laptop to a finished chapter, a cover, and a site, out loud, so you can see exactly where every decision sits.
Save my seat — free, Aug 8 →It isn’t for sale yet, and the workshop is the only door. That’s the one thing this page asks of you.
Some people read all of this, know it’s right, and also know they aren’t going to build it this year. That’s a normal place to be. There’s a way I do it with you instead. → How I work with people