Chapter 18: Cass's Calculation

Cass was alone in the operations center when we returned.

The staff members had been reassigned to facility monitoring posts during the stabilization team's assessment sweep. Veren's team was in the eastern section completing their containment perimeter configuration. The operations center itself was quiet for the first time since the full emergency protocol alarm had activated, the terminals running their automated monitoring cycles, the communication units silent, the central display showing the facility's boundary status in the clean green and amber of a system that had moved from crisis to managed recovery.

Cass was at her desk.

Not at the central terminal. At her desk, which was a distinction I had not seen before in the time I had been interacting with her. The central terminal was where Cass ran the facility. The desk was where Cass existed as a person who ran the facility. The difference was small and it was visible to me only because I had been reading her behavioral data long enough to understand what the small differences meant.

She was looking at a document.

She looked up when we entered and her expression shifted into the operational register she maintained in every interaction I had observed. But it shifted from something else first and the something else was the expression I had seen on Scratch's face when he thought about my father. The expression of a person sitting inside a long time.

I sat down across from her.

Ryn took the entrance.

You went to the access corridor, Cass said.

Yes, I said.

The contact window.

Yes.

She looked at me with the specific assessment she applied to everything I told her, the one that was simultaneously evaluating the content of the information and the operational implications of the information and the person delivering the information as all three simultaneously.

What happened, she said.

I told her.

Not the full account. Not the immersion quality of the experience or the specific architecture of the choice the evaluation had presented or the answer I had given. The operational summary. The contact had occurred. The Chief Analyst threshold had been reached and confirmed. The evaluation had been completed. What the completion meant for the tribunal case and for what came after the tribunal case.

She listened without interrupting.

When I finished she was quiet for a long moment.

The tribunal case needs to include the contact evidence alongside the corruption evidence, she said. Not as a separate submission. As an integrated component that makes the corruption evidence incomprehensible without it.

Yes, I said.

That requires authenticating the contact evidence in a format the tribunal can receive, she said. The System notifications you have received are personal interface data. They are not externally verifiable through standard documentation channels. She paused. The Bureau will argue they are fabricated. That an Analyst class hunter with a demonstrated capacity for data manipulation constructed a narrative around System notifications that cannot be independently verified.

I know, I said.

She looked at me.

I have something that addresses part of that problem, she said. She turned the document she had been looking at when we entered and pushed it across the desk toward me.

I looked at it.

It was a System generated facility report. Automatically produced by Vault 9's monitoring infrastructure during the boundary events of the past twenty-four hours. The report contained the standard boundary status data, the emergence classifications, the protocol activations and the power restoration record.

And at the bottom of the report, in the System generated data fields that no human hand had touched, was a classification entry that the automated monitoring system had logged without anyone directing it to.

BOUNDARY EVENT CLASSIFICATION: COMMUNICATION. ANALYST CLASS CONTACT PROTOCOL: INITIATED. CONTACT RECEPTION: CONFIRMED. CHIEF ANALYST THRESHOLD: REACHED.

The facility's own automated monitoring system had logged the contact.

Not because anyone had filed a report. Because the System had generated the classification automatically and the facility's monitoring infrastructure had recorded it in the standard event log the way it recorded every boundary event classification.

This was not personal interface data.

This was institutional infrastructure data generated by the same automated systems the Bureau used to authenticate every boundary event classification in every facility it operated. The same systems whose outputs were considered primary evidence in every dungeon-related legal proceeding for the past thirty years.

The Bureau had authenticated the contact themselves.

Through their own infrastructure.

Without knowing they were doing it.

I looked at the document and then at Cass.

She held my gaze with the expression of a person who had been sitting with a calculation for a long time and had just delivered its result.

When did you find this, I said.

Approximately forty minutes after the contact window opened, she said. The automated report generates every four hours during active boundary events. This report generated at the standard interval and I reviewed it as part of my standard monitoring protocol and found the classification entries at the bottom. She paused. I have been sitting here since then deciding what to do with it.

You decided to give it to me, I said.

I decided to give it to you, she confirmed. Because the alternative was filing it in the standard Bureau reporting chain where it would be reviewed by whatever Bureau official processes Vault 9 incident documentation and would either disappear into the review queue or be flagged for suppression by whoever in the Bureau's documentation management system is watching for exactly this kind of classification entry.

