Aelith talked while they rode. Not voluntarily — Varren extracted it, question by question, the professor's method of turning conversation into an interview so gradually that the subject didn't notice the transition from casual exchange to systematic debriefing.
"The Compact has held chapters Four, Five, Six, and Seven for nine years," Aelith said. They were in a wider valley now, the terrain allowing them to ride three abreast, the pace steady. "Four bearers at any given time, though the specific bearers have rotated as integration claims them. Ryn is the third Fifth Chapter bearer. The previous two lasted fourteen months and eleven months respectively."
"Integration rates," Varren said. "The Fifth Chapter has a faster progression than the others?"
"Significantly. The memory function draws on the bearer's own memory architecture — the chapter uses the bearer's neural pathways as a substrate for the system's memory storage. The more the chapter stores, the more of the bearer's own memory it displaces." Aelith's voice remained clinical. The distance of someone who had watched this happen to colleagues and who had calibrated her emotional response to be functional rather than absent. "Ryn's personal memories began degrading at month eight. By month fourteen, she was losing days. Not forgetting what happened — the days simply weren't being recorded. The Fifth Chapter was allocating all available memory capacity to system data."
"She's losing herself," Sera said quietly.
"She's losing her history. The person she is in the present moment is intact — personality, decision-making, emotional responses, all functional. But she can't remember last Tuesday. She can't remember bonding the chapter, most days. She wakes up and the Fifth Chapter provides her with a summary of her situation, and she operates from the summary rather than from memory." Aelith looked at the road ahead. "On good days she remembers her village. On bad days the village is data she's been told about."
Valen listened. The Grimoire's channels in his left hand were conducting the conversation's emotional weight the way they conducted everything — as information, data points in the ongoing integration process. He could feel the resonance of another chapter's description. The Fifth Chapter's cost structure was different from the First Chapter's — memory-specific rather than memory-random — but the mechanism was the same. The chapters consumed their bearers. Different chapters, different flavors of consumption. Same end.
"The Fourth Chapter," he said. "Your chapter. What's its cost?"
Aelith looked at him. Measuring how much to share. "Processing overload," she said. "The Fourth Chapter's pattern recognition is continuous. It doesn't stop. Every system I encounter — a trade network, a military logistics chain, a weather pattern, the social dynamics of a room full of people — the chapter breaks it down into component patterns and presents the analysis simultaneously."
"You see patterns in everything."
"I see patterns in everything, all the time, without the ability to stop seeing them." She held up her right hand. A fine tremor, barely visible. "The cognitive load produces neurological overflow. My hands shake. My sleep is interrupted by processing runs that the chapter initiates without my input. On bad days, the pattern recognition extends to my own thoughts and I become aware of the patterns in my own cognition, which produces a recursive loop that—" She stopped. Lowered the hand. "The cost is clarity at the expense of peace. I see everything and can't stop seeing it."
Varren was taking notes. The professor's response to another data point in the chapter-bearer relationship model she was building. "And the cost escalates with integration?"
"My integration is at forty-three percent. At current progression, I have approximately four years of functional capacity. The tremor will spread. The processing overload will increase. Eventually, the Fourth Chapter's pattern recognition will consume enough cognitive bandwidth that my own thoughts can't maintain coherence." She looked at her hands. "I become a processing node. A human-shaped analysis engine running the Fourth Chapter's function without a person inside."
Nobody spoke. Hooves on packed earth. Wind across the valley.
"I'm sorry," Neve said.
Something cracked in Aelith's composure. Just a flicker. "Thank you."
---
The Fourth Chapter's practical capabilities became evident that afternoon.
They'd been riding for six hours when Aelith pulled up beside Valen and said, "Mordren's tracking network is intersecting our route."
"How do you know that?"
"The Fourth Chapter." She gestured vaguely at the terrain around them. "The Inquisition uses a standard distributed tracking methodology — relay runners, message drops, regional agents who report sightings to a central coordination point. The methodology has a pattern. I can read the pattern from the residual traces — the message drops leave informational signatures, the relay routes create flow patterns in the regional communication network, the coordination responses produce timing correlations."
"You can see their tracking system."
"I can see any system. Mordren's tracking network is a system. A well-designed one — the coverage pattern is thorough, the relay intervals are efficient, the coordination response time is approximately six hours from sighting to deployment." She looked at the ridge to their east. "The last sighting report was filed from a posting station twelve miles southeast of here, nine hours ago. A relay runner carried it northeast to the provincial coordination node. The deployment response will reach the hillcountry approach routes within—" She calculated, the Fourth Chapter's processing running behind her eyes. "Four hours."
"Four hours."
"Mordren has two advance teams operating in the hillcountry. Three operatives each, standard Inquisition field configuration. They're running a convergence pattern — not trying to intercept directly, but narrowing the corridor of available routes until we're channeled into a predictable trajectory." She traced the pattern in the air with one hand, the tremor visible. "From their perspective, we're moving northwest through a valley system that has limited exit options. They don't need to catch us. They need to predict where we'll be in twelve hours and position blocking forces at the valley exits."
Ren had been listening. His skepticism had given way to something closer to professional respect. "You can see all that. From here."
"The Fourth Chapter reads systems. The Inquisition's tracking methodology is a system."
"Can you see how to beat it?"
"I can see three route modifications that would break the convergence pattern." She pointed northwest. "The valley we're in exits through a pass that Mordren's advance teams will reach before us. Alternative: we leave the valley here, cross the ridge to the west, and enter the adjacent valley system. The adjacent system exits northwest through terrain that the Inquisition's coverage pattern doesn't account for — a gap in their relay network, probably because the terrain is too difficult for standard relay runners."
"Difficult terrain meaning difficult for us too," Ren said.
"Difficult terrain meaning the horses can manage it but it's slow. We lose six hours. We gain operational freedom." She looked at Valen. "The trade-off is time against detection. If we stay on the current route, we save six hours but encounter Mordren's blocking position. If we divert, we add six hours but pass undetected."
"Six hours," Valen said. "Ryn has been in the vault for twelve days."
"Twelve days, yes. And if Mordren's advance teams intercept us, the delay is significantly more than six hours. It's—" She paused. The Fourth Chapter processing. "Indefinite. The convergence pattern is designed to channel the target into a contained engagement. Once contained, the Inquisition's standard protocol is sustained pressure until surrender or reinforcement arrival. Mordren's main force is three days behind us. If the advance teams pin us down, Mordren arrives in three days and the situation becomes significantly more complex."
"We divert," Valen said. No deliberation needed. Three days of Mordren closing in versus six hours of difficult terrain. The math was simple.
---
The western ridge was not simple.
Neve read it before they climbed. Her assessment: possible but unpleasant. The slope was steep, the footing was loose shale over sandstone, and the ridge top was narrow enough that they'd need to cross in single file.
They crossed. It took an hour. The horses were unhappy about it in the specific, expressive way that horses were unhappy about things — ears back, hooves placed with exaggerated care, the occasional snort that conveyed more than words. Ren's horse, the largest, had the hardest time. Ren dismounted and led it on foot, his boots sliding on the shale, swearing in combinations that were creative even by his standards.
"Seven hells and a goat's broken tooth," he said, after the third near-slip.
"That's a new one," Valen said from above him.
"Desperation breeds creativity."
They made it. The western valley was narrower but passable — better terrain on the valley floor, worse visibility from the ridges, the trade-off that Aelith's analysis had described. Drace and Tomik — Aelith's companions, who had spoken perhaps ten words between them since joining the group — took rear positions with the automatic positioning of people who had done escort duty before.
Valen rode beside Aelith. "The Fourth Chapter's pattern recognition. Can you read the Grimoire's patterns?"
She looked at him. The assessment, as always. "Yes."
"What do you see?"
"I see a communication protocol that's running at approximately twelve percent capacity. The First Chapter is designed to coordinate the network's timing — you described it as a metronome, which isn't wrong. But the metronome is barely ticking. The communication layer is active but the signal is weak because you haven't initialized the coordination sequence."
"I don't know how to initialize it."
"The vault's design documentation would tell you. That's why we're going there." She looked at the Grimoire, warm at his hip. "But I can tell you what I see from the processing side. The First Chapter is sending out a coordination pulse. Constant. Low amplitude. The Fourth Chapter receives it and the reception triggers my processing function — the chapter starts analyzing the pulse's data structure, trying to decode the coordination protocol. It can't decode it because the protocol hasn't been fully transmitted. It's like receiving the first word of a sentence and trying to guess the entire sentence from one word."
"And the Fifth Chapter?"
"The Fifth Chapter would be receiving the same pulse and trying to store it. Memory function — recording the coordination signal, building a history of the communication attempts. But without the full protocol, the memory function can't organize the data. It stores everything, which is why Ryn's personal memories are being displaced — the chapter is dedicating storage capacity to recording fragments of a signal it can't yet interpret."
"The cascade is all of us receiving partial signals and trying to make sense of them without the full protocol."
"That's the pattern I see, yes." Aelith's hands were trembling more than before. The processing load of describing the Fourth Chapter's input while simultaneously running the Inquisition pattern analysis and the terrain assessment and whatever else the chapter was feeding her. "The vault has the protocol. You activate it. The chapters synchronize. The cascade resolves."
"That simple."
"That's the pattern. Whether the execution is simple—" She managed something that was almost a smile. "The Fourth Chapter shows me patterns. It doesn't show me outcomes."
They rode. The western valley opened northwest. Behind them — to the east, beyond the ridge they'd crossed — Mordren's advance teams were converging on a valley exit that would be empty when they arrived. They'd find tracks. They'd adjust. But Aelith's analysis said the adjustment would cost them eighteen hours of repositioning, and eighteen hours was enough.
The Grimoire wrote in the margins: *Cascade at sixty-four percent.*
One point. One day. The metronome ticking up, one percent at a time, the system's failed initialization grinding forward on its own broken schedule.
He had the recognition pattern. He had the coordination protocol's first fragment. He had a processing layer riding beside him and a dying memory layer waiting in a vault two hundred and forty miles ahead.
And he had a question that wouldn't stop: whose idea was all of this?
His? The Grimoire's? The system's?
He kept riding. The question rode with him.
