Every Loop Costs a Friend

Chapter 17 - Leverage

Chapter 17 · 1,743 words

The data conflict was worse than he'd expected.

Soren spread Thessa's alternative route maps across the data-review table and layered his own verified coordinates on top, using transparent parchment sheets to keep both visible. The guild's data-review room was empty. It was past midnight, the lamps burning low, and he'd had the space to himself for two hours.

He'd told himself he was evaluating her data for useful information. That was true. Her team had explored corridors he hadn't mapped, and the east approach to the second chamber was genuinely new.

But the overlap was the problem.

Where both teams had mapped the same corridors, the data should have agreed. It didn't. At coordinate 11F/6E, Thessa's map marked the zone as clear. Her team had passed through without incident. His death-pattern data showed entity presence at that position. A confirmed location from two separate runs where companions had died at exactly that coordinate.

He stared at the overlapping marks. Her team had walked through a kill zone and survived. The entity positions had shifted between his mapping runs and hers. The tower adapted to team composition, changed where the imperceptible things stood. Her survival was luck. But her map said *clear*, and any team that followed her data without correction would walk into positions that might or might not be occupied depending on when they entered.

The tower shifted entities between runs. Her data was correct for her run. It would be wrong for the next one.

His data was different. His verified conclusions didn't just record where entities had been. They captured the pattern of how the tower placed them. The crystallized knowledge wasn't a fixed map. It was an understanding of the system. Entity positions shifted based on team composition, but the shift followed rules he'd verified under pressure and the tower had acknowledged as permanent.

Her data was a snapshot. His was a framework.

But her data contained information his framework didn't have. The corridors she'd explored beyond junction 14F were real. The east approach was real. The alternative second chamber entry her team had found, through a narrow passage on the northern wall, was real.

He needed her data. And her data needed his corrections to keep her teams alive.

The question was whether he could make the exchange without revealing too much about where his knowledge came from.

He began marking corrections on her maps. At each point where her data contradicted his verified conclusions, he drew a small circle in red ink and wrote the corrected coordinate beside it. Seven corrections in total. Seven positions her team had walked through by luck and marked as clear. Seven positions that would kill the next team that followed her map without adjustment.

Beside each correction, he wrote a single word: *entity.*

Then he pulled out a fresh sheet of parchment and began listing the information he wanted from her: the complete alternative corridor data beyond junction 14F, the northern passage to the second chamber, any observations about the second chamber's interior that her team had recorded, and, carefully, at the bottom of the list, any data her team had collected about the staircase to Floor 2.

He didn't expect much there. His own teams had barely reached the staircase. But if Thessa was as aggressive as her casualty reports suggested, she might have pushed past it.

He worked for another hour, organizing the exchange into two columns: what he would give, what he wanted. The columns were roughly balanced. His corrections would save her teams from walking into confirmed entity positions. Her corridor data would give him access to areas he hadn't explored.

It was clean. Professional. Two people trading information of roughly equal value.

It was also the exact kind of repeated, mutually beneficial interaction that deepened bonds.

He knew this. The erasure mechanic targeted bond depth. Stronger connections produced more complete erasure. Every positive interaction with another person increased the connection. Every successful exchange built trust. Trust, repeated over time, became the kind of bond that the loop would target first.

He looked at the two columns on the parchment.

The Floor 2 data was too valuable to refuse. He needed to know what lay above the first staircase, and Thessa's team might have pushed far enough to provide initial intelligence. His own verified conclusions covered Floor 1 completely, but Floor 2 was unexplored territory.

He rolled up the parchment and tucked it inside his jacket.

He would make the exchange. He would be careful about how much he revealed. And he would accept the cost of deepening a bond with Thessa Kaine because the alternative, entering Floor 2 without data, was worse.

The calculation was clean. The feeling underneath it sat wrong.

---

She agreed to meet in the guild's unused briefing room on the second floor, a narrow space with a long table and chairs pushed against the walls, normally reserved for team debriefings that no one had scheduled tonight.

Thessa was already there when he arrived. She had her maps spread across the table, weighted at the corners with iron candle holders. A stylus in her hand. No greeting when he walked in.

"You found the conflicts."

"Seven positions where your data contradicts verified entity locations." He pulled the rolled parchment from his jacket and set it on the table. "Corrections are marked."

