The Wrong Kind of Immortality

A few weeks passed as they always did. Training in the mornings. Correspondence and merchant work before midday. Consortium duties in the afternoon.

The routine held. His road infrastructure recommendations continued to circulate through the system, generating occasional follow-up questions and the slow, incremental progress that characterised institutional change. He submitted assessments, reviewed case files, and maintained the quiet rhythm of a man who intended to remain unremarkable.

Then the document arrived.

It was waiting on his desk when he came in that afternoon, slotted among three routine requests and a Consortium circular that had nothing to do with him. No seal marked it as urgent. No cover note accompanied it.

Orestis set his satchel down and read the header: Preliminary Training Capacity Review.

Below it, a block of text detailed scope and purpose in the careful, bloodless language of institutions that preferred to be seen preparing rather than acting. The document spoke of expanded readiness, increased throughput, and projected recovery efficiency under accelerated conditioning.

A training methodology. One significant enough to warrant Consortium review, apparently.

The Orthessa Mage Consortium was best known for its study and application of magical systems, but its expertise extended to other fields as well. When an organisation wanted a process tested for long-term stability—spellwork, infrastructure, or even something as mundane as a training regime—the matter often ended up at the Consortium for external review.

Orestis checked the routing. And paused.

Well. This is unexpected.

The document had originated in Kallistrate—Crown and Temple, jointly authored. It should have stayed within their own channels. The fact that it hadn’t, meant they wanted the numbers checked by someone without a stake in how they turned out. Not because they were unsure, but because the method was meant to scale.

Even setting aside the irony of this document reaching him of all people, Orestis had not expected to have the clearance to review it in the first place.

My name has apparently begun circulating—or they ran out of people who preferred comfortable answers. Either way, someone has decided my judgement is reliable enough to review this.

He sat, unfolded the pages, and read on.

The Crown’s involvement was evident in the structure: resource tables, timelines, projected outputs—all arranged with the confidence of people accustomed to thinking in terms of scale. The Temple’s presence was subtler. It appeared only in footnotes and parenthetical phrases: clerical intervention cycles, post-healing functional readiness, aura output stabilisation following treatment.

Partway through, the shape of it began to feel familiar.

He remembered that one of the reasons later cited for Kallistrate’s victory was the number of aura-capable soldiers it had deployed—far more than Logrion had expected, and far earlier than anyone thought possible.

So this was how they had done it.

They had run soldiers through repeated cycles of intense training, then used divine healing to repair the damage. The program was ambitious, but not incoherent: physical conditioning under sustained load. Repeated exposure to aura activation thresholds. Recovery handled through scheduled clerical healing, treated as predictable rather than uncertain.

The numbers were neat. Comfortingly so. They assumed that healing removed the cost.

It didn’t.

Healing spells—even divine ones—restored tissue, closed tears, reset alignment, and returned blood to proper flow. What they did not do was increase tolerance or strengthen what had already failed.

Each cycle would leave the soldier whole, but no more capable of enduring the next strain than before. The damage would be gone, but the limit would remain. Push hard enough, often enough, and the distance between the two vanished.

The programme would work. It would compress years of development into months. And the resulting force would carry its failures forward, unseen, until they accumulated faster than healing could correct.

Whether the Temple understood the risk was unclear. That they had proceeded anyway was not.

Even if they did, they’d likely consider the cost acceptable. Same logic that decided my parents were an acceptable cost. Different scale. Same arithmetic.

Orestis folded the document carefully.

The programme would succeed—at first. What mattered was how it would be described when it stopped.

***

The Owl looked up as Orestis approached the desk.

“Spellwork again?” the archivist asked.

“Not this time,” he replied. “Failure patterns. Long-term strain in systems that were declared resolved.”

The Owl tilted his head. “Does this have anything to do with the document that arrived on your desk this afternoon?”

Of course he knows about it.

“Tangentially,” Orestis said.

The Owl studied him for a moment. Then slid a token across the desk. “Third floor. Post-remediation reports. You’ll want Stacks C through F.”

Orestis took the token and went upstairs.

The material was exactly what he needed. Ward degradation under sustained load. Structural fatigue in transit arrays. Progressive misalignment in stabilisation frameworks. None ended in catastrophe. They all ended in correction.

He read quickly, skimming failure summaries, slowing only at remediation notes. Reinforcement added. Load redistributed. Margins widened. Oversight adjusted.

Always adjusted.

