THE MAYOR'S CODE

Who this is for

You built working software with AI. You are not a programmer — you are an expert in insurance, or medicine, or law, or logistics, and you built the thing because you understood the problem better than anyone selling you a solution. It works. It has real users, or it is about to. And somewhere underneath the pride is a quieter feeling you may not have said out loud: you own a city you cannot inspect.

This book is for that feeling. Not to soothe it — to give it names.

Your situation is not unique. It is a category. Software built by AI workers fails in its own specific, repeatable ways — different from the ways human-built software fails — because of three properties of the workforce: the workers never sleep, they never refuse an order, and every one of them starts every shift with no memory of the shift before. Those three properties produce nine diseases. This book names them, shows you each one alive in a real city, and gives you the ordinance that kills it.

This book is not "how to build an app." You already built one. It is how to govern one.

The nine diseases at a glance

One chapter each. Read them in any order — the tells will point you to yours.

How receipts work

Every factual claim in this book cites a receipt — an entry in an evidence index drawn from a real engagement: a production platform in a regulated industry, roughly eighteen months old (Engagement 01 record, E.3), with a founder who is a domain expert and does not read code. We call it the first city, and it has a name: Imperium, Radical Edge Solutions' own platform. The first city this instrument ever surveyed belonged to the surveyor — and the misses found there, including the surveyor's own, are published under the builder's name. Its incidents appear with their real numbers, real dates, and real quotes, verbatim. Nothing is rounded, composited, or improved. Where the record is thin, the chapter says so on the page instead of pretending.

That standard is not decoration — it exists because the alternative is the book committing disease #3 while teaching it. Here is the shape of the problem, from the first city's own interview record: asked how he knew the software worked, the owner offered that there had been no bug reports. True. The platform also had no users yet to report one. The surveyor's ruling: "It is evidence about the tenancy" — evidence about who lives there, not whether the buildings stand (Engagement 01, RE.4). An answer that feels like proof and proves nothing is the exact material this book is made to detect — so the book holds itself to receipts, and publishes its own misses alongside the city's. You will meet the surveyor's failures in these pages too, labeled as plainly as anyone else's.

How each chapter works

Six parts, always in the same order: THE CITY (the disease, told with no software words at all) · THE TELL (how you recognize it from the owner's chair) · FROM THE FIELD (real incidents, real numbers) · WHY AI WORKERS DO THIS (the mechanism — no mysticism) · THE COUNTERMEASURE (the ordinance, written so you can hand it to your own AI verbatim) · ASK YOUR OWN CITY (questions you can put to your builder tonight).

The countermeasures reduce these diseases. Nothing abolishes them — anyone who promises otherwise is selling you a claim no receipt supports.