The visit had been pleasant.

  Even the part where his mother cornered Eirene in the kitchen to ask about her favourite desserts—which was not, Orestis was certain, innocent curiosity. Avra Stathis did not collect dessert preferences without strategic intent. Somewhere in the back of her mind, a hypothetical menu was being constructed for a hypothetical occasion that she would deny planning if asked directly.

  She’s going to start embroidering tablecloths. I give it two weeks.

  Still. It had been good. His father was in solid health, business was running smoothly, and the house remained exactly as he remembered it. Which was, depending on the perspective, either comforting or slightly unsettling.

  The food his mother had packed sat neatly on the table between them—wrapped, labelled, and portioned with an efficiency that suggested she had started preparing it well before they arrived. Two separate bundles. One for him. One for Eirene. Each with a handwritten note tucked beneath the twine.

  She made one for Eirene. A separate, personalised bundle. We have crossed a point from which there is no return.

  “Your mother is very kind,” Eirene said, reading hers.

  “She is building a case,” Orestis replied.

  Eirene smiled but did not argue. Which, he noted, was not the same as disagreeing.

  He set his mother’s food aside and turned to the matter he had been thinking about since the letter.

  “The call-nodes,” he said.

  Eirene looked up.

  “My mother’s suggestion. A pair for you and your mother.”

  “You said you’d look into it.”

  “I have.” He paused. “The problem isn’t building them. It’s what happens after.”

  He laid it out. The call-nodes his parents used worked because of where they were. Theramon was small, rural, and had no one with the technical knowledge to question a communication device’s range. His parents talked to their son in Orthessa, and if anyone noticed—which they wouldn’t—they’d assume the device was high-end. Plausible enough for a merchant household.

  Axiomera was different. Call-nodes existed there in meaningful numbers. People who understood range limitations lived there—enchanters, trade mages, Consortium-adjacent specialists. A device appearing in the Aretaios household that could communicate with Orthessa at unlimited range would attract exactly the kind of attention Eirene’s family could not afford.

  “The design itself isn’t the risk,” he said. “If someone opened it up, they’d find principles that are ahead of the market but not recognisably impossible. The issue is context. A device with that range, in that household, in that city—it becomes a question someone might ask.”

  There was no need to even mention the war preparations. It would draw Kallistrate’s interest immediately—and not quietly.

  Eirene nodded. She had already worked through most of this. He could see it in the way she was waiting for the solution rather than the problem.

  “My current design bypasses signal degradation through a branch of dimensionalism that no one is actively researching. It would take years before anyone in the Consortium could replicate the approach—the theoretical groundwork hasn’t been laid yet.” He paused. “Which makes it safe for Theramon, where no one would ever examine it closely. But in Axiomera, even the existence of an unexplained device draws scrutiny.”

  “So we need a different approach.”

  “We need the approach to not matter,” he clarified. “If the technology is standard—if unlimited range becomes the norm—then no one questions any individual device. A pair of call-nodes in your family’s home isn’t an anomaly. It’s a purchase.”

  He let that settle.

  “If it becomes common, it becomes unremarkable,” she said.

  “Exactly. Standards are safer than brilliance.”

  He’d been turning the solution over since Theramon, refining the concept while his mother talked about weather and his father reviewed shipping manifests.

  “The core idea is straightforward,” he said. “Current call-nodes use sympathetic resonance. The range limitation exists because the resonance signal degrades over distance. Everyone working on the problem is trying to extend the range—push the signal further, reduce degradation. They’re solving the wrong problem.”

  “You want to eliminate the distance instead.”

  He nodded. “Open a gateway inside one half of the call-node, with the exit anchored to the other half. The two halves become spatially adjacent regardless of physical separation. The resonance link doesn’t need to carry over hundreds of kilometres—it only needs to carry across the width of the gateway.”

  Eirene’s expression sharpened. “You’re not changing how the call-node works. You’re changing where it works.”

  “The communication mechanism stays exactly the same. Sympathetic resonance, standard principles. The only addition is a gateway that reduces the effective distance to zero.”

  “Gateways require Third Circle mana. At minimum.”

  “It does. Which is the constraint that makes it interesting, because ambient mana is nowhere near that density. You’d need to concentrate it—gather diffuse mana and compress it to Third Circle quality using a formation built into the device itself.”

  Eirene worked through the process out loud. “The formation gathers ambient mana. Compresses it. Opens the gateway. The gateway stays open until the concentrated mana is depleted, then closes. The formation begins gathering again.”

  Orestis inclined his head. “The mana storage units would need to be modified to concentrate ambient mana first. An additional formation would open a gate, eliminating the need for the range-extension formation.”

  “In other words, nothing is being added in net terms—one modified, one removed, one added. The size of the device would remain the same. In theory.”

  She had reached the root of the matter.

  “Both spells were designed for scale—gateways are meant to be large enough to walk through, and concentration formations are meant to cover wide areas to gather more ambient mana. No one has tried to miniaturise either, because there’s been no reason to.”

  “Until now.”

  “Until someone asks the right question. Miniaturising both formations to fit inside a palm-sized shell—that’s the real engineering challenge; the kind the Consortium is built for.”

  She nodded, understanding. “You’re not going to build it.”

  “If I build it, I’m the source. Every question about the design leads back to me. If the Consortium develops it, it’s institutional innovation. Routine progress. And once it enters the market—commercially licensed, widely available—a pair of call-nodes in any household, anywhere, is just a household item.”

  Eirene was quiet for a moment, assembling the full picture. “You’re describing months of development.”

  “At least,” he conceded. “The theory is derivable from existing work, but the engineering is genuinely difficult. The gateway needs to be compressed to a fraction of its standard size while maintaining structural integrity. The concentration formation needs to work in a space orders of magnitude smaller than its intended operating area, which means gathering far less ambient mana per cycle, which means longer recharge times. Prototypes. Testing cycles. Material sourcing. Iterative refinement. It’s real work.”

  This novel's true home is a different platform. Support the author by finding it there.

  “And you want me to bring the idea to them,” she stated, grasping his intention.

  “I want you to bring the concept. Not the solution—the problem.” He laid out the outline. “You’ve been studying communication enchantment theory. You’ve seen the range limitations. You’ve identified the theoretical bottleneck. You have a suggestion for an alternative approach.”

  “A suggestion any sufficiently motivated researcher could arrive at independently, given the right framing.” She considered it. “It’s a good idea.”

  It should be. I did not arrive at it accidentally.

  “There are three people in the Consortium’s Applied Enchantments division who could develop this,” he said. “Maren Hale—she runs the communication systems research group. Methodical, thorough, unlikely to ask how a merchant’s daughter arrived at a novel theoretical framework without showing her work.”

  “And the other two?”

  “A tall woman with short grey hair who works two doors down from Hale. She’s a formation specialist—the miniaturisation problem is her domain. I’ve seen her notation; she’s good,” he said. “The other is a younger man. Dark complexion, round spectacles. Always has ink stains on his left sleeve. He handles the theoretical side—spatial binding, coordinate-independent anchoring. He’d recognise the gateway concept immediately.”

  She gave him a flat look. “You’ve worked in the same building for months, and you don’t know their names?”

  “I’ve worked in a different wing for months. I know Hale by name because she submitted a review request to Systems Continuity last quarter. The other two I’ve only seen in passing.”

  “You remembered the ink stains on his sleeve but not his name.”

  “The ink stains tell me he’s left-handed and works late,” he pointed out. “His name would tell me what his parents thought sounded distinguished.”

  Eirene shook her head, but the exasperation carried warmth. “I’ll find them. You’ve given me enough to work with.” Then she paused, looked at him steadily. “Thank you. For thinking about this.”

  Orestis waved it off. “My mother asked.”

  “She asked you to make one. You redesigned the technology so it wouldn’t bring attention down on anyone who used it. That’s not what she asked.”

  No. It isn’t.

  “It’s the better solution,” he said.

  “It always is, with you.” She paused. “And once it’s developed? How long before it reaches the market?”

  “After the prototyping phase—months. The Consortium would license it commercially. Mass production would follow. At that point, people would assume your family purchased a pair from the first available batch. Unremarkable.”

  She was quiet for a moment.

  “My mother would like that,” she said, and her voice was softer than before.

  He did not reply. Some things didn’t need a response.

  ***

  The case file was waiting on his desk when he arrived at the Consortium that afternoon.

  This was not, in itself, unusual. Case files appeared regularly—routed through Systems Continuity’s intake process, stamped, catalogued, and distributed according to availability and expertise. Orestis had handled dozens since his arrival. Site audits, infrastructure reviews, integration assessments. Routine work, competently assigned.

  This one was different.

  He noticed the routing first. Standard case files arrived through the general queue—assigned by a clerk based on workload distribution. This one had been flagged with a departmental referral code. Someone upstream had specifically requested him for a cross-departmental issue.

  The file itself was slim. Two systems—a ward array governing a storage facility in the eastern district and a transport relay serving the same area—had begun producing correlated anomalies. Individually, each system reported within tolerance. Jointly, their outputs suggested an interaction that neither had been designed to produce.

  Two systems sharing the same space and never designed to speak. Where have I seen this before?

  The parallel to the suppression site was obvious.

  He read through the technical summary. The ward array was recent—installed within the last two years as part of a district expansion. The transport relay was older, predating the expansion by at least a decade. Neither system’s documentation referenced the other. Their maintenance schedules were handled by different teams, reviewed by different auditors, and funded through different allocations.

  No one had examined the interface because, on paper, no interface existed.

  The problem lives in the gap. As always.

  He turned to the referral notes. The requesting department had included a single line of justification: Anomaly consistent with cross-system interaction. Consultation requested: Orestis Stathis.

  No ambiguity. No general referral. Just his name.

  But the routing code was executive-level authorisation. Someone at the Directorate had signed off on this referral, which was unusual for what presented as a minor anomaly. Cross-system ward interactions were common enough that most were resolved through standard channels without escalating beyond the maintenance teams involved.

  Unless someone had decided that the pattern warranted closer attention. Not the anomaly itself—the type of anomaly. The kind that required someone who thought about systems in terms of how they failed together rather than individually.

  Orestis noted the authorisation level, assessed the implications, and then set the thought aside.

  Thinking about why they sent it to me is less productive than actually solving it.

  He gathered the file, requisitioned access to both systems’ maintenance records, and left for the eastern district.

  ***

  The work took longer than necessary—not because it was hard, but because the documentation was terrible. The ward array’s installation records had been filed under the district expansion project rather than the city’s central ward registry. The transport relay’s maintenance logs existed in two versions that did not agree with each other on three separate dates.

  Orestis spent the first hour reconciling records before he could begin examining the actual systems.

  If the Consortium ever wants to improve overall performance by ten percent overnight, they could start by standardising their filing conventions.

  The interaction, once he found it, was straightforward. The ward array’s refresh cycle coincided with the transport relay’s signal recalibration window. During the overlap—approximately forty seconds every six hours—both systems drew from the same ambient mana pool simultaneously. The draw was small enough that neither system registered strain. But the shared draw created a brief harmonic in the local mana field that the transport relay interpreted as signal noise.

  The relay compensated by amplifying its next cycle. The ward array, detecting the amplified signal as environmental interference, tightened its next refresh. Each system’s correction fed the other’s compensation, producing a slow oscillation that was invisible to individual monitoring but measurable when both datasets were overlaid.

  Not dangerous. Not even particularly urgent. But left unchecked, the oscillation would widen until one system started reporting actual errors—at which point, two separate maintenance teams would each conclude the problem was in their system, and spend weeks chasing a fault that existed in neither.

  He mapped the interaction, documented the feedback loop, and proposed a correction: offset the refresh cycle by twelve seconds. The overlap would be eliminated, the harmonic would dissipate, and neither system would require modification.

  Clean. Minimal. No one would notice it had been done.

  He filed the report, initialled the verification, and returned the case file to intake with a recommendation for a follow-up check in thirty days.

  On his way out, he paused at the corridor junction near the Applied Enchantments wing. Through an open door, he could hear the muffled sounds of a discussion in progress—spell formations, by the fragments that reached him. A woman’s voice, precise and unhurried, was walking through a derivation.

  Hale, probably. Good. She’s in today.

  He continued past without stopping. This was Eirene’s conversation, not his.

  ***

  “How was work?” Eirene asked that evening.

  They were in her room. The food from Theramon was spread between them—his mother’s cooking, reheated with a minor thermal enchantment that Eirene had cast without being asked.

  “Interesting,” he said. “Two systems interfering with each other. Neither knew the other existed.”

  “Did you fix it?”

  “I offset a timing cycle by twelve seconds.”

  She considered that. “All of that for twelve seconds?”

  “The twelve seconds were the solution. The four hours were finding out which twelve seconds.” He paused, then added, “The case was routed oddly. Executive-level authorisation on the referral code.”

  Eirene looked up from the food. “For a timing offset?”

  “For the type of problem. Cross-system interaction, interdepartmental scope. It’s a reasonable referral on its own. The authorisation level is what doesn’t fit.”

  She studied him. “You’re concerned.”

  “I’m noting a pattern. The suppression site drew institutional attention. The follow-up was handled quietly, and no one said anything directly. But the type of work being sent my way has shifted. The cases are more specific. More precisely targeted.”

  “Meaning they’re not assigning you whatever’s available. They’re assigning you what they think you’re suited for.”

  “Which implies someone made that assessment. And that the assessment was specific enough to generate a routing preference.”

  Eirene was quiet for a moment. “Is it dangerous?”

  “No. It’s institutional efficiency. They found someone who solves a particular type of problem, and they’re directing that type of problem toward him. It’s rational. It’s also exactly how the Consortium consolidates dependency without announcing it.”

  “And you’d rather not be depended on.”

  “I’d rather the dependency remain at a level where my absence creates inconvenience, not crisis.” He reached for a wrapped pastry.

  His mother had included a note inside the wrapping: Make sure you share with Eirene. As though he wouldn’t. As though Eirene’s separate, personalised bundle was insufficient evidence of his mother’s priorities.

  “I’ll pay attention,” he said. “If the pattern deepens, I’ll adjust.”

  “You already see it,” she said mildly. “You’re deciding how much to care.”

  That was uncomfortably accurate. He set the pastry down and looked at her. “I’ll be careful.”

  “I know.” She held his gaze for a moment, then reached for the other bundle. “Now. Your mother included a note in mine that says—and I’m quoting—‘tell him to eat the soup before it goes cold.’ She underlined ‘before.’”

  Orestis looked at the wrapped container he had designated for later consumption.

  “It isn’t cold yet,” he said.

  “She underlined it twice, Orestis.”

  He ate the soup. It was good. Just not as good as the pastries. Perhaps he should start with the soup next time—save the best for last. He would eat it all anyway.

  Patreon, along with extra lore and author notes.