The same kind of monitoring that had been watching for analytical pathway findings for twenty-two years, I said.

Yes, she said. The same kind.

I looked at the document.

This needs to leave this facility with the stabilization team's equipment manifest, I said. Alongside Scratch's data and my father's papers and your witnessed account.

Cass reached across the desk and took the document back and signed the bottom of it with the specific signature I had seen on the witnessed account she had given me earlier. Not her administrative signature. Her personal signature. The one she had told me was admissible as an institutional record under the regional government oversight charter.

She pushed it back across the desk.

It is already on the manifest, she said. I added it twenty minutes ago. I was waiting for you to come back from the access corridor before I told you it existed because I needed to understand what had happened in the contact before I could assess whether the document's contents were accurate.

I looked at her.

The contact occurred, I said. The classification entries are accurate.

She nodded once. The nod of a person who had been waiting for that specific confirmation and had now received it and could move forward from it.

I picked up the document.

There is something else, she said.

I waited.

She reached into her desk drawer and produced a second document. This one was not a System generated report. It was handwritten. Her handwriting. Dense and precise in a way that suggested it had been written quickly but carefully, the kind of writing that happens when a person is working from a clear mental outline and transcribing it rather than composing it.

My personal account of the eastern face access routing decision, she said. The full account. Not the operational summary in the incident report. The complete account including the boundary status data I had access to when I made the decision and my assessment of the Bureau team's objective based on the archive deletion I had discovered three days prior. She pushed it across the desk. Everything I knew when I made the decision and what I concluded from what I knew.

I looked at her.

This is not covered by your operational mandate, I said.

No, she said. It is not. The incident report is covered by my operational mandate. This document is a personal account that falls outside it. Which means if the Bureau reviews it they will argue it is not an admissible institutional record. She paused. However the regional government oversight charter has a provision for personal accounts from facility wardens regarding decisions made in the performance of their duties that they have independently documented as matters of personal record. The provision was written specifically to allow wardens to create accountability for decisions that fall in the gap between their operational mandate and their personal judgment.

You have been planning this for longer than today, I said.

I have been planning this since the day I pulled your arrest file and found the timestamp anomaly, she said. I did not know what form it would take. I knew that whatever I found in your file was the beginning of something that was going to require me to make decisions that my operational mandate would not cover and that I was going to need a way to document those decisions that was both honest and legally defensible.

She held my gaze.

I have been running this facility for eleven years, she said. I have made a very long series of small decisions to do the slightly less wrong thing. This is not a small decision. I want the record to reflect that I understood the difference.

I looked at the document in my hands.

The complete account of everything Cass had known and concluded and decided in the past eleven days. The archive deletion discovery. The routing decision. The eastern face access configuration. The countersignature on the evidence manifest. All of it documented in Cass's handwriting with her personal signature and the date and the specific provision of the regional government oversight charter under which it was admissible.

It was the most significant single document in the evidence package because it was the only one that connected every other piece to a human decision made with full knowledge of its implications.

Ryn spoke from the entrance.

Veren is coming, he said.

I looked up. Through the operations center window I could see Veren moving through the corridor toward us with the specific pace of someone who had something to report and was moving at the speed that the urgency of the report required.

She entered the operations center and looked at me and then at Cass and then at the documents on the desk between us.

The containment perimeter is configured, she said. The junction barrier is holding. Eastern face access corridor is clear. She paused. The Bureau emergency response team has made radio contact. They are one hour and forty minutes out. They are requesting facility access authorization from the warden.

Cass looked at me.

One hour and forty minutes.

The contact window countdown updated at the edge of my vision.

Two hours and fifty-seven minutes remaining.

The Bureau team would arrive before the contact window closed.

I looked at the documents on the desk.

I looked at Cass.

I looked at Ryn.

I looked at the boundary status display on the central terminal showing the facility's current state in green and amber and the specific entry at the bottom of the automated report that the Bureau's own infrastructure had generated and that was now sitting on Cass's desk with her personal signature at the bottom and her eleven years of careful small decisions behind it.

The Bureau emergency response team was one hour and forty minutes out.

One hour and forty minutes to complete what my father had spent nineteen years preparing.

I picked up both documents and stood up.

We need Scratch and Greiss, I said.

Ryn was already moving toward the corridor.