Abara accessed at 0340.
Not three days. One day. The monitoring flag triggered on Marcus's communicator at 0342 and he was in Kira's room at 0344, which was the fastest she'd seen him move in a non-physical-threat situation.
"He's in," Marcus said.
She was already at her secondary display. The monitoring system Ren had set up logged access events in real time — she could see the terminal cluster, the Level 4 clearance authentication, the file pull sequence.
Kira Vale — Protocol Documentation.
Binding Equation — Cross Research Files.
T7-D Integrated Pair Supplemental — Cross, dated two days ago.
"He's pulling it," Marcus said.
"Yes," she said.
She watched the file access log. The pull took forty seconds — Cross's twelve-page document transferring to wherever Abara's transmission system went. The terminal session lasted another three minutes: he read two other files, standard content that had been in his regular access rotation for fourteen months.
Then he logged off.
"The Valerian statement," Kira said. "He read it."
"Got ahead of his schedule by two days," Marcus said. "He wanted to see if there was new data to transmit alongside the escalation." He paused. "The false document went with it. Whatever he transmits to his Cult contact—"
"Goes with the false integration-depth markers," she said. "Yes." She looked at the access log. "He pulled the supplemental before anything else in today's session. He went directly to T7-D." She paused. "He knew Cross had new work on that cluster."
"His previous access had Cross's preliminary T7-D notes from two days before the alignment," Marcus said. "He knew the cluster was active." He looked at the log. "But he also knew the T7-D analysis had become more urgent — if Abara is reading the Cult's internal communications as well as feeding them—"
"He'd have seen Valerian's statement before it was published," Kira said.
"And he'd have understood why the T7-D integrated pair data was immediately relevant," Marcus said.
She looked at the log.
Something about the sequence bothered her. The T7-D supplemental first, then the standard rotation files. Most of Abara's previous sessions had started with the standard rotation and pulled the new or changed files at the end. This session was inverted.
"He was told to get the T7-D supplemental specifically," she said.
Marcus was quiet for a moment.
"His Cult contact briefed him before this session," he said.
"Or Valerian's second source in the Directorate identified the supplemental as new material and flagged it through whatever channel they use," she said. "Either way—" She looked at the log. "Someone on the Cult side knew the T7-D supplemental existed before Abara pulled it."
"The document was uploaded to Cross's working files forty-eight hours after the second alignment," Marcus said. "Forty-eight hours and three minutes."
"Who had access to Cross's working files in that window," she said.
"Harrow," Marcus said immediately. "Internal Affairs. Director Chen. Cross herself." He paused. "And every Research Division researcher with Level 4 clearance."
"How many Level 4 researchers."
"Eleven," he said. "Including Abara."
She looked at the log.
"Abara knew the supplemental existed before his 0340 session," she said. "The access log shows he went directly to it. Eleven Level 4 researchers have access to Cross's working files. We've been watching Abara's terminal cluster. Have we been watching the other ten?"
Marcus was on his communicator before she finished.
---
Ren's team needed four hours to pull the access logs for all eleven Level 4 terminal clusters.
At 0800, Kira and Marcus went through the results with Ren on the secure relay connection. Ren's surveillance blessing — she'd always thought of it as a field-monitoring ability, the capacity to observe and track without being observed — had a precision that showed in his log analysis: he didn't just pull the access events, he'd tagged each one with the correlation between the access pattern and the specific files accessed, looking for the flag she'd identified.
Abara was the primary access point. He'd been the systematic gatherer.
But one other Level 4 terminal had accessed Cross's T7-D working files within the forty-eight-hour window before Abara's 0340 session.
"Dr. Sirin Vela," Ren said. "Junior Research Division. Level 4 clearance established seven months ago when the Protocol research division was expanded. Terminal cluster in the northern section of the floor — not the cluster we've been monitoring."
"Her access pattern," Kira said.
"Single access," Ren said. "Yesterday afternoon, 1540 hours. Cross's T7-D supplemental file, one read-only access event. Duration: nine minutes. No download." He paused. "She read it. She didn't pull it."
"She read the false document," Kira said.
"Yes," Ren said.
"And she's connected to Abara," Marcus said.
"That's what I need to establish," Ren said. "The single access event puts Vela in proximity to the information before Abara's overnight session. Proving a transmission from Vela to Abara — or from Vela to a Cult-side contact — requires either direct surveillance or additional access log correlation." He paused. "If Vela is a second mole, or if she's connected to Abara's pipeline, the double agent operation has a problem."
Kira looked at the relay display.
The double agent operation worked if Abara was the sole pipeline. The false integration-depth markers in Cross's supplemental would go to Abara's contact and from there to Valerian's research network. One clean document, one clean misinformation path.
If Vela had read the false document and also transmitted it — either confirming it to her own contact or flagging it as new Cross material — the operation still worked. The false document was the same regardless of who transmitted it.
Unless Vela had also read the real T7-D analysis.
"Vela's access history," she said. "Has she accessed Cross's files before?"
"Three previous accesses," Ren said. "Seven months ago, two months ago, one month ago. The access pattern doesn't show the systematic three-to-four day cycle Abara uses — more like research reference access. Looking at specific clusters when her own work intersects with them."
"What does Vela research," Kira said.
"She's listed as binding equation analysis support," Ren said. "Research division secondary team."
The binding equation analysis support team. Cross's division, not Abara's. Vela would have had legitimate professional reasons to read Cross's files.
"Does her research work intersect with the T7-D cluster," Marcus said.
"Her published division reports for the last seven months include references to blessing-curse integration mechanics," Ren said. "Consistent with a researcher whose work is adjacent to Cross's."
"Adjacent," Kira said. "Not Cross's immediate team."
"Correct."
She looked at Marcus.
The possibilities: Vela was a second mole. Vela was a researcher who had read the supplemental for professional reasons and transmitted it to Abara through an informal professional relationship. Vela was a Cult-adjacent contact who had been briefed to watch for new T7-D material and flagged it to Abara. Or Vela had read the supplemental for legitimate research reasons and hadn't transmitted anything.
"Ren," Kira said. "Active surveillance on Vela's terminal cluster starting now. Alert Marcus on any Research Division access event from that cluster." She paused. "And any communication between Vela and Abara — electronic, physical, anything."
"Confirmed," Ren said. "I'll have the surveillance network extended to her cluster by 0900."
The connection ended.
---
The legal working group called at 1000 with the response to the morning news cycle.
Fourteen news outlets, Kira's statement and Valerian's framing running in parallel. The response from the political environment had been — the legal team's assessment of "split," which meant the existing opinion landscape had held its divisions rather than shifting significantly in either direction.
"The statement was measured," the legal team lead said. "Measured was the right call in the first twenty-four hours. The Valerian narrative has the advantage of being simple — Protocol aberration, accountability gap, uncontrolled power. Your statement complicates the simple narrative without replacing it." A pause. "The next twenty-four hours need something that generates a different kind of attention."
"The mole pipeline documentation," Kira said.
"The mole pipeline documentation is a legal instrument," the team lead said. "Its political effect depends on when and how it enters the public record. If we drop it now — in the context of the morning news cycle — it reads as reactive. As Kira Vale attacking Valerian's credibility instead of addressing his argument." A pause. "The Council session is three weeks out. The documentation goes into the most effective political position if it arrives at the Council session as part of the formal record."
"Three weeks is Valerian's operating window," she said.
"Yes," the team lead said. "He'll move in that window. We're monitoring his next scheduled public event — he has a Cult advocacy meeting on Thursday. He may use that to escalate further."
"What's his escalation option," she said.
"Formal hearing request to the Council," the team lead said. "He's been building toward that for months. The alignment event gives him the specific trigger — a multi-location Protocol operation conducted without Council notification. He can file a formal hearing request on accountability grounds." A pause. "If he files, the Council has to respond within ten days."
"A formal hearing," she said.
"Where Protocol bearers would be required to address the Council's questions directly," the team lead said. "And where the Cannot Lie curse would prevent you from deflecting."
She was quiet.
"The Cannot Lie curse in a formal Council hearing," she said. "I could potentially be compelled to confirm operational details that the mole pipeline documentation is trying to keep outside the public record."
"The hearing is legally distinct from testimony compulsion," the team lead said carefully. "You're not legally compelled to answer every question in a hearing context. But politically—"
"Politically, declining to answer reads as confirmation," she said.
"Yes," the team lead said.
She looked at the window.
A Council hearing. The alignment event as the trigger. The Cannot Lie curse in a public forum with twenty-one bearers' identities and operational history as the subject matter.
"If he files the hearing request Thursday," she said.
"The Council reviews it within forty-eight hours," the team lead said. "If the Council approves it — and given current political climate, approval is likely — hearing is scheduled within the ten-day window."
"Eleven days from Thursday," she said. "Before the Council session where the mole documentation lands."
"Yes," the team lead said. "He's trying to run the hearing before our counter-documentation arrives at the Council level."
She ended the call.
She went to find Cross.
---
Cross was at the table with the T7-F integration mapping, which she'd been extending since the previous morning's eighteen-pair analysis. She was adding the network's other bearers to the map — estimating integration depths for everyone in the twenty-bearer group, building a comprehensive picture of where the network stood on the T7-F three-stage framework.
"The Council hearing," Kira said.
"I heard some of it through the wall," Cross said, without looking up. "The Cannot Lie curse in a formal hearing."
"Yes."
"The Architect designed the Cannot Lie curse to pair with Telepathy," Cross said. "Blessing five — you can read minds, you can't lie. The pairing makes certain things impossible for you — specifically, the kind of social maneuvering that depends on implying things that aren't true." She looked up. "But the T7-F integration framework says the curse-side generates the binding agent. If the Cannot Lie curse is deeply integrated with the Telepathy blessing—"
"What does the Cannot Lie curse generate," Kira said.
Cross looked at the page.
"The Cannot Lie curse's generation function," she said slowly. "In the context of the integration mapping." She ran a finger down the page. "Pair five is in early stage two. The Telepathy blessing's function is reading truth — receiving accurate information from other minds. The Cannot Lie curse's generation function—" She stopped.
"Cross," Kira said.
"Is also truth," Cross said. "The Telepathy reads it. The Cannot Lie produces it." She looked at Kira. "The pair five integration is producing truth as the binding agent output. The generation mechanism and the reception mechanism are the same fundamental function."
Kira looked at her.
"The Cannot Lie curse," she said. "Is making binding agent by forcing me to tell the truth."
"Every time the curse activates," Cross said. "Every truth you're forced to say. Every deflection you're prevented from making." She looked at the page. "The Council hearing — the formal questioning context where the Cannot Lie curse is most active — would be the highest generation event for pair five's integration function." She paused. "You'd walk out of that hearing with a significant integration advance on pair five."
Kira sat down.
"The Architect designed a formal testimony context into the test," she said.
"The Architect designed twenty-four years of the Cannot Lie curse into the test," Cross said. "The formal testimony context is the highest-intensity version of what the curse has been doing your entire life." She looked at Kira. "Whether this means you should attend the hearing or avoid it—"
"The pair five integration advances," Kira said. "The truth-generation mechanism runs at maximum. The Telepathy reception function gets the most active generation it's had since the pair was first integrated."
"Yes," Cross said.
"And the political cost," Kira said. "In a formal hearing, the Cannot Lie curse runs at maximum, which means I answer questions I'd otherwise find ways not to answer."
"Yes," Cross said. "Both outcomes happen simultaneously." She looked at Kira. "The Architect's design, probably."
Kira looked at the window.
The hearing as a generation event. The Cannot Lie curse and the Telepathy blessing reaching their highest integration activity in a formal public context. The political exposure and the integration advance running together.
Both at once.
The Architect had built the hearing into the test forty years before Valerian filed the request.
"I'm not going to avoid the hearing," she said.
Cross didn't look surprised.
"I didn't think you would," she said. "I'm documenting the pair five integration projections so you know what to expect." She paused. "The T7-F second-stage framework says to hear the generation as data. In the hearing context, the generation is active on every question you answer." She looked at Kira. "Don't manage around it. Listen to what it's telling you."
"What will it tell me," Kira said.
"What's true," Cross said. "That's what the pair five generation function produces. In a hearing, that might be the most useful information available."
Kira looked at the relay display. At 16.8%, stable.
"Valerian files Thursday," she said. "We have until Thursday to prepare."
"Or to move faster than Thursday," Cross said.
Kira looked at her.
"The mole pipeline documentation," Cross said. "The legal team said the Council session is the best timing. But if Valerian files Thursday and schedules the hearing before the Council session—" She paused. "The documentation doesn't have to wait for the session. It can be submitted to the Council's review as supplemental evidence to the hearing request itself."
"The hearing request triggers the documentation submission," Kira said. "Instead of the documentation arriving at the Council session after the hearing."
"Yes," Cross said. "The hearing context and the documentation arriving together."
Kira looked at the window.
The pair five generation function. Truth.
"Tell the legal team," she said.
[INTEGRATION: 16.8% — VELA: SECOND ACCESS POINT — HEARING: POTENTIAL T-MINUS 4 DAYS — PAIR 5: STAGE-TWO IDENTIFIED]
