Cherreads

Chapter 38 - CHAPTER 38: THE EASTERN DISTRICT DISPUTE

CHAPTER 38: THE EASTERN DISTRICT DISPUTE

The crack in the foundation ran from one corner of the warehouse wall to the other.

I stood in the construction zone beside Kaido, watching orc and dwarf workers shout at each other across the rubble of what had been the first hybrid-technique building in Tempest. The wall hadn't just failed—it had collapsed spectacularly, taking a section of roof with it and scattering materials across half the site.

"Orc reinforcement methods are adequate for simple structures," the dwarf team leader was saying, his voice carrying the condescension of someone whose people had built mountains into fortresses. "But they cannot support the load-bearing requirements of proper architecture."

"Dwarven mortar ratios are designed for stone, not composite materials," the orc construction chief shot back. "You insisted on using your specifications without adapting them to our methods."

"Your methods are—"

"My methods built the eastern district while your people were still negotiating trade terms."

The argument had been building for twenty minutes. Rigurd had summoned me because "you started this hybrid approach"—a characterization that wasn't entirely accurate but wasn't entirely wrong either. The corridor dispute I'd mediated during the Dwargon delegation's arrival had led to the collaborative construction project. The collaborative construction project had led to this warehouse. The warehouse had led to a wall collapse that threatened to reignite tensions between species that had only recently learned to work together.

Butterfly effects. Again.

"The failure investigation can wait," I said, stepping between the arguing leaders. "Right now, this site is unsafe and the argument is making it worse."

"The investigation cannot wait," the dwarf leader insisted. "Responsibility must be assigned—"

"Responsibility can be assigned after we understand what actually happened. Blaming each other based on assumptions will only—"

"The assumptions are obvious. Orc construction methods—"

"Were approved by your engineering consultant three weeks ago." I pulled the documentation from memory—Kaido had shown me the approval forms during our logistics coordination. "You signed off on the hybrid approach. Both of you did."

The silence that followed was uncomfortable.

"The real question," I continued, "is why the wall failed when the method was approved by both teams. That suggests the problem isn't the method—it's something specific to this application."

The orc chief's expression shifted from defensive to thoughtful.

"The mortar ratios," he said slowly. "We adapted them for the composite materials, but the dwarven specifications assume mineral consistency that doesn't exist in our sourcing."

The dwarf leader frowned. "You modified the ratios?"

"To match our materials. The original specifications called for mountain-quarried stone. We're using river-deposited aggregate."

"That would change the binding properties. The load calculations would be—"

"Wrong," I finished. "Not because either method is inferior. Because the specifications weren't adapted for the actual materials being used."

The argument deflated.

Both leaders stared at the cracked foundation with new eyes—not looking for blame, but looking for technical understanding.

I used the opening.

"Rebuild the wall together," I said. "Both teams, working on the same section. Test the mortar ratios on small samples before scaling up. Document what works and what doesn't. Make this failure a learning opportunity instead of a grievance."

The orc chief exchanged glances with the dwarf leader.

"That would require cooperation."

"You've been cooperating for three weeks. One failure doesn't erase that. Unless you let it."

The dwarf leader stroked his beard—a gesture I'd learned to read as thoughtful consideration rather than dismissal.

"The orc is right about the material adaptation," he admitted reluctantly. "Mountain specifications don't translate directly to river aggregate. I should have caught that during review."

The orc chief's posture relaxed slightly.

"And the load calculations need dwarven precision. Our methods work for weight distribution, not structural engineering."

It was the closest either of them would come to apologizing.

I took the opportunity to reach for the CSN dashboard.

[Link Initiation — Target: Orc Chief Grakk — Compatibility: 34%]

Low compatibility, but I wasn't trying to form a lasting bond. I needed thirty seconds of connection to share one specific effect.

The link formed.

Warmth spread through my chest—fainter than with Gobta or Mira, the low compatibility limiting the emotional resonance. But I could feel Grakk's frustration, his shame at the failure, his defensive anger masking deeper uncertainty about whether the orc contingent truly belonged in Tempest's construction hierarchy.

I pushed through the link.

[Perk Activation: Comfort Pulse]

The calming effect flowed from me into Grakk—a gentle reduction of emotional intensity that didn't eliminate his feelings but softened their edges. His shoulders dropped slightly. His jaw unclenched.

The link collapsed after twenty-two seconds, strain building faster than expected due to the low compatibility.

But the effect held.

Grakk turned to the dwarf leader with less hostility than he'd shown moments before.

"Joint reconstruction," he said. "Your engineering, our labor. We test everything before scaling."

The dwarf leader nodded.

"Agreed. And the documentation becomes standard protocol for future hybrid projects."

They shook hands over fresh rubble.

I walked back to the administrative district with Kaido, the system notifications appearing in my peripheral vision.

[Achievement: Diplomatic Shadows — Cross-species construction dispute resolved. Infrastructure butterfly generated.]

[+220 SysXP | +12 CR | +8 SC | +4 CA]

[Level Up: 21 → 22. +3 SP.]

Level 22. The achievement had pushed me over the threshold I'd been approaching for days. But the "Infrastructure butterfly generated" notation caught my attention.

The system was tracking consequences I couldn't see.

"Good work back there," Kaido said. "I thought that argument was going to end with someone in the healer's quarters."

"It almost did. The underlying tension is real—old grievances from before Tempest existed. One wall collapse isn't going to fix that."

"But it won't make it worse now." He paused at a street corner. "Benimaru was going to assign military oversight to the eastern construction zone if the dispute escalated. Standing patrols, conflict monitors, the whole security apparatus."

"And now?"

"Now the resolution means we don't need military presence. Those patrol units get redeployed somewhere else." He shrugged. "Probably the outer perimeter. Eastern border's been understaffed since the expansion."

The information landed with weight I couldn't explain to Kaido.

Patrol redeployment. Military resources freed from one location and sent to another. The kind of logistical cascade that seemed minor but could matter enormously when circumstances changed.

I thought about Gobta's patrol route, shifted west-to-east after the first corridor dispute. About the construction project I'd inadvertently launched by asking a single question about hybrid foundations. About the wall that had collapsed and the argument that had almost escalated and the Comfort Pulse I'd used to lower the temperature enough for reconciliation.

Each decision created ripples. Each ripple touched decisions I couldn't see.

The butterfly map in my quarters was getting crowded.

That evening, I added another line to the diagram.

Dispute resolved → Military oversight removed → Patrol units freed → Redeployed to...?

The question mark stayed empty.

Somewhere in Tempest's administrative building, Benimaru was signing orders that would move people and resources based on decisions I'd influenced. The specifics were invisible to me—which units, which routes, which schedules—but the cascade was real.

I stared at the map until my eyes ached.

"I keep changing things without knowing what I'm changing. The original timeline is getting harder to predict. If Falmuth attacks when the source material says they will, I won't know if the defenses are stronger or weaker because of what I've done."

The thought was uncomfortable.

I'd been operating on the assumption that my butterflies were mostly positive—cultural preservation, cross-species cooperation, food that strengthened the community. But military deployment wasn't something I could evaluate. Patrol routes weren't my area of expertise.

For the first time since arriving in Tempest, I wondered if I was making things worse without knowing it.

Want more? The story continues on Patreon!

If you can't wait for the weekly release, you can grab +10, +15, or +20 chapters ahead of time on my Patreon page. Your support helps me keep this System running!

Read ahead here: [ patreon.com/system_enjoyer ]

we just added free chapters on unwrittenrealm.com — plus the whole novel is translated into 14 languages. read it in your language for free.

More Chapters