4 · AMNESIA DRIFT

THE CITY

Every morning a new crew arrives at the gate. Skilled, tireless, willing. Not one of them has ever been here before, and none can ask yesterday's crew anything, because yesterday's crew is gone and left nobody behind. What they do instead is read the notice board at the gate — and then they build.

The notice board is therefore the entire memory of your city. Not a summary of it. The whole of it.

A board is a document, and documents rot on a different clock than cities. A wall gets moved on Tuesday; the notice describing that wall is amended on Tuesday only if someone remembers to walk down and amend it. Nobody is ever punished for forgetting, because the board looks the same either way. Do this for a year and the board is no longer a description of your city. It is a description of a city that used to be here.

The cruel part is that the crew does not doubt the board. It has nothing else to doubt it with. A wrong notice does not slow a tireless crew down — it aims them. They will build accurately, quickly, beautifully, in the wrong place, and hand you the invoice with justified pride.

And the notices you check least are the ones you need most. The emergency instructions — read once a decade, at the worst hour of the worst day — sit on the board for years with nobody's eyes on them, which is exactly the condition under which they go quietly wrong.

THE TELL

• You explain the same thing to your workers over and over.
• A worker confidently describes a rule you changed months ago.
• A correction you gave last month has to be given again this month.
• Your written instructions for the workers carry no dates.
• Nobody can tell you when your written description of the product was last read against the actual product.

FROM THE FIELD

The notice board itself. In the first city, one brief is loaded into every worker session — the standing orders, read before any work begins. The survey read it against the law it was summarizing. It had drifted in three places. One of the three described the city's strongest gate as advisory; the reality was a rule enforced at the source with nobody permitted to bypass it — the brief said "ADVISORY" where the ground held a "server-side branch ruleset, no bypass actors" (Engagement 01, F-001).

That particular drift ran in the safe direction: the brief understated a defense that was in fact solid. The direction was luck. The same mechanism tilted the other way tells every worker a gate exists that does not, and work ships through a hole everyone believes is closed.

The auditor, mid-audit, committing it. This receipt is the instrument's own and it is not softened here. During an audit built specifically to detect this pathology, the auditing worker needed something from the first city's document archive. It searched 86 documents by brute force, one after another, without opening the catalog that indexed them. The catalog existed; the habit of consulting it did not. The proposal written afterward names the event without mercy: "Amnesia Drift committed by an agent in the middle of an audit designed to detect it" (the first city's library-law proposal, receipts index R4.2).

Read what that costs the reader of this book: the instrument examining your city is built from workers with the same missing memory as the ones that built it. The shelf existed; the ordinance did not. That is why the ordinance exists now.

The runbook read at the worst hour. The first city's disaster-recovery procedure — the document a person opens during an emergency and follows literally — named an infrastructure project that had since been renamed. The finding's own words: "Line 16 was a current-state claim, and it was wrong." (Engagement 01, F-017). Nothing had failed. Nothing needed to. The defect was pre-positioned for the one day it would be read.

The drift-catcher that had drifted. The first city held a guarantee that its records could always account for themselves — the very thing Chapter 1's second records office broke. When the ledger wrote that incident up, it recorded something worse than the incident: the guarantee "was quietly false for demo the entire time" (the first city's ledger, DL-062). For one of its environments the promise had never been true, and nobody learned that, because nothing watched the watcher.

Half a guard. Later the city built a guard specifically to catch drift of a particular kind. It watched only half its assigned ground and stayed green straight through a genuine drift incident: "It was green throughout the DL-064 incident." (the first city's ledger, DL-065).

The counterweight, because this chapter can be misused. Not every mismatch is rot. Roughly 73 references in the first city's records to a fixed point in the industry's annual calendar were noticed, considered, and ruled to be domain facts, deliberately preserved — the ledger says so explicitly (the first city's ledger, DL-107). A crew that treats every repetition as decay will delete the city's own vocabulary and call it hygiene. Drift is a document disagreeing with the ground. It is not a document being old.

WHY AI WORKERS DO THIS

There is no mystery in the mechanism. An AI worker holds nothing between shifts. Every session begins from written material plus whatever you type in the first minute — that is the sum of what it knows about your city. It is not forgetful. It is new, every time, permanently. And it cannot tell a current document from a stale one: both are text, both read as fact, and a date on the page means nothing unless something compares that date to reality.

The second half is what owners feel personally. A correction made in conversation dies when the window closes. You did not teach the city; you taught one crew, for one shift, and the transcript is not the notice board. Unless the correction lands on the board, the next crew re-earns the same mistake at full speed — and you experience this as having the same argument, repeatedly, with a worker who has never met you.

THE COUNTERMEASURE

The ordinance, in these words:

"Anything a worker must know to avoid harming this city lives in one dated document, and that document gets read against the real city on a schedule — not when someone remembers. When you correct me and I accept the correction, write it into that document in the same shift, or the correction did not happen. And when the document and the city disagree, stop and say so out loud before you build."

Two additions only the mayor can supply. First: the emergency documents get checked most, not least — they are read once, under pressure, by someone with no time to doubt them. Second: the schedule is the ordinance. A brief nobody reads against the ground is drifting right now, at a rate nobody is measuring.

The honest limit is in the record above. Checking reduces drift; it does not abolish it. The first city's brief was governed and still drifted in three places (Engagement 01, F-001), and the guard built to catch drift stayed green through a real one (the first city's ledger, DL-065).

ASK YOUR OWN CITY

1. Find three things written down about your product that are no longer true. (Three, not one. Stale instructions are worse than none: they are confidently wrong, in writing.)
2. Read the standing instructions your workers load at the start of every session, out loud, against the actual product. Where do the two disagree?
3. The last time you corrected a worker — was that correction written into those standing instructions, or did it die when the conversation ended?
4. If every worker vanished tonight and new ones arrived tomorrow with no memory of this place, what would they have to read to avoid destroying it? Does that document exist? Is it current?
5. When was your written description of the product last updated, measured against the last significant change you made to it? Is it dated at all?