Every other level showed you things. This one shows you what is underneath them — and why a smiley face needs one part and a booking site needs twenty-one.
What architecture actually means
A treehouse needs some wood, a hammer and an afternoon.
A block of flats needs foundations, water pipes, a lift and a fire escape. It also needs a drawing of all of that, made before anybody picks up a hammer.
Both of them are buildings. Nobody thinks the treehouse was lazy. Nobody wants to live on the eighth floor of a treehouse.
Architecture is deciding what parts you need, and what leans on what, before you start.
Here is the bit that surprises everyone. You do not choose architecture by taste, the way you choose a colour. You choose it by what would go wrong.
Every single part on this page exists because of something that happens without it. That is the whole subject. Once you see that, the words stop being frightening.
The boring part is the part holding it up
Dig the foundations first, or do not bother. Then add floors and see what happens.
Nobody claps for the foundations. Nobody ever sees them. They are the only reason the eighth floor exists.
And notice what happened when it fell. Floors one, two and three were perfectly good floors. They came down anyway, because of a decision made before any of them existed.
The word your AI will use constantly
The list of parts is called a stack, because the parts sit on each other.
That is all it means. When somebody asks "what's your stack?" they are asking "what parts did you use?" — nothing cleverer than that.
Ten things you could build
From the easiest thing anybody ever makes, to the hardest. Each one shows the whole stack, and what the new parts are for.
How to read each one
Each build has a tower and a list. They always say the same thing, because they are made from the same thing.
The tower builds itself when you scroll to it. Foundations first, the part you can see last. Tap any part to pull it out and watch what stops with it. Follow a message sends one all the way through and back.
The parts marked new are the ones this build adds. Everything else came with you from the build before.
So how much do you need?
Three questions, in this order. Each yes costs you parts.
Does it have to keep working when your laptop is shut?
Yes means you need a computer that never sleeps. This is the biggest single jump on the whole page — three parts became seven.
Does anybody except you need to see the same thing?
Yes means a filing cabinet, and a doorway for reaching it. A pocket in your own browser cannot be shared with anyone, ever.
Would losing all of it be a disaster, or just annoying?
That one answer decides how much of everything else. Backups, checks, alarms and practice copies are all bought with the same currency: how bad is it if this goes wrong.
And a fourth, which changes the tone of all three: does money change hands? If it does, every answer gets stricter, because a wrong charge has to be fixed today.
The two mistakes
Building flats when a treehouse would do. This is the common one, and it is usually not your fault. Ask an AI for a booking form and it can happily hand you a login system, a queue and three rented services. Ask why each part is there. If there is no answer, take it out.
Building a treehouse and then adding eight floors. Also common. It works. It keeps working. Then one day it does not, and the thing that failed was decided months ago.
The right amount of architecture is the smallest stack that handles what actually goes wrong for you. Not the biggest one you can imagine.
Every part you add is a part that can break, needs looking after, costs something every month, and has to be explained to whoever comes next. Parts are not free just because the AI typed them quickly.
"What if I want it to send emails on its own?"
This question comes up early, and it always adds the same three parts. It is worth knowing them by name, because the answer is the same whether it is emails, texts, or a message into a chat app.
✉️ A postmanYou rent an email or text service. Never build one. Mail you send yourself mostly lands in spam, and fixing that is somebody's whole career.
🔑 A locked drawerThe postman wants a password. It can never live in the page, because anybody can read a page. It lives on the always-on computer.
📋 A jobs listSending is slow and sometimes fails. Nobody should wait for it, and nobody should lose their booking because an email service had a bad morning.
Then one decision, which is really an architecture decision in disguise: what happens when the postman is down?
Write your own copy down first. Tell somebody second. Always that order. A name you kept is a problem you can fix tomorrow. A name you never wrote down is gone.
Quality control
Architecture decides what can go wrong. Quality control is how you find out that it did — ideally before anybody else does.
Here is the only reason to bother doing it early. Press let one go, then catch the mistake as soon as you can.
🐝
The numbers are made up. The shape of them is not. The same mistake gets more expensive every hour it survives, and the jump at the end is not gentle — because by then you are not just fixing it. You are telling people, apologising, and working out what else it touched.
Quality control is not a thing you do at the end. It happens in three places, and they are all different jobs.
While planning — the cheapest place there is
Write the stack down before anything gets built. If you cannot say why a part is there, take it out.
For every part, ask: what happens when this one is broken? If you do not like the answer, that belongs in the plan. Not in a surprise at two in the morning.
Say what it must do. Then say what it must never do. The second list is the one people skip, and it is the one that matters when things get strange.
Decide what "working" means, in a sentence somebody could actually check.
Ask your AI to argue with your plan before it builds it. Ask what it would do differently, and what it is least sure about.
While building
Checks that run by themselves, every time. On this site they have caught a real mistake on every single level that had them.
Never fix a bug without first writing the check that fails because of it. Otherwise you never learn whether the fix worked, and you never notice when the bug comes back.
A practice copy, where things get tried before real people see them.
A second opinion that did not write the thing. A fresh conversation, or a different AI. The one that just built it already believes it did a good job.
Look at it on a phone. Every time, not at the end.
Once it is live — this part never ends
Something watching that it is up. Not you, refreshing the page.
An alarm that wakes a person, and only when it is real. An alarm that cries wolf gets switched off, and then it is worse than having none.
Somewhere the errors collect, that somebody actually reads.
Backups — and the bit everybody skips: actually restore one. A backup you have never restored is a rumour.
A way to put yesterday's version back in a hurry, without thinking hard.
Keeping the rented parts up to date. They change whether you were ready or not.
There is a checklist for this alreadySection 3's templates include a QC.md you can hand straight to an AI.
The single most useful line in it: ask a different conversation to check the first one's work. The AI that built something is the worst possible judge of it.
Give this to your AI
Paste this into the AGENTS.md file from Section 3. It turns most of this page into something that happens without you having to remember it.
AGENTS.md — add this
## Architecture
- Before building anything new, list the parts it needs
and why each one is there. Wait for me to say yes.
- If a part has no reason, do not add it.
- Tell me what stops working if each part is unavailable.
- Never put a password or key anywhere the browser can
see it.
- Save our own copy first, then call anybody else's
service. Never lose data because somebody else was down.
- Anything slow or likely to fail goes on a jobs list,
not in front of a waiting person.
- One fact lives in one place. Work everything else out
from it.
- Tell me when a change makes the stack bigger, and what
it costs to run each month.
- Before we launch anything: backups, a way to put the
last version back, and somewhere errors collect.
Things to try
Pull the always-on computer out of build four. Then do it on build seven. Count what stops each time. Same part, very different afternoon.
Find the part that stops almost nothing. There is one on every build. It is the part everybody thinks is the most important.
Compare build five and build seven. One hotel, then a million rooms. Of the parts that got added, count how many are there to make it work — and how many are there to stop it all breaking at once.
Follow a message on build six, then on build eight. One asks a question and waits. The other leaves a line open. That is the whole difference.
Write the stack for something you actually want. Before you ask for a single line of code, list the parts and why each one is there. Then ask an AI what you forgot.
Explain the foundations to a grown-up without using the word architecture. If you can do that, you understand it.