Extra's Path To Main Character-Chapter 29 - 28 - What the Index Remembers

The Memory Index flagged it on day eighty-nine.

Amaron was reviewing his training logs when the notification appeared — not visually, not with sound, but with the particular quality of attention-shift that meant the Void System had cross-referenced something in his recent observations against the stored records from his first life and found a match worth bringing to his attention.

He stopped what he was doing and pulled up the reference.

The Kessen Expedition. Grade 3 rift clearance in the eastern district. Scheduled to begin in four days. Team composition: six Hunters, mixed rank B and C, led by a Guild senior named Orvath who had the reputation for running difficult operations cleanly. Duration: approximately one week. Outcome in the original timeline: successful clearance, zero casualties, substantial commercial value extracted.

Except that wasn’t the complete record.

Amaron pulled up the deeper layers of the Index — the details he’d filed away in his first life as context rather than critical information. The Kessen Expedition had been successful. But it had also been the operation where Elian Solhart, then eighteen years old and recently promoted to B-rank, had taken his first serious injury. Not life-threatening. Not career-ending. Just a significant wound that had required three weeks of recovery and had taught him something important about overextending during combat that he’d carried forward for the rest of his career.

In the original timeline, that injury had happened on day five of the expedition, in the rift’s deepest chamber, during an engagement with a crystalline entity that had been significantly more dangerous than the preliminary assessment suggested.

Amaron looked at the date. Four days from now.

He opened his notebook and wrote carefully.

Day 89. Kessen Expedition scheduled. Elian will be injured on day 5 if the original timeline holds. Injury is significant but not critical — three-week recovery. But timeline has been diverging. May happen differently. May not happen at all. Need to prepare for multiple scenarios.

He stared at what he’d written and tried to determine what preparation looked like for an event that might not happen, that he couldn’t prevent without revealing knowledge he shouldn’t have, and that had shaped the original protagonist in ways that might matter.

— ◆ —

The question was not whether to intervene. The question was how.

In his first life, Amaron had not been on the Kessen Expedition. He’d been working a low-level monitoring contract in the third district while the significant people did significant work elsewhere. He had learned about Elian’s injury secondhand, through Guild reports and overheard conversations, the way he learned about most things that mattered.

In this life, he had options.

He could apply for a position on the expedition. His C-rank registration and recent performance evaluations made him eligible for B-rank team positions with approval. But joining the expedition would mean being present for an event he had complete foreknowledge of, which created its own complications. If he prevented the injury too easily, it would raise questions. If he failed to prevent it despite being there, it would raise different questions.

He could warn Elian directly. But warning him would require explaining how he knew something dangerous would happen on day five of an expedition that hadn’t started yet, in a rift that hadn’t been fully surveyed. That explanation did not exist in any form that wouldn’t sound like madness or prophecy.

He could do nothing. Let the expedition proceed as planned, trust that Elian was competent enough to handle himself, accept that some injuries were part of the process of becoming the person the story needed him to be.

This last option was the most strategic. It was also the one he knew, with absolute certainty, that he would not choose.

Because the plan had changed. Because people mattered more than perfect positioning. Because Elian Solhart had walked into a cartographer’s shop and refused to let him stay alone, and that meant something.

He closed the notebook and went to find Elian.

— ◆ —

He found him at the Guild hall, reviewing contract documentation with the focused attention of someone preparing for a major operation. Amaron waited until he’d finished the page he was reading, then approached.

"The Kessen Expedition," Amaron said without preamble. "You’re on the roster."

Elian looked up. "I am. Team lead is Orvath — he’s good. Grade 3 clearance, eastern district. Should be straightforward." He set down the documentation. "Why? Are you interested in joining?"

"Maybe," Amaron said. "What’s the team composition?"

Elian pulled up the roster. "Six total. Three B-rank combat specialists including me, two C-rank support including a dedicated healer, one surveyor position still open. They’re looking for someone with structural assessment experience because the preliminary survey flagged some instability concerns."

Structural assessment. That was his official specialization now. He could apply for the position with legitimate justification.

