Chapter 20: System Notification

Veren was in the eastern section corridor when we found her.

She was standing at the junction perimeter with two of her team members and looking at something on her assessment terminal that had produced the specific quality of focused attention that field hunters develop for readings that do not match their operational expectations. She looked up when we approached and held up the terminal so I could see the display.

I read it.

Then I read it again.

The stabilization assessment had covered every boundary section in the facility following the power restoration and the lower quadrant failure event. The northern section was holding at 19% localized integrity with supplementary power support providing stabilization. The eastern section was elevated but manageable. The lower quadrant was post-failure and sealed.

The reading Veren was showing me was not from any of those sections.

It was from the western section.

The section of the boundary that ran along the facility's western wall, opposite the lower quadrant, the section that had shown no anomalous readings in any of the monitoring data I had been tracking since intake. The section that had not been part of any of the stress redistribution patterns following the lower quadrant failure. The section that had been the most stable part of the entire boundary structure throughout everything that had happened in the past twelve hours.

The western section was reading 11%.

I looked at Veren.

When did this appear, I said.

Eighteen minutes ago, she said. It was not present in the assessment sweep we ran two hours ago. The degradation from stable to 11% in eighteen minutes is not consistent with any standard boundary deterioration pattern I have seen in eleven years of stabilization work. She paused. It is consistent with an engineered failure mode that was set to activate at a specific trigger point.

The same methodology as the lower quadrant regulatory layer failure, I said.

Yes, she said. Different trigger. The lower quadrant failure was designed to activate at the longer cycle peak. Based on the degradation pattern this failure mode was designed to activate at a specific time elapsed from the lower quadrant failure event.

How long until it reaches catastrophic threshold, I said.

At current degradation rate, she said. Approximately thirty-two minutes.

Thirty-two minutes.

The western section ran along the facility's western wall.

I pulled up the facility schematics on the handheld terminal and looked at the western section's physical location relative to the facility's infrastructure.

The western section boundary ran directly adjacent to the main exit corridor.

The corridor that connected Vault 9's interior to the surface access shaft.

The only way out of the facility that did not go through the eastern face access or the east corridor.

I looked at Veren.

If the western section fails, I said.

The main exit corridor is adjacent to the failure zone, she said. A western section failure produces a breach event in the corridor itself. The main exit becomes an active emergence zone. She paused. Anyone in the main exit corridor during or after the failure event is inside a Class-S emergence without containment infrastructure.

Voss engineered two failure modes, I said.

The lower quadrant to close the contact window, Ryn said from beside me. And the western section to seal the exit.

He knew someone would be here, I said. He knew the longer cycle peak would produce a contact window and he knew an Analyst class hunter in this facility during the peak would attempt to leave with the evidence before his team could arrive. He built a contingency. If the Bureau team failed to retrieve Scratch before the contact window opened, the western section failure would seal the exit and keep everyone inside until the Bureau emergency response team arrived with the authorization to do what the black transport team could not.

Ryn was very still.

He built a trap, he said.

He built a trap, I confirmed. With two triggers. The lower quadrant to prevent the contact. The western section to prevent the exit. Both engineered into the facility's boundary architecture years in advance. Both timed to activate at specific points in the longer cycle peak sequence.

Veren was watching me process this with the expression she had been developing since I first showed her the Rift Mapping data. The expression of a specialist encountering a level of systemic premeditation that exceeded the parameters of her professional framework.

Can you stabilize the western section, I said.

She looked at her terminal.

At current degradation rate and with the equipment we have available, she said. I can slow the degradation. I cannot stop it. The regulatory layer failure in the western section is more advanced than the lower quadrant was when you sealed it during first shift. The middle band is not failing. It is already gone. The primary barrier is fully unsupported across the entire western section.

How much can you slow it, I said.

Enough to extend the window from thirty-two minutes to approximately fifty minutes, she said. Possibly fifty-five. Not beyond that without specialist equipment we do not have on site.

Fifty minutes, I said.

Fifty minutes, she confirmed.

I looked at Ryn.

He looked at me with the expression that meant he had already completed the operational calculation and was waiting for me to confirm that his calculation matched mine.

It matched.

Fifty minutes to get four people out of a Class-S containment facility through a main exit corridor that would become an active emergence zone at the end of those fifty minutes. With a Bureau emergency response team one hour out. With a regional government authorization that Cass had activated this morning but that had not yet been formally processed into an early release order.

And with the System notification that had appeared at the edge of my vision while Veren was showing me the western section reading, sitting there with the particular quality of something the System had been waiting to deliver until the exact right moment.

I read it now.

