Every Loop Costs a Friend

Chapter 14 - After-Action

Chapter 14 · 1,331 words

Garran Dault read the report three times.

His office was on the guild's third floor, a functional space, organized, with stacks of previous reports in neat piles on every surface. He moved stiffly, old injuries protesting the weather, and settled into his chair with the careful economy of someone who'd learned to work around pain.

Soren's report lay open on his desk. The pages were marked with his annotations, small, precise notes in the margins, underlined passages, question marks beside specific claims.

He adjusted his reading glasses, a personal affectation in an otherwise institutional space, and returned to the entity positioning data.

Four coordinates, mapped relative to the chamber entrance. The precision was extraordinary. Each position was given in paces from the entrance and distance from the nearest wall, with enough detail to reconstruct the chamber's geometry. A first-run scout should have been able to note that entities existed, that they killed, that they were imperceptible. Not this. Not coordinates.

Garran had trained hundreds of scouts over two decades. He knew what Initiate-level observation looked like. This report exceeded that standard by a measurable margin.

He turned to the safe route section. The route was described in detail, a path through the first chamber, verified through direct navigation. The route implied systematic mapping. Someone had understood the chamber's geometry well enough to thread a path between killing zones. That required knowing where the entities were. And you couldn't know where the entities were from a single expedition.

Unless you'd watched your companions die and counted the positions.

Which was what the report claimed. But even that required a level of analytical detachment that most Initiates didn't possess under lethal conditions.

He turned to the movement patterns section and stopped.

*Entity positions are fixed during individual runs but shift between runs based on team composition. The tower adapts entity placement to the number and rank of expedition members.*

Movement patterns. Adaptive properties. This wasn't observation from a single expedition. This was pattern recognition across multiple runs. This was the kind of analysis that required at least two full expeditions, and the current report claimed to be from a scout's first entry into the tower.

Garran set the report down and removed his glasses.

He pulled another file from his desk, the expedition records for Soren's team. Team leader: Petra, Copper-rank. Expedition date: three days ago. Floor accessed: 1. Team casualties: four. Survivors: three, including Soren Ashfall.

He cross-referenced with Petra's own debriefing. Her report was brief, professional, and confirmed the timeline. She'd noted that Soren had mapped entity positions through companion death patterns and led the team through a safe route. She'd also noted, in a single flat sentence, that his knowledge "exceeded what would be expected from a first-run Initiate."

Garran put the files down.

Soren Ashfall. Nineteen years old. Licensed for nine weeks. Entered the tower for the first time two weeks ago. Died, according to the expedition's initial report, and was somehow back in the tower three days ago with knowledge that no first-run scout should possess.

The most likely explanation was that Soren had some form of prior knowledge, perhaps from a relative who'd explored the tower before the current emergency, or from access to classified expedition records. But the movement pattern data didn't fit that explanation. Those patterns described how the tower adapted between runs. That was information you could only get from experiencing multiple runs.

Unless the scout was lying about the data's source, or something else was happening entirely.

Garran had seen impossible knowledge before, in his decades of guild service. It usually meant one of two things: either the person was a spy, or they'd found something inside the tower that had changed them.

He pulled a fresh file from his desk drawer and opened it to a blank page. Whatever the explanation, he would document it.

He began a quiet investigation.

Over the next three days, Garran cross-referenced Soren's data against every other team's expedition reports. The data was consistent. Soren's coordinates matched what other teams had found, though no other team had mapped positions with the same precision.

The movement patterns were the most anomalous element. No other report mentioned the tower's adaptive properties.

On the second day, Garran sat at his desk with two reports side by side. Soren's after-action form on the left, a Copper-rank team's expedition log on the right. The Copper-ranks had encountered the same first chamber, lost two members to invisible entities, and retreated. Their report described the entities as "unlocatable" and recommended "caution and further reconnaissance." Soren's report, from the same floor, contained a complete coordinate map and a verified safe route.

Garran drew a line under the word "unlocatable" in the Copper-rank report. Then he looked at Soren's precise coordinates. The same chamber. The same entities. A different level of observation entirely.

He began watching Soren in person.

He positioned himself at the training grounds during combat drills, standing at the edge of the exercise yard with the casual attention of someone with nothing better to do. He watched Soren during a briefing on second-wave team assignments, noting the way the Initiate stood at the back of the briefing hall, listening carefully, speaking only when directly addressed. The voice was controlled, measured. The kind of voice that belonged to someone choosing each word with care.

None of it proved anything. But the discrepancies in the report remained, and Garran's professional instinct told him they weren't accidental.

He requested Soren's personnel file from the guild's records office. The file was thin. Standard background, no family connections in the capital, training records that showed adequate but unexceptional performance. Nothing that explained the gap between the scout's experience and his knowledge.

Garran closed the file and sat in his office, the report open on his desk.

The data was valuable. That was undeniable. If the movement patterns were accurate, they would save lives. Future teams would enter the tower with better information, and fewer people would die on Floor 1.

But the source of the data was a problem. And Garran had spent too many years in the guild to believe that impossible knowledge came without a cost.

He began writing his own report, a confidential assessment addressed to the guild's expedition command. He documented the discrepancies, noted the anomalies, and recommended further observation.

He didn't recommend immediate confrontation. He wanted more data.

He wanted to know what Soren Ashfall was carrying.

Soren noticed the attention on the fourth day after submitting his report.

It was subtle. Garran's presence at the training grounds, the training officer's gaze during briefings, the way conversations seemed to pause when he entered a room. Nothing overt. Nothing that could be called surveillance.

But Soren knew what it felt like to be watched. He'd been expecting this since the moment he'd written the movement patterns section.

He adjusted his behavior carefully. He kept his combat drills at the expected level, competent but unremarkable. He spoke only when spoken to during briefings. He avoided the guild hall's common room in the evenings, eating in his bunk or at a quiet corner of the mess hall.

He didn't know what Garran had found. He didn't know how much the training officer suspected. But he knew the report contained anomalies, and he knew Garran was the person most likely to notice them.

He knew exactly what Garran was looking for. He couldn't explain it. The loop was real. The erasures were real. The conclusions were permanent. But none of that could be said aloud. The truth was either unbelievable or, worse, believable in a way that would deepen Garran's bond with him and put the training officer at erasure risk.

So he maintained the cover. He answered questions with careful, neutral responses. He offered nothing more than what he'd decided was safe to share.

And he waited for the confrontation he knew was coming.