"I could fill that position," Amaron said.

Elian’s expression shifted to something between interest and concern. "You could. But it’s a Grade 3 rift. Higher risk than what you’ve been running. Are you ready for that?"

The honest answer was that he’d cleared Grade 3 rifts in his first life more times than he could count and the risk level was manageable if you knew what you were doing. The answer he could actually give was more complicated.

"I’ve been training," he said. "And I’ve worked with structural instability before. I can handle it."

Elian studied him for a moment. Then he nodded. "All right. I’ll recommend you to Orvath. He makes the final call, but if I tell him you’re competent and reliable, he’ll likely approve it. But Volg—" He paused. "If you’re coming on this operation, I need to know you’re doing it because you want the work, not because you’re worried about me."

Amaron looked at him. The observation was more perceptive than he’d expected.

"Both," he said, with the honesty that was becoming harder to avoid around Elian.

"Fair enough." Elian picked up the documentation again. "I’ll talk to Orvath this afternoon. Expect a response by tomorrow. And Amaron — thank you. For watching my back."

"That’s what teammates do," Amaron said, and left before the statement could feel more significant than it already did.

— ◆ —

The approval came through the next morning. Orvath accepted his application based on Elian’s recommendation and his recent survey contract performance. He was officially on the roster for the Kessen Expedition, scheduled to depart in three days, with a surveyor position and structural assessment responsibilities.

Amaron spent those three days preparing.

He reviewed every detail of the original timeline’s expedition that his Memory Index contained. The rift’s layout. The entity types encountered. The specific chamber where Elian’s injury occurred and the circumstances that led to it. He mapped out alternative approaches. Identified intervention points. Calculated exactly how much he could reveal without compromising his cover beyond recovery.

He also updated his notebook with a contingency plan.

If the timeline holds: Elian engages crystalline entity on day 5, chamber 7-D, overextends during pursuit, takes significant injury. Intervention: position near engagement zone, maintain barrier support, redirect entity before critical strike.

If timeline diverges: unknown variables. Adapt in real time. Priority remains: Elian survives intact.

Risk: revealing capability beyond C-rank to 6+ witnesses including senior Guild member. Acceptable if alternative is Elian injured.

Conclusion: people > plan. Again.

He closed the notebook, packed his field gear, and tried not to think too hard about the fact that he was walking directly into an event from the original timeline with the explicit intention of changing its outcome.

The Void System had noted, correctly, that he’d accepted visibility as a cost of being present.

He was about to test exactly how much visibility he was willing to accept.

— ◆ —

The night before the expedition, he went to the Solhart residence.

He knocked. Vela answered. She took one look at him and said, "You’re doing something dangerous tomorrow."

"Grade 3 rift clearance," Amaron said. "Standard operation."

"Nothing about the way you’re standing right now suggests ’standard.’" She stepped aside to let him in. "Elian’s upstairs. But come have tea first. You look like you need it."

He sat at the kitchen table — his chair now, he’d stopped thinking of it as borrowed — and drank tea while Vela moved around the kitchen with the familiar efficiency that he’d come to associate with safety.

"Are you worried about tomorrow?" she asked after a while.

"I’m prepared for tomorrow," Amaron said. "That’s different from worried."

"Is Elian in danger?"

The question was direct. The answer was complicated.

"He’s always in danger," Amaron said carefully. "He’s B-rank combat. That’s the work. But I’ll be there. And I’m good at keeping people alive."

Vela looked at him with the warm, assessing attention that meant she understood more than he was saying. "You’re going on this expedition because you’re worried something will happen to him."

"Yes."

"Can you tell me what?"

"No," Amaron said. "But I can tell you I’ll do everything I can to make sure he comes back intact."

Vela was quiet for a moment. Then she nodded. "That’s enough. Just — make sure you come back intact too. This house has gotten used to having you around. We’d notice if you didn’t."

Amaron looked at his tea and had no response that would be adequate. So he simply said, "I’ll be careful."

"Good," Vela said, and refilled his cup.