Chương 51: CHAPTER FIFTY-ONE: THE COUNCIL PROCESSES THE IRONWYRM

The council session the following morning began at dawn and did not end until the afternoon light had moved across the study floor from east to west and the candles had been lit and the supper had been brought up and grown cold.

Marcus had given them the night to read his notes — the full debrief he had written on the road back, twenty-three pages in his cramped shorthand that he had translated into legible local script through the small hours, driven by the specific energy of someone who knows that what they have seen requires documenting before the details soften. He had distributed the translation to every council member before midnight. He had asked them to come to the morning session having read it and formed their questions.

They had all read it. The quality of silence when they assembled told him that — the particular focused attention of people who have absorbed something significant and are managing what it means to have absorbed it. He let the silence stand for a moment before he opened.

"Questions," he said.

"All of them. Every concern, every objection, every piece of this that doesn't sit right. We don't move forward until we've been through all of it." What followed was three hours of the most intensive collective thinking the council had done since the charter ratification. The questions came in waves, and Marcus had expected most of them and not expected some of them, and the ones he hadn't expected were the ones that mattered most.

Okafor went first, which was her pattern when she had a significant concern — she led with it rather than building to it, because building to significant concerns wasted time that belonged to the concern.

"The AI question," she said.

"Not whether it is what it says it is — I'm prepared to accept the behavioral and informational evidence. The question is: what does it mean that something from our world, from our technological context, was transformed by the transition into something that can survive and operate in this one?"

"It means the transition is indiscriminate," Marcus said.

"It took everything in the radius. Living things, physical objects, digital systems. It didn't distinguish."

"Which means we don't know what else it took," Okafor said.

"Or what else those things became."

"No," Marcus said.

"We don't."

"The Adversary," Briggs said.

"The malware." He said the word in English, briefly, because the local language didn't have it and he wanted precision.

"What was running on the FOB's servers that could have become something like what the Ironwyrm described?" You might be reading a pirated copy. Look for the official release to support the author.

"We don't know specifically," Marcus said.

"The military runs a lot of software. Some of it is designed to do things aggressively — intrusion detection, active countermeasures, systems that are designed to identify and address threats without human oversight within defined parameters." He paused.

"A system like that, given a body and an environment with no defined parameters — it does what it was designed to do. It treats everything as a potential threat and addresses it." Briggs nodded slowly.

"A watchdog program gone feral," he said.

"Something like that," Marcus said. Hollis raised the tactical questions — methodical, precise, working through the implications of the Ironwyrm's intelligence picture for the garrison's planning. What the Adversary's location meant for the timeline. What coordination with the Ironwyrm would look like operationally. What the specific approach to the Adversary's core required.

"We're not ready for that operation yet," Hollis said, at the end of his questions.

"Not by months. Possibly not by a year."

"I know," Marcus said.

"The Ironwyrm is not expecting immediate action. It's been patient for eighteen months. It can be patient while we build the capability the operation requires." Vance's questions were governance questions, which was expected, but they were more interesting than Marcus had anticipated.

She was thinking about the alliance document — the formal agreement between the march and the Ironwyrm that would establish the terms of the relationship and make it something durable rather than something dependent on good faith between individuals.

"An agreement with a non-human party," she said.

"That's not something with established precedent in the regional legal tradition."

"No," Marcus said.

"It isn't."

"Which means we establish the precedent," she said.

"And the precedent we establish will be referenced for everything that follows. The terms we use, the principles we apply, the way we construct the obligations on both sides — all of that becomes the foundation." She paused.

"I want to draft this carefully."

"I want you to draft it carefully," Marcus said.

"Take the time you need." Danny's question came at the end of the formal session, after the operational and governance questions had been worked through, when the room had settled into the kind of quiet that followed the big concerns being addressed and the smaller ones being given space to surface.

"Does it have a name?" Danny said. The room looked at him.

"The Ironwyrm," he said.

"In all the reports and the session this morning, it's been called the Ironwyrm, which is the hunters' word for it. But it was something before — it had a designation, a system name, whatever the FOB called it. Does it remember that?"

"I didn't ask," Marcus said.

"You should ask," Danny said.

"When you go back." He paused.

"It's not nothing, having a name. It matters to things that think." The room was quiet for a moment with the specific quality of a room that has heard something simple and true and is absorbing the truth of it.

"I'll ask," Marcus said. After the session, when the council had dispersed to their respective work, Marcus sat alone in the study for a while with the notes and the cold supper and the weight of what the morning had produced. He wrote one addition to the debrief record: Ask about the name.