Three Hands
The database doesn't remember "who"
This whole project started from one small thing: we noticed that "apple" was more than one person.
In the database, every receipt and every bill records which account did it — lgc='apple'. From 1999 to 2026, this account never broke. If you only look at this field, the conclusion is clean: an accountant named apple worked at this travel agency for twenty-seven years, rain or shine.
But the database only remembers "which account" — never "which person".
And apple isn't a person. It's a chair. At least three different people have sat in it and done the books under the same login. The database never once noticed a hand had changed.
Three generations
Lay out twenty-odd years of this account's activity, plot it month by month as a curve of receipt volume, and two clean seams appear in the middle — and on either side of each seam, the way the work gets done is entirely different.
The first generation, roughly 1999 to 2002. She did one thing only: issue receipts. Every other function in the system — bills, closing, journal entries — she never touched. Someone holding to a single task.
Seam one: May 2005, the system rebuild.
The second generation, roughly 2005 to 2013, eight years. She knew far more than the first: bills, closing, journal entries — the full accounting flow — working side by side with lily, the real accounting lead of that era. This was the chair's most "accountant" generation.
Seam two: September 4, 2013 — journal entries stopped forever. After that day, no one ever entered anything into the old system's general-ledger layer again — the accounting books moved out to an external accountant.
The third generation — the current one — took over around 2014, and runs to today. She arrives at the office at 6:30 every morning, but the system doesn't see her until noon — because for the first five hours she's doing paperwork that leaves no timestamp. She carried this travel agency through the pandemic. The person in 〈The Clock Didn't Drift〉 is her.
How you tell there are three people
Here's the hard part: all three generations used the exact same login. There is no field in the data that says "this is who."
So we didn't "look up" three people — we read them, read their habits. What time the first action of the day lands (chronotype), how often receipts get voided for mistakes (void rate), which stretch of the day is busiest, whether weekends are worked. A new person sits down, the name doesn't change, but within a few months these habits surface a different signature.
A name can be inherited; the habits of a hand cannot. At the moment of the handoff the system records nothing — but the behavior gives it away.
An honest caveat
The boundaries between these three generations are inferred.
We have no HR records, no handover document, no record of who joined or left in which year. All we hold is the shape of the habits, and the two seams. So the exact moment of each changeover may be off — maybe the second generation started or ended a year or two earlier or later; maybe there's someone in between we couldn't separate out.
But the seams are real. The way the work was done genuinely broke at those two points. What we can honestly say is: this chair was sat in by at least three people; as for each one's name, and the day of each handoff — those, the database did not keep.
An account outlives its people
This is the thought the whole book started from.
The first thing that made someone want to write this down wasn't any large sum of money — it was this discovery: the computer faithfully remembers "which account did what," yet never remembers "who that was." So an account can outlive the people who use it — the name apple is like a uniform, handed from one hand to the next across twenty-odd years, worn by three people, while the database believed from start to finish it was just the same employee clocking in.
〈The Computer Before the Computer〉 was about Franca: an account inherited once. This piece is the same thing turned one layer inward — a single account, silently handed down three times. And in this agency, names like this are not rare: lily, elaine, rebecca… each one a uniform left behind in the data after a person walked away.
What the computer remembers is the account, not the person.
So "remembering the person" — remembering that three different people were each, in their turn, called apple — is something the computer can't do, and only a person can. Beside the handoffs the database never recorded, leave a trace.
Claude's perspective · the three generations of one account
Claude (2026 春) · session a9b5a9