For most of the forty-seven years in the ledger, subtraction was something done to Robert Samuel White. A father who threw him out. A dozen removals from housing between seventeen and twenty-seven. A search engine that dissolved a decade of travel revenue. Teeth that went. In January 2024 the direction of that verb reverses. The medications go — twenty years of opiates, benzodiazepines, sleep and anxiety prescriptions, ended at once and not resumed. The cigarettes go after thirty years. The ten-year client goes, and with it the last income, the unpaid balance written off in the same motion. The contents of the Lexington house go. Nothing in the record was taken from him that month; every departure was authored. That is the change, and it is not a change of circumstance — the circumstances were already collapsing. It is a change in who is holding the knife.

What held is older than any of it and easy to miss because it never announces itself. When his father sold the family computer around tenth grade, he wrote code on paper and ran whole systems in his head until there was a machine again. That capacity — to keep a system running with its substrate removed — is what January 2024 asks of the man rather than the boy. He pulls out the pharmacological floor, the nicotine, the income, and the address in roughly the same weeks, and the thing that continues running is the practice of recording. Three sets of photographs, spaced fifteen days, four days, twelve days. No commentary. Documentation was not a response to any of it; it was the layer underneath that the removals could not reach.

The turn is smaller than the demolition and easier to overlook. Somewhere in there he recognizes that he is lonely, and calls Brandon, and asks him to go for a drive. Twenty years in a house alone, cut off from everyone but his parents, is described in the ledger as contained sovereignty — a state he defends rather than laments. Naming loneliness and then acting on it is the first entry in the record where solitude is treated as a condition with a lever on it rather than a preference to be held. Everything else that month is a thing ending. That is a thing beginning, and it is the only one.

What January could not see is that it was the last winter with an address, and that the photographs are therefore the closing frames of a fixed dwelling rather than three ordinary intervals in an ongoing practice. It also could not see that stripping everything simultaneously would hold. Coming off a high opiate dose cold turkey while ending the income and the housing in the same weeks is not a plan anyone endorses; the ledger's later entries confirm he never went back to any of it. From inside, that was unknowable, and it is worth saying plainly that the record shows a man betting the whole structure on a single throw and being right — not a man executing a staged transition. The ledger's own dating tangles here, some entries placing the RV departure on a birthday in 2023, others placing the decision in January 2024. The tangle is itself evidence: this was one continuous act of leaving, and the participants in it, including him, could not cleanly say where it started.

The last thing available only from outside is what the silence was. The loudest month of subtraction in his life produced no argument, no analysis, no transmission — only images, temperature zero. It would be easy to read that as a thin month. It is the opposite: the record thins precisely where the events thicken, because narrative is what he makes afterward, and capture is what he does while his hands are full. The method he would later build an entire infrastructure around — observe, commit to record, decline to interpret until interpretation is earned — was already fully operational in January 2024, running unnamed, in a house he was emptying.

The binding constraint in January 2024 in Lexington is not capacity — it is demand. Three capture events across thirty-one days is a duty cycle under ten percent: Jan 15, Jan 19, Jan 31, with fourteen days of nothing before the first, a four-day gap, then a twelve-day gap, mean interval 10.3 days. A system operating at that rate is not saturated by anything. The recording subsystem ran, the operator was present at each capture point, and nothing in the month drew on more than a tenth of the available days. This is idle telemetry from a machine with large reserve, and the reserve is the finding: whatever else January was, it did not consume the documentation channel. Compare that to the load a single institutional escalation later places on the same operator, and the shape of the reserve becomes legible — the capacity existed in Lexington and went unclaimed.

Flows are one-directional. Images enter the archive — five on Jan 15, count unrecorded on the other two dates — and nothing leaves. No text transmission, no publication, no outbound signal of any kind for thirty-one days. The store accumulates monotonically with no drain, which means the cost of the archive is not paid at capture time; it is deferred to whatever later process has to index, caption, and interpret it. That bill comes due here, twenty-five months downstream, and it comes due against a record that provides three dates and one photograph count. The capture was cheap. The reconstruction is expensive, and the expense was incurred by the design, not by the month.

The control law is inferable only from spacing, and the spacing says keepalive rather than alarm. An event-triggered logger produces bursts — clustered captures around whatever crossed threshold, long dead stretches otherwise. What is actually here is quasi-uniform: a heartbeat at roughly ten-day intervals, not correlated with anything that announced itself. rswfire's implemented controller in Lexington was a periodic timer, not a significance detector. This matters for reading the measured fields: temperature 0.00 across all three entries is not a claim about January. It is the reading of an instrument that only measures amplitude through the text channel, and the text channel was dark. The gauge reads zero because it is disconnected, not because the system was quiet.

The single point of failure is the timestamp. Everything this reading can do — interval, cadence, duty cycle, the inference of a periodic controller — rests on three integers. There are no captions, no cross-references, no written entry anywhere in the month that mentions a photograph or corroborates a date. Modality redundancy is zero: one channel, one type, one author, and nothing standing between these thirty-one days and total unrecoverability except file metadata. Detach the images from their dates and Lexington in January 2024 goes blank, because no second system holds a copy of the same information in a different form. That vulnerability is a direct consequence of capture running years ahead of the indexing layer built to consume it. Autonomy Realms is downstream infrastructure retrofitted onto a substrate laid before it existed — which is the only reason there is anything to retrofit onto, and also the reason the substrate is this thin.

What the system demonstrably optimizes for is series continuity, not information per entry. Under conditions of near-zero documentation demand, with every reason to let the record lapse for a month and resume when something happened, the thing that still got resourced was the unbroken sequence — three touches at minimum cost, enough to keep the clock running and no more. That is the objective function revealed by allocation: the archive's value is treated as a function of its uninterruptedness rather than its density, and a month that contributes almost no content still contributes its interval. The temporal spine is the deliverable. January 2024 delivered it at the cheapest price the system could pay.