What caught his attention was not what they fixed, but what they didn’t revise. The language was consistent: failures attributed to variance, material limits, unforeseen interactions. The system itself was rarely questioned. It hadn’t failed, they claimed. It had simply been stressed beyond expectation.

Expectation. A convenient place to hide assumptions.

He opened another volume. A relay collapse that had occurred only after years of continuous operation. No single overload. No identifiable trigger. Just a gradual narrowing of tolerance until correction was no longer sufficient.

It was revealing of Orthessa’s operational beliefs. It didn’t pretend systems lasted forever. It accepted that they wore down. What mattered was recognising when reinforcement stopped helping and redesign became necessary.

The Owl passed by once, paused, and set down two additional volumes without comment.

“Related,” he said.

I appreciate an archivist who understands what you’re looking for before you do.

He continued reading. By the time he returned the token, he had everything he needed.

Not because he had learned anything new. He hadn’t.

But that was the point.

Back in his workspace, he laid the training document beside his notes.

The language he needed was already there in Orthessa’s records—in its quiet habit of naming limits without assigning blame.

He adjusted the terminology. Stability became function. Recovery became operational readiness. Margins became load tolerance.

None of it was inaccurate.

Then he added a footnote citing infrastructure precedent: long-term operation under repeated correction, and strain that accumulated despite successful repair.

The language was measured. Nothing inflammatory. Nothing speculative. It served only to provide context.

Context that anyone paying attention would find impossible to ignore.

He continued through the document. Each adjustment was small. Each was technically correct. Together, they shifted the analytical vocabulary from the Temple’s framing—where healing was a solution—to the Consortium’s framing—where repeated correction was a known failure pattern.

Language matters. Whoever names a failure usually decides who is blamed for it.

When he finished, the document appeared unchanged to anyone not specifically looking for the difference. He submitted it. No reply followed.

By morning, another request had arrived, referencing the revised section without comment. The programme would continue. His review would be filed. And when it all eventually collapsed, the records would show that the risks had been identified, framed in institutional language, and quietly ignored.

Anyone who reads the footnotes carefully will understand exactly what they imply.

Most people never read footnotes.

***

When Orestis returned to the inn that evening, the proprietor stopped him at the desk and handed him a letter.

“Came earlier,” she said. “Didn’t catch you before.”

Orestis glanced at the seal, then nodded and took it. The paper was stiff, official, and unremarkable in every way that mattered.

Right. This, then.

He did not open it immediately.

Upstairs, he set his satchel down and removed his coat. Only then did he break the seal. It was something he had always known would arrive eventually.

Both this and the Temple document likely arrived with the same courier batch. Kallistrate’s bureaucracy is nothing if not efficient at bundling contradictory intentions.

The contents were simple.

Office of Civic Registration

Kallistrate Administrative District

Notice of Recall

In accordance with standing statutes governing civic obligation, you are hereby notified that your presence is required in Kallistrate for assessment and assignment.

You are to present yourself at the Office of Civic Registration within thirty (30) days of receipt of this notice.

Failure to comply may result in penalties as outlined in Section IV, Subclause 7.

If you believe this notice has been issued in error, you may submit a petition for review. Processing times are subject to availability.

This notice constitutes official record.

No name in the salutation, nor any justification. No urgency beyond the deadline, and no indication that anyone expected resistance. It was merely a general notice—issued to no one in particular.

Thirty days. How generous. As though geography were the only obstacle.

Orestis folded the letter and slipped it back into the envelope.

He set it aside with the rest of his correspondence. He would forward it to the Consortium and let them deal with it. That, after all, was why he had made the arrangement in the first place.

Let bureaucracy fight bureaucracy.

***

Alke was already at her desk when Orestis arrived the next morning. She looked up as he stopped, expression brightening slightly.

“Morning,” she said. “You’re early.”

“Brief matter.” He set the envelope on her desk. “I received this yesterday.”

She unfolded the letter with practised ease. Her eyes moved quickly over the text. There was no visible reaction.

“Ah,” she said, mild and untroubled. “That.”

Orestis waited.

Alke refolded the notice and set it aside, not returning it to him. “You don’t need to do anything about this.”

“I assumed as much. I only wanted to confirm whether it required tracking.”

“No,” she said, smiling. “It won’t come up again.”

That was fast. And that was certain.

He inclined his head. “Understood.”

She was already reaching for the next document. “Anything else while you’re here?”

“No. That was it.”

“Good,” Alke replied cheerfully. “I’ll mark it as resolved.”

He left her to her work. The letter remained where she had placed it, face down among several others, indistinguishable from the rest.