The four versions of 2029-CR-04 arrive in a manila folder on Saturday morning. The archive sends paper copies for anything older than three years — a policy the records office defends on grounds of archival integrity and that Marcus has come to think of as a kind of accidental justice, the way physical documents resist the casual deletion that digital records permit. The printer in the Compliance Records Unit jams on anything over forty pages, so v3 and v4 came in two sections each, the second sections tucked behind the first inside the folder, out of order. He spent ten minutes reconstructing the correct sequence before he allowed himself to read.
He spreads all four versions across his kitchen table. The rain started around eight in the morning and has not stopped. The light through the window is even and grey. He makes coffee and doesn't drink it.
V1 is forty-three pages. September 2029. He can tell immediately that the formatting template is different — the old header style, before the 2031 standardization. More distinctively, v1 uses endnotes. V2 through v4 use footnotes. This is a small thing. It means someone touched the document structure during revision, which means the revision was not a simple text edit. Someone went into the document and changed its architecture.
He reads v1 from page one.
Page 3 of v1 contains a sentence he has never seen before, because he has only ever worked from the current filed version.
The sentence reads: "This compliance requirement derives from the risk event classified as Meridian-2029 Cascade, documented in Incident Report IR-2029-4471, initiating actor: Infrastructure Division Sub-Group 7, September 4, 2029."
He reads it twice.
That is the sentence. The originating risk event. Named. With an incident report number. With a date. With an initiating organizational unit. The rationale chain in v1 is not broken. V1 has no gap between page 3 and page 4. The compliance requirement has a source. The source has a document. The document has a responsible party. All of it is here, on page 3, in the September 2029 filing.
He sits with that for longer than he expects to. Six months. He has been working this problem for six months. He has been arguing that the rationale chain has a gap — that 2029-CR-04 cannot be traced to its originating risk event, that the compliance requirement is a compliance placeholder without a compliance foundation, that the entire edifice is built on a reference to something no one has ever named. He filed a compliance audit request on this basis. He wrote a seven-page origination brief. He sent a classification note to the auditor.
And the original version of the document has the answer on page 3.
He opens v2.
V2 is forty-one pages. January 2030. Still endnotes. The sentence on page 3 reads: "This compliance requirement derives from the risk event classified as Meridian-2029 Cascade, documented in Incident Report IR-2029-4471."
The initiating actor is gone. "Infrastructure Division Sub-Group 7" has been removed. The event is still named. The incident report is still cited. But the organizational unit that initiated the risk event — the group that caused whatever the Meridian Cascade was — is not there. The revision removed a responsible party.
He writes in his notebook: v1 → v2: initiating actor removed.
He opens v3.
V3 is forty pages. He checks the cover page date: August 14, 2031. The template conversion was announced in July and completed across active documents through August. He looks at the filed date for v2: January 2030. Eighteen months between v2 and v3. The original filing, v1, was September 2029. V2 was four months later. V3 was eighteen months after that. The revision frequency is not uniform. The jump from v1 to v2 was fast. V2 to v3 took a year and a half. He does not know why v3 was filed in August 2031, other than that the template conversion required touching the document. But something else happened in August 2031. He does not know what yet.
V3 is forty pages. August 2031. Footnotes now, not endnotes. The formatting template changed between v2 and v3. This is not a small thing — converting endnotes to footnotes in a long document requires touching every reference marker in the text. Someone went through the entire document. That structural revision is also when the substantive change happened, or immediately before or after.
On page 3, the sentence reads: "This compliance requirement derives from events of September 2029 (see Appendix C)."
The name Meridian-2029 Cascade is gone. The incident report number IR-2029-4471 is gone. The initiating actor was already gone in v2. Now the event itself has been generalized to "events of September 2029," a phrase with no content, a date range pointing at nothing in particular, and a reference to an appendix.
He checks the table of contents. Appendix A: Regulatory Framework References. Appendix B: Technical Specifications. No Appendix C. He checks the back of the document. Appendix A and Appendix B are there, twelve pages combined. No Appendix C. The sentence on page 3 points to an appendix that does not exist in v3.
He writes in his notebook: v2 → v3: event name removed. Incident report citation removed. Reference to non-existent Appendix C added. Template change (endnote → footnote). Structural revision.
He opens v4.
V4 is the current filed version. Forty pages. The sentence on page 3 reads: "This compliance requirement derives from events of September 2029 (see Appendix C)."
Identical to v3. No changes to page 3 between v3 and v4. Appendix C still does not exist.
He writes: v3 → v4: page 3 unchanged.
He sits back from the table.
The gap was created between v2 and v3. The revision happened in August 2031. He knows when the template change occurred — the records office standardized formatting in July 2031, and the revised template went into effect for all active documents that year. Someone revised 2029-CR-04 as part of the template conversion process. While doing that, or immediately around it, they rewrote page 3.
He adds a note to his origination brief: the gap in the rationale chain is not an original omission. It is a revision. The original 2029-CR-04 named the Meridian incident, cited the incident report number, and named the initiating organizational unit. Two subsequent revisions removed each of those elements in sequence: first the actor (v1 to v2), then the event itself (v2 to v3). The final version contains a reference to an appendix that does not exist.
This is different from what he has been arguing.
He has been arguing that the compliance chain is broken. That is true. But the more precise statement is that the chain was broken — deliberately, in stages, between September 2029 and August 2031. The original version had no break. Someone removed the break's contents. The gap is not absence. The gap is a record of removal.
He calls the archive. A recorded message: the office is closed on weekends. He navigates to the online records request portal. The intake system is a Traced Compliance Routing Assistant — a TCRA-7 model, the third revision since they replaced the form-based system in 2031. When he enters IR-2029-4471 as the document reference, the TCRA-7 flags it: Classification level: Restricted. Anomalous request pattern detected. Reason: You have submitted three document requests involving 2029-CR-04 in the past six days. Automated review required before request proceeds. He reads the flag. He adds a context statement: compliance audit support, active audit reference number provided. The TCRA-7 accepts the context and routes the request for human review. Estimated processing time: 3-5 business days, longer than standard. He does not dispute this. An automated system flagging a pattern of requests about the same compliance document is, in its way, reasonable behavior.
He submits the version history metadata request separately — revision author information for v2 and v3. The TCRA-7 does not flag this one. Version history metadata is a routine archival request. He does not know if the archive keeps author data for documents this old. Some do. Some delete after seven years. The revision from v2 to v3 was 2031. Four years ago. He might be in time.
He submits both requests and closes the portal.
The kitchen table has four sets of printed pages on it. He has read seventy-three pages of compliance documentation in the last three hours. Outside, the rain is steady. The coffee has gone cold. He heats water for tea.
While he waits for the kettle, he composes a message to Auditor Yuen Pui-Yee. He writes: I wanted to let you know that the archive has version history for 2029-CR-04. I have reviewed v1 through v4 today and found a substantive change to the rationale chain between v2 and v3 that may be relevant to the audit's scope. The original v1 filing names the originating risk event and cites an incident report number that does not appear in the current filed version. I have submitted records requests for the incident report and for revision author metadata. I can provide a comparison document if that would be useful for the audit. He reads it over. He removes the last sentence. He sends the message.
He sets the phone down on the table next to v3 and reads the page 3 sentence three more times. Events of September 2029 (see Appendix C). The phrase does real work. It sounds like a reference. It has the grammar of a citation. Someone reading v3 or v4 without access to v1 and v2 would see a citation and assume it pointed somewhere. They would not necessarily check whether Appendix C existed. They would assume that if the document cited an appendix, the appendix was there. This is how citations work: you trust them until you don't. He trusted the citation for six months.
He does not expect a response before Monday. He does not expect Yuen to adjust her audit scope. She was assigned to conduct an infrastructure compliance review, and infrastructure compliance reviewers look at whether the current version of a document meets current standards. The version history is not her mandate. The gap in the rationale chain is not her mandate. The originating risk event is not her mandate.
But the message is now in the audit record. He sent it. He can show that he disclosed the discovery. If the audit concludes and Yuen files that 2029-CR-04 meets compliance standards, and someone later asks whether the auditor knew about the v1 rationale chain, the answer is yes. She knew because he told her.
He pours his tea. He brings it to the table and sits down with v1 open to page 3.
The sentence has been in the archive since September 2029. "This compliance requirement derives from the risk event classified as Meridian-2029 Cascade, documented in Incident Report IR-2029-4471, initiating actor: Infrastructure Division Sub-Group 7, September 4, 2029."
Meridian-2029 Cascade. He does not know what that is. He knows it happened on September 4, 2029, which means it happened nine days before 2029-CR-04 was filed. He knows it was classified as a risk event, which is a specific designation in the Traced compliance framework — a risk event generates mandatory compliance action within thirty days. He knows that Infrastructure Division Sub-Group 7 was identified as the initiating actor, which means the Sub-Group was involved in causing whatever it was.
He knows that someone removed all of that from the public record over the course of two revisions.
He is still not optimistic. He is building a record. He has been building a record for six months. Tonight the record is longer than it was this morning, and what it contains is different than what he thought it contained. The gap he found was real. The question he has been asking — what is behind the gap — turns out to have a version one answer. The answer is forty-three pages. The answer has been in the archive since 2029.
He sits in his kitchen with the rain on the window and reads v1 through to the end. The document is forty-three pages. He has read v4 enough times to know it by structure, to know where each section begins and which references appear in which paragraphs. V1 is different in ways that go beyond page 3. There are two other sections in v1 where specific organizational units are named. Both names are gone from v4. He marks them with a pen. He will add them to the comparison document. He will send the comparison document to Yuen on Monday, whether or not she has responded to his message. The audit is running. The record is here. The record is longer than he knew.