SYSTEM NOTIFICATION: VAULT 9 FACILITY ASSESSMENT COMPLETE. BOUNDARY INTEGRITY FAILURE PATTERN CLASSIFIED AS DELIBERATE SABOTAGE. EVIDENCE OF ENGINEERED FAILURE MODES DETECTED IN LOWER QUADRANT AND WESTERN SECTION. CLASSIFICATION: INSTITUTIONAL MISCONDUCT, BUREAU DIRECTOR AUTHORIZATION LEVEL. AUTOMATIC NOTIFICATION DISPATCHED TO: INTERNATIONAL DUNGEON SAFETY COMMISSION, REGIONAL GOVERNMENT OVERSIGHT OFFICE, INDEPENDENT HUNTER GUILD EMERGENCY NETWORKS. NOTIFICATION INCLUDES FULL TECHNICAL DOCUMENTATION OF ENGINEERED FAILURE MODES.

The System had classified the boundary failures as deliberate sabotage.

The System had automatically notified every external body that had received the initial emergency notification.

With full technical documentation.

Not my analysis. Not Cass's incident report. Not Scratch's data or my father's papers or Greiss's account of the front organization or any piece of evidence that the Bureau could characterize as coming from a convicted felon with a personal agenda.

The System's own classification of its own infrastructure.

The Bureau's own documentation methodology applied to the Bureau's own sabotage of a facility the Bureau operated.

I showed the notification to Ryn.

He read it.

He looked at me.

That is not something Voss can suppress, he said.

No, I said. The System notifications go directly to the external bodies. They do not pass through Bureau communication infrastructure. They do not require Bureau authentication. They are the System's own output delivered through the System's own channels.

Voss built twenty-two years of suppression infrastructure, Ryn said slowly. And the System just used that same infrastructure's documentation methodology to file an authenticated record of the sabotage directly with every body that has jurisdiction over Bureau operations.

Yes, I said.

He was quiet for a moment.

Your father knew the System would do this, he said. He knew that reaching Chief Analyst threshold and completing the contact would trigger an automatic assessment of the facility's boundary infrastructure. He built the timeline specifically so the contact would complete before the western section failure sealed the exit. Not just to receive the contact. To trigger the System assessment.

Yes, I said. I believe that is correct.

Veren had been watching our exchange with the expression of a person who was processing more information than her operational framework had been designed to contain and was handling the overflow with the professional composure that eleven years of stabilization work had built into her.

Fifty minutes, she said. I will start the stabilization procedure immediately. She looked at me. I suggest you start moving.

I looked at Scratch and Greiss who had followed us from the operations center and were standing behind Ryn with the patient stillness of two people who had spent a combined twenty-one years in this facility and had developed a profound tolerance for waiting for the next significant development.

Scratch was holding the transport packaging with the reproduced data and the evidence documents and Cass's witnessed account and the System generated facility report with the contact classification entries.

He had been holding it since Cass had handed it to him in the operations center.

Nineteen years of waiting and he was holding it with the same steady unhurried hands he brought to everything.

I looked at him.

Ready, he said.

I looked at Greiss.

He nodded once. The nod of a man who had spent two years in this facility regretting a choice he had made and was now in motion toward the consequence of choosing differently.

Ryn was already looking at the main exit corridor.

He looked back at me.

Cass, I said.

Already done, said Cass's voice from behind us.

I turned.

She was standing at the junction between the eastern section corridor and the main corridor with a document in her hand and the expression of a person who had made every calculation she needed to make and had made them all correctly and was now simply present in the moment that the calculations had been building toward.

The early release authorization, she said. Regional government channel. Countersigned by me under the facility warden's emergency operational mandate. Effective immediately. She held it out. Four names. Kael Drant. Ryn Oset. Edwan Greiss. And one more.

She looked at Scratch.

His full name, she said, is on the authorization. Not inmate designation. His name. The one that was redacted from his intake file nineteen years ago.

Scratch looked at the document.

Something moved across his face that was not any of the expressions I had catalogued in the time I had been interacting with him. Not the analytical precision. Not the patient endurance. Not the grief I had read when he talked about my father.

It was simpler than all of those.

It was relief.

Forty-eight minutes, Veren called from the eastern section corridor.

I took the authorization document from Cass and looked at it and then at her.

You are not on it, I said.

No, she said. I am not. I am the warden of this facility and my place is in this facility until the Bureau emergency response team arrives and the formal incident investigation begins. She paused. When it does I will be here with eleven years of careful documentation and the regional government oversight charter and everything I have signed and witnessed and filed in the past eleven days.

She held my gaze.

What I need from you, she said, is to make sure that when the investigation begins the people conducting it already have everything they need to conduct it correctly.

I looked at the transport packaging in Scratch's hands.

They will, I said.

She nodded once.

Then she turned and walked back toward the operations center with the specific walk of a person who has completed the most significant decision of their professional life and is now moving toward its consequences with the same precise economy they bring to everything else.

I looked at Ryn.

He looked at the main exit corridor.

Forty-seven minutes, he said.

We started moving.