There have been some good questions in my previous posts about my agents, so I want to clear up a few things.
I call them agents because it helps me think and stay organized. But strip the jargon and here's what's actually happening: a folder with the right files in it tells an AI who it is, what it does, and what good looks like.
Unix figured this out a long time ago. I remember working on mainframes in my early 20s. Files in folders. It wasn't powerful because it was complex. It was powerful because it wasn't. Unix came out in 1969; I was using it from 1998 to 2002.
The "writing room" is a folder. Cash lives in it. His instructions, his guardrails, his examples, his voice reference — all files. The AI reads the folder and knows how to behave. The room gives it context. The files give it structure.
I have 15 of these rooms. Duke orchestrates between them.
The naming isn't the point. The structure is.
Here's the part most people miss: almost every agent in my system has a human counterpart. A real expert whose domain knowledge shaped the instructions — and who can tell me when the agent gets it wrong. Cash's counterpart knows copywriting. Trace's counterpart knows data. That feedback loop is how the system actually improves.
You're not building AI. You're building infrastructure.
Build the foundation. Build the structure. The agents are just what you call it when the rooms start working together.
My lesson: don't copy me, don't copy Jake, we all learn from each other, and then you make it your own. Stick to the fundamentals. Watch Jake's videos; it will rewire your brain and change how you think about AI. There are no shortcuts. You have to build a foundation first.