The lock was the surface. The system was underneath.

EDITION 002 / SUNDAY MAY 3, 2026

[ solo stack ]

Run lean. Stack smart. Compound forever.

When I was twelve, my school got new computers. Real ones. Win95, glowing CRTs, a whole lab of them.

The teacher locked the workstations during off-periods so we couldn't play games. There was a password on the screen. We were supposed to wait until class.

I learned the commands to bypass it. Not because I was a genius. Because I read the manuals. The password was on the screen, sure. But the commands underneath the password, the ones that controlled what the password actually did, those were also right there. The teacher just hadn't bothered to look.

My friends and I played games for half of seventh grade.

I think about that story a lot now, watching how operators are using AI.

Most of us are looking at the lock. The prompts. The chat box. The "five things ChatGPT can do for your business" listicle. We're treating the surface like it's the whole game.

It isn't. The actual game is what's underneath.

Walk through a house with me. The previous owner left it half-finished. The kitchen layout is wrong for how you cook. The bedrooms are oddly placed. There's a closet that opens into another closet for some reason.

Most people, in that house, would do what most operators do with AI. They'd buy paint. New furniture. A nice rug. They'd make the surface look better and call it good.

But the actual job, the job that takes the most time and matters the most, is reading the blueprints. Where are the load-bearing walls? Where does the plumbing run? Where can you safely take down a wall to make the kitchen work?

You don't paint a room before you know where the studs are. You don't decorate a house you haven't mapped.

AI is the same. The prompts are the paint. The blueprint is the system underneath. What your business does, who does it, when, with what context. Owners who skip the blueprint end up with a beautifully decorated AI workflow that doesn't fit their business and breaks the moment something real happens.

Closer to home for most operators: when you hire someone new, you don't hand them a task list and walk away.

You walk them through the business. Who reports to who. Where the files live. What the customer expects. What's allowed and what isn't. The unwritten rules. The history. The "we tried this before, here's why it didn't work."

That walkthrough is the entire difference between a hire who's useful in week one and a hire who's still asking basic questions in month three.

Prompts are like the task list. Useful, but only if the walkthrough already happened. Most operators are typing tasks into a chat box that has no idea what their business actually does, who their customer is, what good looks like in their world. Then they wonder why the answers feel generic.

Here's the rule I keep coming back to.

Mapping means writing it down. Plainly. What your business does. Who does what. When it's done. What success looks like. What you'd never do, and why.

That document (or set of documents) is the walkthrough you'd give a new hire. It's also the blueprint AI needs to actually be useful in your business, not in the average business the model was trained on.

Most "AI consultants" are selling prompts. The win is the map.

The Grade 7 kid wasn't smarter than the teacher. The kid just looked at what was actually happening, instead of accepting the surface.

That's the move with AI. Stop accepting the lock. Start asking what's underneath. The word for that work is mapping. It takes longer than collecting prompts. It pays for years.

[ THIS WEEK'S ASK ]

Hit reply and tell me one process in your business that runs entirely in someone's head. The kind that nobody wrote down because the person who does it has been doing it for years. That's a candidate for mapping, and the answers shape what I write next.

If this one hit, forward it to one operator who's buying paint when they should be reading the blueprints.

[ BUILD LOG ]

[ STACK MATH ]

One number this week:

12,000

Lines of mapped system running across my businesses on AI rails.

Without the map, the prompts are just paint.

[ NOTE ]

Sunday afternoon. Edition #1 went out last Tuesday, edition #2 goes out this Tuesday, and right now the cursor is blinking. Coffee's cold. I keep telling myself the work is mapping the system, and then I sit down to map the next system. It's the job. Same as it is for every operator reading this.

See you Tuesday.

— [ solo ]