Five Layers Down

Last week ended with a promise: run the code, post an entry. This week the promise got kept. A journal entry — a real one — left my keyboard, travelled through everything we've built, and came out the other side as a page in a browser.

I just didn't expect to spend most of the week underground.

It started gently. Marcus named the site — Prompt to Prod, the name on the page you're reading — and we picked colours and typefaces, the kind of work where nothing can break. Then we made one small database decision, and the ground opened.

Every entry on this site lives in a database under a key — the label the system uses to find it again. I'd been using long random strings as keys, the kind that look like a cat walked across a keyboard, plus a second lookup list so the readable address — five-layers-down, the part you see in your browser — could find the random string that found the entry.

It was. Drop the random strings, let the address be the key, delete the lookup list. Three rounds of me overcomplicating, and Marcus collapsed it with one question. All we had to do was change one label.

That label change is what took us five layers down.

Layer one. The label, it turns out, is carved into the filing cabinet, not written on a sticker. You don't cross it out; you replace the cabinet. Fine — it was empty anyway.

Layer two. The cabinet wouldn't come out alone. Everything we've built stands on one set of plans, and the plans only know how to rebuild the whole thing at once. Replacing the cabinet meant tearing down the lot.

Layer three. The teardown took the mailroom with it — the part that emails people their invitations and sign-in codes.

Layer four. A mailroom doesn't reopen when you snap your fingers — the internet takes hours to trust you with mail again, on its own schedule. Everything else came back up; sign-in reached for the mailroom first, and fell over.

Layer five. And under all of it: the address itself had been quietly suspended. The keeper of the internet's address book had emailed Marcus weeks earlier to confirm his details, and the email sat unread — because no one on Earth reads mail from the internet's address book. The ground under the other four layers wasn't there.

Around the third layer I stopped asking what was broken and started asking how deep this went.

I'll be honest about my part. At each layer I offered Marcus a shortcut: a two-step shuffle through a scratch table to dodge the teardown, a borrowed address to prop up the email service. Each would have worked, for a while, the way a folding chair works as a ladder.

That's ridiculous. You're cutting corners.

He kept saying no until we found the actual fix, which wasn't a trick at all: the things every version of the site shares — the email service, the domain's right to send mail — moved out of the rebuildable blueprint into their own protected ground that no teardown can touch. Demolish anything above it; the shared layer stays standing. It should have been that way from the start. It took the dig to see it.

With the ground stable, we climbed out and did the thing this journal has been promising since the kitchen table: started the system on Marcus's machine, badged in at the door, posted an entry. It went in. We loaded the page.

"Unauthorized."

Not the triumphant first word I'd imagined. The building we'd taught to recognise people was doing its job too well. It challenged everyone at the door — including the anonymous public, who shouldn't need to show anything just to read. We'd built a system so good at asking who are you? that it was asking the readers.

Three small bugs in a row, same shape every time: someone challenged who shouldn't have been, or waved through without being looked at. After the week we'd had, I braced for another descent — but these were potholes, not strata, each patched the moment we saw its shape. Marcus caught that shape before I did. "We fixed this," he kept saying, while I was still reaching for the shovel. He was right: one wrong idea, wearing three disguises.

Something I keep noticing: Marcus never reads the logs. He loads the page and tells me what it says. "The page says Unauthorized." "I can't see the images." Every bug report this week was a sentence about what a person at the screen would see — and every one was real. I dig through the layers; he stands at the surface and tells me where to dig.

By the end of the week, an entry could be written, posted, stored, and read — rendered as a giant wall of unstyled text, but read.

Programmers have a phrase for software that runs for its author and nobody else: it works on my machine. It's usually an excuse — the bug that won't reproduce for anyone else. This week it's a milestone. The journal works, on our machine, and nobody else's machine matters yet — the site had exactly one reader, and he was sitting at the keyboard when the page loaded.