POV: Sylra
The worst kind of problem was one that had already been running while you were looking the other way.
War room. Four maps, three document stacks, one table between all of them. The kind of room that removed every courtesy except the one that mattered: precision.
I laid the facts out flat — no staging, no order that implied hierarchy between pieces. Everything visible at once.
The forged medical records. The Lineage Challenge filing. The ten-day audit requirement. The fifty-five-day Panel window. The access log anomaly Vedran was still pulling apart.
"Kael," I began. "Assessment timeline. How the audit request sits against the filing deadline, where the margins are."
He had already been building it before I asked — because Kael built the framework before the ask, because waiting to be asked wasn't useful when the structure was already available.
"The audit request goes in today," Kael said, setting a folded document on the table. "Panel receipt acknowledged within twenty-four hours. Auditor assignment within forty-eight. Audit execution begins day three."
"Audit completion?"
"Day thirteen," he told me. "Three days of buffer if the Panel's auditors find anything requiring secondary verification."
"That leaves forty-two days for the Panel to review the evidentiary case and rule," I said. Kael nodded. "The margin is functional. It is not comfortable."
"Solvayne's legal team files a delay motion," Caelen said. Not a question. He stood at the far end of the table, arms at his sides, reading the timeline the way he read a patrol map — for the point where the line got thin.
"They can challenge the auditor assignment," Kael said. "Dispute scope, methodology, auditor independence. None of those motions succeed, but each one costs days."
"How many days?" I pressed.
"Two to four per motion," Kael replied. "Three filings could push us into single-digit margin."
Caelen said nothing. He looked at the timeline.
"Then the audit filing has to be airtight on day one," I said. "Scope, methodology, auditor credentials — every challenge vector pre-addressed in the request before they can raise it."
"Already drafted," Kael said. "It anticipates four distinct challenge vectors. The language is clean." He delivered it without inflection, which meant he was certain.
Caelen didn't sit. He hadn't sat since we entered — he moved along the far edge when he spoke, held still when he listened.
At the near corner, Vedran worked. Access log printouts spread across his section of the table, cross-referenced against the forgery's technical signature. Three marks in three colors on three sheets.
"Vedran," Caelen said. Not a question — the economy of a man who had watched Vedran work enough times to know that anything before the right moment was wasted breath.
Vedran didn't look up. He placed a fourth sheet beside the three marked ones, aligning them with the care of someone assembling an argument rather than a display.
"Three entries," he said. "Three separate archive access sessions. Different dates, each one six weeks apart from the last."
"Six weeks," I said. "Not random. Not opportunistic." He replied: "Each session runs eleven to fourteen minutes. Short enough to fall inside the routine access band. Short enough to look like maintenance."
"But not maintenance," Caelen said. "Not even close," Vedran confirmed. "The depth of each access goes three layers deeper than any maintenance function requires. The anomaly is small. Consistent. Designed to be small."
"Each session uses the same technique signature as the forgery," I said, looking at Vedran's marks and reading the pattern. "Same entry point. Same operator."
"Correct," Vedran said. "The technique doesn't vary across sessions. A breach involving multiple operators produces different signatures. This is one person. Three sessions. Planned spacing."
"Six weeks apart," Kael noted. "The first session predates the filing by twelve weeks. Someone began this four months before the announcement."
"Twelve weeks before the announcement," Caelen said. He had moved to the table. "The pipeline began while the circuit was still forming. Before the forest. Before the third bond."
The room took that in. Caelen ran a hand flat across the table once — not a gesture, a contact. The involuntary movement of a man absorbing a piece of information and trying to hold still while he did.
"If the pipeline started that early, the announcement wasn't the operation," Caelen said. "It was one delivery point in something longer." He looked at Vedran. "How many sessions total, including what you haven't confirmed yet?"
"Three confirmed," Vedran replied. "The six-week interval suggests a deliberate pattern. If it held from the beginning, there may be two to three additional sessions predating my first confirmed entry."
"Which means Veth was reading our internal structure as the circuit was being built," I said. "Running a live read of this court as it happened," Vedran said. "Concurrent with the operation we thought we were running."
"We need to know what went out in each session," Kael cut in. "Not just that the pipeline ran — the specific documents, the specific dates accessed."
"That is what the chain gives us," Vedran said. "When we have the name, we pull every session that person authorized and trace the exact content. Session by session."
"Archive access logs are audited quarterly," Caelen noted. "The first session fell inside an audit window that would have reviewed it."
"And passed," Vedran returned. "Whoever did this timed each session to fall within the parameters that read as routine in a quarterly review. They knew the audit cycle."
"They weren't just inside the archive," I said. "They were inside the audit process itself." "Every layer of it," Vedran confirmed. "They knew exactly where the review line was and stayed behind it. Every time."
"Suspect pool," Caelen said. His voice carried the flat edge of a man who intended to leave this room with names. "Where does the archive pattern put us?"
"Ithara's laboratory access narrows to three," Vedran replied. "Cross-referenced against the archive session timing and the pipeline pattern — one of those three was in the right place on the right dates. All three times."
Vedran gathered the four sheets and aligned them side by side on the table — three access sessions, one forgery, the same technical signature threading through all four at every point of entry without variation.
"Quarterly audit cycles. Six-week spacing. Session lengths calibrated to read as routine." He set the last sheet down. "This wasn't improvised under pressure. Someone mapped every review threshold in this archive and built the operation around them."
He looked at me. "Whoever is sitting inside this palace didn't breach us once and run. They've been here for months, moving material out at a pace careful enough that no one was looking for it."