Chapter 87: Hearing Minus Three

The first disruption event hit at 0315 on the second night.

Not the worst moment for it—she was awake, which was better than being pulled out of sleep. The relay implant pulsed twice at 0314, giving her thirty-one seconds. She sat up, put her back against the wall, and ran through the management framework as the routing test resolved.

It lasted four minutes.

Pair fourteen—Energy Blasts and Recoil Damage—attempting a cross-pair route through pair thirteen and hitting an incompatible pathway. The interference was a sharp stutter in the integrated signal, pairs thirteen and fourteen arguing briefly about input priority, the recoil damage curse briefly spiking before the routing test found its endpoint and stabilized.

She logged it at 0319.

*Routing test one: pairs 13-14. Duration 4:07. Management required, manageable. Recoil damage spike significant but short. Pre-warning: 31 seconds. Sat down before onset—no fall.*

The second disruption event came at 1100 on day two—during the bearing group's joint legal preparation session. The relay implant pulsed twice and she interrupted what she'd been saying to Osei, sat down without explaining why, and held the pairs through twenty-three seconds of pairs six and seven attempting a routing exchange that went badly before correcting.

Osei waited without asking questions.

When it resolved, Kira said: "Continue."

Osei continued.

"The precursor monitoring," Osei said afterward, when the session had ended and the room had cleared. "The relay pulse."

"Yes," Kira said.

"The committee is going to see the Cannot Lie curse as an asset," Osei said. "But they may also see the disruption events as risk. Depending on how they characterize them."

"The disruption events are part of the stabilization phase of the third alignment," Kira said. "They're temporary, limited in duration, and I have thirty seconds of warning." She paused. "They're not dissolution risk."

"Can you say that in the testimony window," Osei said.

"Yes," Kira said. "Because it's accurate."

Osei made a note.

"Good," she said.

---

The third disruption came and went on day two at 2230—brief, five minutes, while she was eating. She set down the fork, worked through it, picked the fork back up.

After that, the cross-pair routing ran quiet.

By day three morning, the integrated signal had stopped producing routing conflicts. The eighteen pairs were running in a configuration that had sorted itself into something stable—pairs exchanging data in a coherent sequence, the output of each pair feeding into the next in a loop that the Architect had apparently designed to be self-organizing once initiated.

Vedran confirmed it at 0900 on day three by reading her frequency signature from across the room.

"Stable," he said. "The routing is set." He paused. "I've never seen stabilization complete in two and a half days before."

"Is that good," Marcus asked.

"It suggests the specification architecture is well-developed," Vedran said. "The routing configuration found stable pathways faster than the other specifications I've observed. Which means—" He paused. "The pairs were ready. The management work Kira has been doing for twenty-four years may have pre-organized the pairing relationships in ways that made the routing easier to establish."

"The management framework was preparation," Cross said.

"Inadvertent preparation," Kira said.

"The most useful kind," Vedran said. "The kind you can't consciously perform."

Cross had the updated integration numbers by 1000.

"21.4%," she said. "The stabilization completion advanced the percentage again. The routing configuration running stably is a different state from the routing configuration being established." She paused. "The Architect's measurement—what the 21.4% represents—I'm now more confident it measures the fraction of the cross-pair resonance architecture that's running stably. Not how many pairs are at third stage. How much of the final resonance design is active and stable."

"And 21.4% is how much," Kira said.

"Approximately a fifth," Cross said. "Which means—the endpoint is much further than I originally estimated, but the trajectory is also faster than I originally estimated. The integration percentage is advancing through alignment events and stabilization phases rather than through gradual pair-by-pair work." She paused. "The timeline to the endpoint is—I need more data. But it's not centuries. It may not even be decades."

Kira looked at the window.

A fifth of the way toward whatever the specification was building her toward. Whatever the Architect's specific question was for eighteen pairs of blessings and curses and the particular human who carried them.

"Three days until the hearing," she said.

"Three days," Marcus said.

---

The legal team's day-five documentary filing deadline fell on day three of the hearing countdown.

Everything that could be submitted to the Council's review committee had to be submitted by end of day. Cross's forty-seven-page dissolution documentation with the three-page executive brief. Dorian's submission, already filed, now supplemented with Cross's T7-F framework annotation that made the mechanism legible for non-technical readers. The operational record documentation—fourteen months of Guild field records establishing the management capacity argument. The mole pipeline counter-filing, establishing the retaliatory-filing characterization.

Vedran's observation record.

She'd made the decision at 0700 on day three, after Vedran had confirmed the stabilization was complete.

"Your documentation," she'd said to him. "Forty-one years of specification observation records. Protocol frequency data from seventeen dungeon sites over four decades. The three completed specification case studies."

He'd looked at her.

"You want to file it," he'd said.

"It's the most comprehensive historical record of Protocol specification development that exists," she'd said. "The committee is weighing one specification—mine—against a dissolution risk argument and a Curse Collector documentation file. Your observation record is evidence that Protocol specifications develop toward specific endpoints that aren't dissolution. That they've been developing for decades. That the Architect's design is real and has produced results."