She unrolled it, scanned the red circles and the single word beside each one. Her expression didn't change.

"Seven," she said.

"Seven."

She looked up from the parchment. "You're certain about these positions."

"Yes."

"Because your framework accounts for position shifts between runs." Not a question.

He didn't answer directly. "Your teams walked through all seven. The positions had shifted by the time your team reached them. They won't shift the same way next time."

A pause. She set the parchment down and picked up her stylus.

"Fine." She pulled her own stack of maps toward the center of the table, thicker than he'd expected, multiple sheets bound together with leather cord. "Everything beyond junction 14F. Three alternative corridors, two of them connecting to the second chamber through different approaches. The northern passage is narrow, single file, low ceiling, but it bypasses the main corridor entirely."

She spread the maps out. He leaned forward, scanning the coordinates. The data was detailed. Timestamps, traversal notes, environmental observations. Her annotation style was hasty but thorough. She didn't miss things.

"The second chamber's higher than the first," she said, pointing to a note in the margin. "Ceiling disappears into haze. Different acoustics. Sound carries. And there are marks on the floor. Parallel scoring, too regular to be natural."

He'd seen the scoring marks himself. Faint, parallel lines on the second chamber's floor. He'd noted them in his report but hadn't had time to investigate.

"The staircase?" he said.

Her hand paused over the maps. "We reached it. Black steps, sourceless light, going up. We didn't ascend."

"Floor 2 data?"

"Nothing. We turned back at the staircase." She looked at him. "That's the limit of what I have. You want Floor 2 intelligence, you'll have to get it yourself."

He absorbed this. The staircase existed, confirmed by a second team. Floor 2 was above. No one had entered it yet.

"The exchange is even," he said.

"It is." She began copying his corrections onto her maps, her stylus moving quickly, precisely. The scratch of the nib was the only sound in the room.

He watched her work. She was good at this. The mechanical precision of transcribing coordinates, the spatial reasoning that let her integrate his corrections into her existing route structure without losing her own data. She wasn't just collecting information. She was building a system.

It was uncomfortable to watch. Her competence was directed at the same problem he was solving, and she was solving it with a method that treated companion deaths as acceptable data-gathering expense.

She finished the corrections and set the stylus down.

"These positions," she said. "Your framework accounts for entity shifts. Mine doesn't. That means your system is more complete than what you've shared."

"It covers Floor 1."

"It covers more than Floor 1. The way you described the shift mechanism, team composition as a variable, that implies a structural understanding of how the tower operates. Comprehension, not just observation."

He kept his face neutral. "I pay attention."

"You pay attention in a way that produces infrastructure." She leaned back in her chair. "I don't need to know how you do it. I need the data to keep working."

"The corrections are yours now."

"This run." She held his gaze. "Next time my team finds something that contradicts your maps, I'll bring it to you first."

The words landed differently than she intended. *Next time.* The phrase carried the weight of a standing arrangement. Repeated contact, mutual dependence, the kind of ongoing exchange that built trust through consistency.

He'd walked into this calculating the cost of a single transaction. She'd just turned it into a relationship.

"Fine," he said.

She nodded, gathered her maps, and stood. At the door, she paused.

"The scoring marks in the second chamber. My team measured them. Forty centimeters apart, consistent depth, running the full length of the east wall." She looked back at him. "Nothing natural does that."

"I noticed."

"Good." She left.

Soren sat alone in the briefing room, her maps spread across the table beside his own. The Floor 2 data was here. Corridor layouts, approach variations, environmental observations. Valuable. Genuinely useful. He could begin planning his Floor 2 reconnaissance with real information instead of speculation.

He looked at the maps and thought about the words she'd used without quite meaning them. *Next time.*

The transactional relationship was established. Functional. Mutually beneficial.

And every successful exchange from here forward would pull them closer together. Repeated contact. Growing trust. The slow, invisible accumulation of connection that the loop's erasure mechanic would target the moment he died.

He began organizing her Floor 2 data into his own coordinate system, marking useful information in black ink, noting gaps in red. His hands were steady. His mind was already working through the operational implications.

The feeling sat underneath the calculation, quiet and persistent. He was binding himself to another person. The bond formed through the slower mechanism of mutual dependence. It was the kind of bond that wouldn't feel like a bond until it was too late.

He kept working.

---