Building a Kingdom as a Kobold-Chapter 79: I File Reports. Not Warnings. Until Today

I didn’t plan on escalating anything today.

My job’s mostly routine. I process field reports—scout returns, civic updates, some minor resource metrics. I’m not a hero. I’m not frontline. I haven’t drawn a blade in six years.

But today’s paperwork didn’t sit right.

It started with a delay. One of our scouts hadn’t checked in on time. Standard protocol says you wait forty-eight hours before raising a flag, and this one was only at thirty-six. So I logged it, marked it for passive pingback, and moved on.

Except the last message they sent caught my eye.

"Collapsed village. Uneven ground. Signal echo from below. Might be a dead node. Investigating."

That’s not unusual, in itself. Terrain shifts happen. But the phrasing stuck with me—"signal echo." That’s not something a scout would write lightly. They’re trained not to over-speculate. I flagged the message in their log, mostly so I wouldn’t forget it, and got back to clearing out my queue.

That’s when the second thread showed up.

A routine civic compliance form, submitted from a small relay outpost near the same region, listed a festival held two nights ago. Normally, we don’t track local customs unless they affect trade routes or mana usage. But this one had a few terms that weren’t local.

"Sovereign Blessing Ceremony. Meal offerings timed. Flamephrase repeated according to Article One."

Article One?

We don’t number their customs.

I pulled the form back up. Scanned it again. There it was.

"Sovereign Flame Code, Article One: First We Cook."

I frowned. That line—I’d seen it before. But not in any formal documentation. I opened a backlogged archive of Ashring material—compiled post-recognition, after the siege. I had to dig for it. Some of their language gets messy.

Eventually, I found it: a scout transcript from some time ago, marked low priority. It was a recording from Ashring’s cooking ward some days after the Sovereign returned.

She’d said, offhand, "First thing we do is cook. Second, we breathe. Third, we keep breathing. Then maybe someone builds a roof."

It wasn’t formal. She wasn’t addressing anyone directly. The file had even been labeled "emotive debris – not a declaration." It read like stress relief.

Now it was being cited as Article One of a flame code.

I copied the phrase into a query line and searched for duplicates. Got three.

All within the last two weeks. Different regions. Different authors.

They were treating it like it was a tradition.

I paused, leaned back in my chair, and let the rain hit the shutters for a few seconds. Thought about ignoring it. Thought about telling myself it was just cultural bleed. That happens sometimes. One settlement does something interesting and nearby towns pick it up. Especially if there’s food involved.

But the phrasing wasn’t changing. It was identical.

I sent a low-priority ping to one of our trade monitors, flagged the merchant lists for the region. While I waited, I opened the latest outpost update from farther west.

Another mention. Another meal. Another fire.

They’d drawn the Ashring symbol over their market tents. Not painted—stamped and molded.

I’ve seen that design a hundred times. I helped approve its original visual archive when Ashring was declared stable. This one was... almost the same. But someone had curved the base lines. Just a little. Enough to pass at a glance. But not enough to mistake it if you knew what the real one looked like.

I sent a follow-up to the trade monitor. Asked for clarification.

Got a brief reply:

"Trade permitted under regional license. Source contract sealed."

That shouldn’t have happened.

We don’t seal contract data on minor exports. And there’s no reason a settlement like Ashring would be issuing secondary distribution rights, let alone sealed ones.

I leaned forward. Pulled open the region map. Marked every report containing the phrase "Sovereign Blessing" or "Flame Code." Five markers, stretching in an arc around a zone we already had under mild observation—low-magic density, minimal conflict. One abandoned village in the center.

I checked the scout again. Still missing. No signal. No ping.

I opened his last two logs. He’d found something under that village. Said the air smelled wrong. Said the heat signature didn’t make sense. Thought maybe there was a failed structure buried beneath the surface.

Then nothing.

I copied the location, added a new file to my desk log: "Civic Spread Pattern – Possible Fabrication." Marked it internal only.

I didn’t have anything solid yet. Just small shifts. Phrases pulled out of context. Symbols altered just enough to pass.

But they were all pointing in the same direction.

I glanced at the window. Down in the courtyard, a traveling vendor was setting up a charm rack. Little fire-shaped pendants. Cheap alloy. Surface-smelted.

He waved up at my window when he noticed me.

I waved back. Then paused.

His charms weren’t generic.

They were shaped like the Ashring flame.

Except the center line was gone. Cleaned out. The whole thing smoothed to a single loop.

I didn’t wave again.

I went back to my desk.

And started drafting the escalation request.

The escalation draft sat on my desk for half an hour before I finalized it.

I didn’t want to overreach. We’ve had false pattern alarms before. Coincidences get flagged, people panic, and then it turns out a phrase just made its way through a merchant chain because someone thought it sounded nice.

But that’s not what this felt like.

Someone was turning casual speech into civic order. Fragments into ceremony. And they weren’t attributing it back to Ashring—not directly. It was being rounded off, made general. Almost anonymous.

That’s what bothered me most.

Ashring never asked for recognition. Their flameprint wasn’t designed for replication. They didn’t file ritual templates. They didn’t send out priests or binders or policy envoys. They just existed. Barely. And now their fragments were showing up hundreds of miles away with formal headers and contract seals.

Distributed and claimed.

I needed someone who could track the movement on the ground.

Someone who’d been there before and wouldn’t mistake what they were seeing.

There weren’t many who qualified. Just one, really.

I walked down two levels to the assignment floor. Found the lead roster. Filed a request under Class-3 Discretional Observation: Cultural Replication Risk.

The clerk at the desk glanced at me. "Which region?"

"Western trail arc. Near Moss Hollow."

He frowned. "We have scouts down there."

"Not responding."

His fingers slowed on the ledger. "Is this a containment issue?"

"Not yet."

"Is this Ashring?"

I didn’t answer right away.

"It’s not Ashring," I said. "But it’s of similar shape."

That was enough.

The form cleared. It went up the chain.

They wouldn’t assign anyone unless it got past third review.

So I waited.

Took the rest of the reports back to my office. Started writing the memo I hoped I wouldn’t have to finish. I only got three lines in before someone knocked.

Not a runner. Not a page.

It was him.

The Hero.

I don’t know what name he’s using this week. The titles change. The badges shift. But everyone in the Guild knows who he is. The one who didn’t break the dungeon. The one who stopped.

He didn’t smile when he entered. He rarely does.

"Got a notice," he said. "Said I’d want to see it."

I passed him the file.

He read quickly. Page by page, no reaction. Until the last one.

"The spiral," he said. "Have they replicated it?"

"Not exactly. Not yet. But they’ve got pieces. Symbols. Speech."

He tapped the edge of the last report. "This part. The merchant trail."

"Sealed contracts," I said. "They’re moving artifacts. Low-value, but symbolic. All bearing modified marks. They’re calling them ’commemorative.’"

"Distribution pattern?"

"Arcing toward the river zones. Not touching Guild-certified regions yet, but close."

He handed the file back. "Someone’s trying to set a civic baseline."

That’s what I was afraid of.

"If they get enough ground-level confirmation," I said, "it could formalize before we have a response."

He nodded.

"Assign me," he said.

"You sure?"

He nodded again.

I filed the order.

Updated the status.

And waited.

The source of this c𝓸ntent is fr(e)𝒆novelkiss