Veyla came to the guildhall on Day 129 looking like someone who'd spent the night arguing and lost.
Her silver skin had the dull tone that Dimensional people got when their biological stress responses depleted the pigmentation's energy supply. She sat at the operations table with her hands flat on the surface and her diagnostic probe clipped to her belt instead of held against her chest, a medic's choice that said the next conversation wasn't medical.
"The advisory council's response," she said.
Ark and Dex were at the table. Sera was in the infirmary doorway, close enough to hear but positioned at the threshold in the way she positioned herself when she was monitoring a situation rather than participating in it.
"The council is suspending advisory support for coalition operations in Dimensional space," Veyla said. "Effective immediately. No Tessara consultation, no remote monitoring, no advisory team deployment until a formal review of the coalition's operational protocols for Dimensional territory is completed."
The words landed on the operations table the way bureaucratic consequences landed: heavy, precise, designed to communicate institutional displeasure through institutional mechanisms.
"The review timeline?" Dex asked.
"Fourteen days minimum. The council convenes every six days. The review requires two sessions plus a response period." Veyla's hands stayed flat on the table. "I argued that the expedition's results justify the operational decision. The Wellspring. The Choir. The Song flow restoration sequence. The council acknowledged the results. They suspended the support anyway."
"Because the results don't change the process failure," Dex said.
"Because the communication loss in the deep zones meant Tessara's advisory team was unable to monitor coalition actions in Dimensional space for nine hours. The council's position is that Dimensional space is Dimensional jurisdiction. Operations in that space require Dimensional oversight. The coalition conducted a major operation without it."
"We lost communication. We didn't refuse it."
"The distinction matters less than the outcome." Veyla looked at Ark. "The council has members who've been waiting for an opportunity to restrict the coalition's access. Councilor Teras argued during the last integration review that human organizations shouldn't have unsupervised access to Dimensional infrastructure. The communication breakdown gave her the votes."
"Councilor Teras has been against the coalition since the integration began," Ark said.
"Councilor Teras has been against unsupervised access. Her position isn't unreasonable. It's inconvenient." Veyla's hands lifted from the table, then went back down. The gesture of someone choosing words carefully. "The expedition was necessary. I believe that. The communication failure was predictable and we proceeded anyway. I told Dex that the day before. The record shows that I recommended communication infrastructure upgrades before the expedition and the recommendation wasn't implemented due to timeline constraints."
"You're on record," Dex said.
"I'm on record. Which is why the council didn't suspend my personal advisory role. I can still consult with the coalition independently. But the institutional support, the advisory team, the remote monitoring, the Tessara council's backing for joint operations in Dimensional space, is paused."
The operational impact was immediate and specific. Without Tessara's advisory support, the gap node repair sequence for the Wellspring flow restoration couldn't proceed. The node repairs required Dimensional engineering expertise. Veyla had some. The full advisory team had more. Working alone, Veyla could guide the repairs but at reduced capacity and with personal risk if the council viewed her independent consultation as circumventing the suspension.
"Can you still help with the node repairs?" Ark asked.
"Personally, yes. Officially, the council's suspension covers institutional resources. My personal expertise isn't institutional." A pause. "But if the council decides that my personal consulting constitutes an end run around the suspension, they can revoke my independent advisory status."
"We need you for the node repairs."
"I know. And I'll help. But we should be clear about what we're spending." Veyla sat back. The dull silver of her skin hadn't improved during the conversation. "Tessara's trust is a resource. The communication breakdown cost us some of it. Using my personal advisory to work around the suspension costs more. At some point the account runs out."
Dex wrote. The pen moved through the operational assessment with the compression that meant the Warlord was cataloguing multiple consequences simultaneously.
"Fourteen days," he said. "The review period. We need the gap node repairs started before then. The Wellspring flow restoration is the corridor's long-term solution."
"Start the repairs. Use my expertise. Accept the political cost." Veyla stood. "I'll brief you on the node repair requirements this afternoon. The first node is in the gap section between Zone 8 and Zone 9, at the point where the Void scarring is heaviest."
She went to the door. Stopped. Turned back.
"Ark. The council's anger is real. Councilor Teras's position is gaining support. The next time the coalition conducts a major operation in Dimensional space without adequate Tessara involvement, the suspension won't be temporary." Her silver eyes held his. "Fix the communication infrastructure. Whatever it costs. Fix it before the next operation."
She left. The guildhall's front door closed behind her.
---
The Corridor Gate activation took twenty minutes at the rift aperture on Day 129 afternoon.
Ark stood on the subway platform with the guardian function at full output and the rift's dimensional boundary within the warden class's operational range. The bond at 80%. The architecture stability at the threshold. The System's activation parameters met.
He opened the Corridor Gate.
The guardian function connected to the rift boundary in a way that the passive monitoring had never achieved. The monitoring equipment watched the rift from outside. The Corridor Gate operated from inside the dimensional fabric itself, the guardian architecture integrating with the rift's aperture structure the way a hand fit inside a glove.
The rift was his.
Not ownership. Control. He could feel the aperture's dimensions, its structural integrity, the flow of dimensional energy through its boundary. He could restrict the opening, narrow it, seal specific sections. He could reinforce the membrane at weak points. He could detect transit through the aperture and, with sufficient concentration, deny it.
The active management was different from passive decay in the way that steering a car was different from watching it roll. The rift's 38% integrity was the same number it had been yesterday. But now the 38% was managed rather than observed.
Except the 38% was lying.
The Corridor Gate's integration with the rift's dimensional fabric showed Ark something the passive monitoring hadn't detected. Micro-fractures. Hundreds of them. Tiny breaks in the dimensional fabric around the aperture, each one individually harmless, collectively dangerous. The integrity measurement counted the major structural components. The micro-fractures were below the measurement's resolution threshold.
The rift at 38% integrity was like a wall at 38% structural capacity with hairline cracks running through the mortar. The number said the wall was standing. The cracks said the wall was one bad day from collapsing in pieces rather than falling as a unit.
"The rift is more fragile than the integrity number shows," Ark told Dex at the evening briefing. "The Corridor Gate detected micro-fractures throughout the aperture boundary. The 38% number is a measurement of major structural integrity. The minor structural damage isn't captured."
"Effective integrity," Dex said.
"Lower than 38%. How much lower depends on the micro-fracture propagation rate under stress."
Dex wrote the number with a question mark. The pen paused. "Does the Corridor Gate help with the micro-fractures?"
"Active management can prevent propagation. I can reinforce the sections where the fractures are densest. But repairing them requires the Wellspring's full Song output through the restored flow path. The Corridor Gate manages the rift. The Wellspring heals it."
"So the gap node repairs are even more urgent than we thought."
"Yes."
The operational list that had been growing since the expedition was now a document that Dex had given its own section in the clipboard. Multiple threads, converging timeline, insufficient resources for all of them simultaneously. The Warlord's pen moved through prioritization the way it always did: triage, sequence, address what's closest.
---
Day 130. The strike planning began.
Kroft was at the guildhall by 0700 with the Silver Chain intelligence report on the Prometheus facility. The report was thin, the reduced-capacity intelligence pipeline delivering what it could: location, approximate size, operational indicators. An abandoned industrial complex forty kilometers outside Korinth. Former manufacturing site. Power consumption patterns consistent with data processing equipment. Vehicle traffic at irregular intervals. No class-energy signatures detected from external monitoring.
"The probe's transmission destination," Kroft said. She laid the site photographs on the operations table. Aerial shots from the Silver Chain's reconnaissance. "The data the probe collected in Zones 1 through 3 was transmitted here. If the data is still on-site, we can recover or destroy it."
"If," Dex said.
"Prometheus isn't stupid. They'll have distributed the data to secondary locations. But the primary processing facility is where the analysis happens. The raw probe data needs to be decoded, analyzed, and translated into actionable intelligence. That takes time and specialized equipment. The facility is where the equipment is."
"How long before they complete the analysis?" Ark asked.
"The probe's data format is dimensional frequency encoding. Prometheus has been developing the technology, but their decoding capacity is limited. The Silver Chain's assessment: five to seven days from transmission to full analysis."
Day 128 had been the transmission. Day 130 was today. Three days of Prometheus working on the data. Two to four days before they could use it.
"Day 132," Dex said. "Strike on Day 132. Two days of planning. Prometheus is at day four of analysis. We hit the facility before they complete the decode."
"Bureau-coalition joint operation," Kroft said. "The oversight protocol applies. The Bureau leads the approach, establishes the perimeter, and handles any civilian interface. The coalition provides the class-energy operational capability inside the facility." She looked at Dex. "The protocol. To the letter."
"To the letter," Dex confirmed.
"I want written operational plans by Day 131 morning. Personnel assignments. Rules of engagement. Contingency protocols for three scenarios: facility occupied and defended, facility occupied and undefended, facility evacuated with equipment left behind." Kroft picked up the photographs. "No cowboys. No improvisation. This is a joint operation with institutional oversight and I will shut it down if the protocols aren't followed."
"Understood," Ark said.
Kroft paused at the door. Her face had lost the institutional authority she wore during operational planning. What was underneath was personal.
"The Petrov incident happened because we didn't formalize the protocols," she said. "The probe happened because our security protocols didn't account for non-class threats. We keep making the same mistake: building systems that cover what we expect and getting surprised by what we don't." She held the photographs. "This strike covers what we expect. Tell me what we're not expecting."
"I don't know yet," Ark said.
"Find out before Day 132."
She left.
Dex was already writing the operational plan. The pen moving through phases, personnel, contingencies. The Warlord's expertise given a task that matched it perfectly, the institutional violence of a well-planned operation taking shape on the clipboard's pages.
Ark sat with the question Kroft had asked. What weren't they expecting? The probe's dimensional frequency drive. The technology that Prometheus had been developing in parallel with their organizational operations. The probe's propulsion system used dimensional frequency manipulation that the Analyst had flagged as architecturally similar to something else.
The Void's approach vector.
The Wellspring's memories had shown the Void entering the network from a specific direction, from the space between the spaces. The corruption had traveled through the dimensional fabric using a frequency that interacted with the network's architecture. Prometheus's dimensional technology wasn't the same frequency. But it was in the same family. The same branch of dimensional engineering, applied differently.
Prometheus was working with dimensional technology that shared a lineage with the Void's method of corrupting the network. Not because they were allies with the Void. Because they were studying the same thing. Dimensional frequency manipulation. The ability to interact with the fabric between dimensions.
The Void did it through corruption. Prometheus was trying to do it through technology.
The same tree. Different branches.
"The probe's frequency drive," Ark said. "Pel's analysis. Has she finished the deeper zone scan data?"
"She's been working on it since last night," Dex said without looking up from the operational plan. "The local storage data. The zones the probe scanned that weren't transmitted."
Ark found Pel in her workshop at the back of the guildhall. The Artificer was surrounded by the probe's disassembled components, the data core connected to a decoding rig she'd built from coalition monitoring equipment and what looked like parts from a coffee maker. Pel's engineering drew from whatever materials were available.
"The local storage," Ark said.
Pel didn't look up. Her hands moved through the decoding interface. "The probe scanned Zones 4 through 6 before we intercepted it in Zone 4. The scan data for Zones 4 and 6 is unremarkable. Corridor architecture. Song frequency levels. Guardian function residue from your barrier maintenance."
"And Zone 5?"
Pel's hands stopped.
"Zone 5 has something the probe was specifically looking for." She pulled up a display on the decoding rig. A frequency map of Zone 5's dimensional fabric, rendered in the probe's scanning format. The corridor's normal architecture showed as green. The Song's frequency showed as blue. And in one section of Zone 5, near the zone's eastern wall, the display showed a red marker.
"A secondary rift," Pel said. "Small. Approximately two meters in diameter. Concealed within the corridor's dimensional fabric using a frequency masking technique that the coalition's monitoring equipment isn't calibrated to detect." She looked at Ark. "The probe found it because the probe was looking for it. The scanning parameters include a search function specifically designed to locate this frequency signature."
"Prometheus put it there."
"The masking technique matches the probe's own frequency drive architecture. Same engineering family. The secondary rift and the probe were built by the same people." Pel turned the display so Ark could see the full scan. "The rift is small enough to pass individual personnel or small equipment. Not a team. Not a vehicle. But a person with the right equipment could enter the corridor through this aperture without using the primary rift at Zone 1."
"They've had access to the corridor."
"For weeks, based on the frequency decay analysis. The secondary rift was established approximately three to four weeks ago."
Three to four weeks. Before the succession transfer. Before the Day 128 expedition. While the coalition was running barrier operations and corridor maintenance and planning the deep-zone investigation, Prometheus had a door into the corridor that nobody knew about.
The probe hadn't just been a data collection mission. It had been a quality check. Prometheus sending a scanner through the primary rift to verify that their secondary access point was still operational and undetected.
And now the coalition knew about it.
Ark looked at the red marker on Zone 5's frequency map. A two-meter hole in the corridor that Prometheus had made with dimensional technology that shared a lineage with the Void's corruption methods.
The strike was in two days. The Prometheus facility was forty kilometers away. And the corridor, the space that Ark was responsible for maintaining and protecting as its guardian, had been compromised for a month.
"Don't tell anyone else yet," he said. "Dex first. Then we decide how this changes the strike plan."
Pel looked at him. At the display. At the red marker that meant the corridor hadn't been secure since before any of them knew there was a reason to worry.
"It changes everything," she said.
