The second estate¶

Ingestion produced a second estate: embeddings, chunk stores, caches, summaries, generated drafts, six months of answer histories. The register of processing activities describes the first one. The DPO’s office is the one room at the Home with a door that closes, and the consultant was shown into it on the first morning. The DPO has opinions. They are correct roughly eighty percent of the time, and the one she opened with was that the pilot had been run under the register and was therefore covered.

Records policy was written for the first estate. The retention schedule on a resident’s medical history in Bestiary, the eleven-year giving history in Covenant, the DPO’s own advice on the two files the scoring model opened, all of it attaches to documents; nothing attaches it automatically to derived artefacts. A summary of a privileged memo is a new document carrying no privilege marking. A chunk of a 2019 relationship-manager note, due for destruction under a schedule the DPO wrote herself, persists in an index that no destruction schedule mentions. Under a legal hold, the honest answer to “where does this content now live” becomes long and partly unknown.

Data protection has its own version of this. A fair amount of personal data in the Home’s estate had never been put to the test, mainly because it was unfindable, protected by what used to be called practical obscurity: the dormant grievance file from the east wing, the medical note about a draccus’s keeper in a 2011 attachment, and fifteen years of what the field workers bring back, which describes the human terrain of half the Disc in the detail of people who never consented to be in anyone’s record. Total recall ends that protection; all of it now surfaces on request. An erasure request now meets content diffused into an index and a hundred generated answers, and diffusion is not a format the rules were drafted around. The parallel estate also concentrates what the original sprawl dispersed. What used to be spread across a hundred field notebooks and three file shares is now one queryable place, a target the mess never offered. The DPO said the Home kept no such map. The consultant agreed that nobody had made one, which was not the same thing.

Capability changes expectation too, and expectation is where the lawyers live. An archive with practical boundaries supported a modest operational sentence: these systems were searched, and nothing was found. The Home has used the sentence when answering a subject access request, and when a chapter asked whether a field worker’s name appeared anywhere it should not. It worked because completeness was never on offer, and diligence was judged against what a bounded search could do. A universal reader retires the modesty. Once the system is known to be able to search everything, “nothing was found” becomes a claim about everything, and its failure sharpens. If the reader could have found it, the question of why nobody knew will not come from inside, in a calm retrospective, but from a claimant, a regulator, or a border official in a capital where the Home’s people are already suspected of being something other than welfare workers. Capability changes the standard against which diligence is judged: discovery requests widen to match the tool, audit expectations inflate to match the capability, and a system bought to reduce workload raises the bar its owner is measured against. Nothing has to fail for this cost to arrive. It is a property of being known to be able to look.

There is one question at the Home that has always been answerable in principle and never been asked, which is why a welfare charity’s travel patterns map so neatly onto somebody else’s interests. Under the old estate, asking it took a person, a quarter’s figures and an afternoon. Under the reader it takes a login and a well-phrased sentence, and the answer arrives like any other.[1]

The doubling reframes the questions that arrive later in the deployment’s life. “Where did the record go” now means which estate the record is in, and “who owns this” now means who owns the derivative estate. The later costs are rarely new problems; they are old questions asked of an estate that no longer has one answer. The DPO wrote the derivative estate into the register as a processing activity.