"Filing my documentation tells the committee I exist," he'd said. "And that I've been observing Guild operations for forty-one years without anyone knowing."

"Yes," she'd said.

He'd been quiet for a moment.

"The Forgettability curse," he'd said. "The formal record will exist. The committee members will read it. But whether they'll retain the reading—" He'd paused. "I've had limited experience with institutional documentation. The curse usually degrades the documentation's traceable connection to me within weeks."

"The documentation is in the Council's permanent record regardless," she'd said. "Whether they remember you specifically or not."

He'd looked at her.

"Yes," he'd said. "Both at once."

She'd taken a second to place that. Then: "You've been around Marcus too long already."

"He explains things clearly," Vedran had said.

Osei had taken the observation record at 1400 and spent forty minutes reviewing it with the specific expression of someone who understood they were looking at something that changed the shape of the legal argument.

"The three completed specifications," Osei said. "All living, post-completion, integrated into normal functioning society. All observable in Vedran's records." She paused. "If I can file this with an expert attestation—Vedran as the observing bearer, Cross as the technical validator—"

"Can you make it land before end of day," Kira said.

"Yes," Osei said.

It filed at 1647.

Thirteen minutes to spare.

---

The intelligence on Valerian's hearing preparation arrived at 1700.

It came from Harrow—Harrow's network inside the Cult's public advocacy structure, a different channel than the Abara pipeline. A slower channel, less specific, but still running.

"Valerian's team has confirmed three witnesses for the testimony window," Harrow said, on the relay. "The first two are as expected—a structural engineer who will testify about the Ironveil secondary effects, and a Guild monitoring analyst who will present the energy reading data from three dungeon sites." She paused. "The third witness is—unexpected."

Kira looked at Marcus. He was very still.

"Tell me," Kira said.

"A Protocol bearer," Harrow said. "Currently unidentified in my network's intelligence. Not a Guild bearer—not someone in the formal bearing registry. Private individual, four blessings, presenting voluntarily to testify about the dissolution risk argument from a bearer's perspective."

"A bearer testifying for Valerian," Kira said.

"A bearer testifying about dissolution risk from personal experience," Harrow said. "My network doesn't have the specifics of their testimony. But a Protocol bearer appearing in the hearing to argue that dissolution risk is real and meaningful—from inside the bearing experience—that's a different argument than the structural engineer and the monitoring analyst."

"It undercuts the 'Protocol bearers themselves don't believe the risk is real' argument," Marcus said. He was still keeping his voice level. She could tell from the deliberateness of it.

"Yes," Harrow said. "The legal team needs to know tonight."

"They'll know in the next twenty minutes," Kira said.

She ended the relay call.

She looked at Marcus.

"A bearer who's going to testify that dissolution risk is real," she said. "From personal experience."

"We don't know their experience," Marcus said. "We don't know if they're describing their own situation accurately, or if Valerian's team has prepped them to characterize an ordinary cascade event as a dissolution risk event."

"The Cannot Lie curse doesn't apply to them," she said.

"No," he said.

She was quiet.

"The operational record," she said. "Our entire management capacity argument is built on demonstrated outcomes over twenty-four years. If a bearer testifies that their operational experience included genuine dissolution risk—"

"It doesn't contradict your operational record," Marcus said. "Different bearers, different Protocols, different management approaches. Their experience doesn't invalidate yours."

"It gives the committee a bearer voice saying the risk is real," she said. "As opposed to a bearer voice saying the risk is manageable."

He didn't argue with that.

"Who is it," she said.

"Harrow doesn't know," he said.

She looked at the window.

A bearer she didn't know, testifying for Valerian. Not for pay—bearers didn't do things for pay that violated their Protocol architecture. For belief. This was someone who genuinely believed what they were going to say.

"Osei tonight," she said. "Full revision of the testimony strategy."

"Yes," he said.

"And I need Vedran to listen to the intelligence briefing," she said. "If the mystery bearer is a specification they've observed—if their frequency signature is in Vedran's records—"

"Forty-one years of observation data," Marcus said. "The probability that he's encountered this bearer in four decades of protocol site monitoring."

"It's not zero," she said.

"No," he said. "Not zero."

She stood.

The hearing was in three days. They'd known about two of Valerian's three witnesses. The third was a bearer whose dissolution experience—real or coached—was designed to do something her twenty-four-year operational record couldn't easily counter.

Both at once. The 21.4% integration and the cross-pair resonance running stable, and the testimony window with an unknown bearer on the other side.

"Brief Vedran first," she said. "Then Osei."

"Affirmative," he said.

[INTEGRATION: 21.4% — CROSS-PAIR RESONANCE: STABLE — STABILIZATION: COMPLETE DAY 2.5 — VEDRAN OBSERVATION RECORD: FILED — VALERIAN THIRD WITNESS: BEARER, UNKNOWN — HEARING: T-MINUS 3 DAYS]