Sprint 2 ended on day thirty.

Charlotte was at her desk when the System board updated:

*[SPRINT 2: COMPLETE. ALL KPIs MET. INDEPENDENT REVENUE INFRASTRUCTURE: ESTABLISHED. DEBT REDUCTION: 34% (TARGET: 30%). TERTIARY ACTIVATION: IMPLEMENTED AT SCALE. SPRINT 3 INITIATED. DURATION: 45 DAYS.]*

She read it once.

Then she opened the Sprint 3 architecture document she had been building for two weeks and started the morning.

---

The first day of Sprint 3 had a different quality from the first day of Sprint 1.

On Sprint 1 day one, Charlotte had sat in a cold study with a clipboard and a System board and a 34% probability of success and had told herself it was just a project.

On Sprint 3 day one, she sat in a study that smelled of activated ore and was warm from the workshop below and had the thirty-two-page knowledge map on the corner of her desk and a Sprint 3 architecture document that Tomas and Vane and Mara had all contributed to, because she had started asking the team what they saw in the next phase and they had told her, extensively, with annotated diagrams.

She read through the Sprint 3 architecture. The agricultural market program. The vineyard pilot expansion. The eastern ore supply chain. The Development Council preparation. The tertiary activation scale-up. The Obsidian economic recovery document that was nearly complete and would be ready before Kaelen—

She stopped.

Before Kaelen left.

She had not said it directly yet — not to herself, not in the risk register, not in any document. Sprint 3 ended in forty-five days. The Development Council was on day twelve. The Obsidian recovery document would be finished by day fifteen at the current pace. Kaelen had responsibilities in Obsidian — the border garrison, the Legion, the ward systems, the three ice engineers who had come back and would be working without him until he returned.

He would leave. She had known this since the Sprints had started. She had planned around it and not said it directly and the not-saying had been its own kind of management.

She wrote it in the Sprint 3 architecture document under *key personnel transitions*: *Grand Duke Valerand von Obsidian — departure expected Sprint 3, exact date TBD.*

She looked at the sentence.

Then she closed the architecture document and went to the morning brief.

---

The brief on Sprint 3 day one had the specific quality of a team that had completed two consecutive successful sprints and knew what it was doing.

Production at one hundred and twenty percent of the original Sprint 1 projection. Distribution network covering seven settlements and five guild partners. Agricultural market development program launched. Field indicator system operational. Three ice engineers on staff. One Legacy Legion corporal certified as an activation specialist. Fen as production quality lead. Tomas as agricultural market working group lead. Mara as field indicator program lead.

Charlotte looked at the room.

She had arrived at Aurelia with forty-three staff members and a 34% probability of success.

She had built a team.

She had not, she realized standing here, told them this. She had updated the Sprint board and reviewed the metrics and assigned the working groups and implemented the pay review. She had not said: *you did this.*

"Sprint 3 begins today," she said, at the start of the brief. "Before the metrics — I want to acknowledge the two sprints we just completed." She looked at the room. "Sprint 1 target was 15% revenue growth. We hit 23%. Sprint 2 target was 30% debt reduction. We hit 34%. Tertiary activation target was fourteen months. We hit 14.2." She paused. "None of those numbers happened because of what I built. They happened because of what you built. The production processes are yours. The quality methodology is Fen's. The field indicator system is Mara's and Brennan's and Oskar's. The agricultural market model is Tomas's and Vane's." She held the room for a moment. "I designed the Sprint architecture. You built everything in it."

The specific silence that followed was the kind she had learned, over seven weeks, to recognize as the silence of a room receiving something it had needed to hear.

Peder said: "You asked."

Charlotte looked at him.

"You asked us what we knew," he said. "That is what you did. The rest—" He gestured, slightly, at the room. "—followed from the asking."

Charlotte held his gaze.

"Yes," she said. "It did."

The brief continued.

---

After the brief, she found Kaelen in the back courtyard.

He had read the Sprint 2 completion notification — she had posted it to the team board before the brief. He was standing in the courtyard with the winter light and the expression that had become, over two months, the baseline rather than the exception.

"Sprint 3 started," she said.

"Yes," he said.

"Forty-five days."

"Yes."

She stood beside him in the courtyard. The winter was easing — barely, the change was more in the light quality than in the temperature, but it was there. The specific shift from the deep-cold quality to the holding-before-spring quality that she had learned to read from Mara's field observations.

"The Development Council," she said. "Day twelve."

"Yes," he said. "Are you prepared."

"I'm building the preparation document now," she said. "I'll want your intelligence briefing by day eight."

"You'll have it by day six," he said.

She nodded. "The ore supplier — third delivery on day nine. Your logistics corps has the coordination."

"Confirmed."

"The Obsidian recovery document. Page eighteen of twenty-two. At current pace, complete by day fifteen."

"Yes," he said. "I've been working on it."

Charlotte held his gaze. "You're working on it without me now," she said.

"Yes," he said. "You built the methodology clearly enough that I can apply it without ongoing guidance." He paused. "That was the point."

"Yes," she said. "It was."

They stood in the courtyard.

"After the document is complete," Charlotte said carefully. "Obsidian will need you."

He was quiet for a moment. "Yes," he said. "It will."

"The border garrison," she said. "The ward systems. The ice engineers who came back — they're here now, but they'll need someone to build the program around. Someone who understands why they came back."

"Yes," he said.

"You need to go back," she said. Not an accusation — the statement of what was true.

He held her gaze.

"Yes," he said. "I need to go back."

Charlotte held his gaze.

"The map," she said. "The northwestern section. You said you'd bring the field fluctuation data when you returned."

"Yes," he said. "When I return."

When. Not if. The specific weight of that word.

"When," she said.

"Yes," he said. "When."

Charlotte looked at the courtyard wall — old stone, settled, patient.

"The Development Council is in thirty-two days," she said. "The document is done in fifteen. Forty-five days total in the sprint." She paused. "You don't need to leave immediately."

He held her gaze. "No," he said. "I don't."

"But you'll leave before Sprint 3 ends."

He was quiet for a long moment.

"Yes," he said. "I will leave before Sprint 3 ends."

Charlotte held his gaze.

"Then we have time," she said.

"Yes," he said. "We have time."

They stood in the courtyard in the specific quality of two people who had said something true and were standing with it, not moving past it, letting it be what it was.

Charlotte's fingers were still.

"The ore delivery coordination," she said. "Day nine. I'll need the logistics schedule by day seven."

"You'll have it," he said.

She walked back inside.

The workshop was warm.

She got back to work.

---

The ore supplier arrived on day nine with the third delivery and stayed for two additional days to review the processing integration.

His name was Edric, and he was the kind of person who had built a business on the specific insight that small independent operations were more resilient than large dependent ones — a philosophy that Charlotte recognized with the specific recognition of someone who had arrived at the same conclusion through different reasoning.

She spent the two days reviewing the supply chain integration with him and Tomas and the Legion engineers who were coordinating the transport logistics. By the end of day ten, she had a supply agreement that extended the raw material runway by fourteen months at current production volume and indefinitely at reduced production volume, with scaling provisions tied to volume thresholds.

She updated the Sprint 3 board.

*[ORE SUPPLY CHAIN: SECURED. DURATION: INDEFINITE AT CURRENT TERMS. SPRINT 3 DAY 10: 71% COMPLETE.]*

She looked at the percentage and thought: we are moving faster than I planned.

This was, she knew, a function of what had been built in the first two sprints — the team's capability, the process efficiency, the relationship network. Sprint 3 was running on the momentum of everything that had preceded it. The targets were being met not because Charlotte was working harder but because the system was working.

She thought about what that meant.

She had been managing Aurelia with the part of her brain that was always running — the framework, the KPIs, the risk register. But underneath that, something else had been running too. The names. The list. Forty-three people who had stayed and eleven more who had arrived because they were asked. The ice engineers and the Legion engineers and the vineyard and the second proof of concept element on the shelf that had arrived because she had stayed up all night reading a technical paper and believed it was right.

Sprint 3 was running because she had built something real.

She closed the Sprint board and went to find Kaelen.

---

The Obsidian recovery document was on page twenty of twenty-two.

Charlotte knew this because she had been reviewing it in the afternoon knowledge map sessions — the abbreviated forty-five-minute version, with the operational cover, the two officers present for the first thirty minutes. The knowledge map work happened in the remaining fifteen minutes and was never enough to finish the northwestern section and was always enough to not stop entirely.

She found Kaelen at his desk with the document open.

"Page twenty," she said.

He looked up. "Yes. The infrastructure maintenance section." He turned the document toward her. "I have a gap in the ward system maintenance protocol. The arcanists who currently hold the maintenance knowledge — I know their names and their specializations. I don't know the knowledge transfer mechanism."

Charlotte sat down. "The apprenticeship record system we designed for Aurelia — you built an equivalent in the Obsidian section."

"Yes. But the ward systems are more complex than the activation process. The knowledge is layered — there are things the senior arcanists know that the junior ones don't know they don't know."

Charlotte thought about this. "The discovery component," she said. "The interviews. Same approach as Aurelia — ask each person what they know, then ask them what the person above them knew that they haven't passed on yet."

"Yes," he said. "That was my instinct. I wasn't certain it transferred to the ward system context."

"It transfers," she said. "The specific structure of the knowledge doesn't change the methodology for capturing it. What changes is who you need to talk to and how you ask." She looked at the document. "The senior arcanists — you said there are four."

"Three active, one retired."

"Talk to the retired one first," Charlotte said. "She'll have the clearest picture of what the others know because she's no longer in the institutional hierarchy. She's not protecting anything."

He held her gaze. "How did you know it was a she."

"It's usually the retired ones who left because they weren't valued," Charlotte said. "And it's usually—" She stopped. "It's usually the people the institution made most invisible who have the clearest picture of the institution."

He held her gaze.

"Yes," he said. "It usually is."

They worked through the infrastructure section for an hour. By the end, page twenty had a complete maintenance protocol with a knowledge transfer mechanism and a specific first step: talk to the retired arcanist.

"Page twenty-one tomorrow," Charlotte said.

"Page twenty-one tomorrow," he confirmed.

She gathered her notes. She was at the door when he said: "Charlotte."

She stopped.

Third time. He had said it three times now — the first in the intelligence meeting, the second the morning after the tertiary activation milestone, the third now. Each time with the same quality: the name from the other place, the one he had no reason to know, said when the professional layer had thinned past its usual depth.

She turned around.

He was looking at her with the amber eye and the blue one and the expression that had been the baseline for two months and was now, today, something different — not less warm, more deliberate. Like something that had been accumulating had reached a threshold.

"The map," he said. "The northwestern section. I know I said I would bring the field fluctuation data when I returned." He paused. "But I have the data. I brought it with me when I came to Aurelia. I have been waiting for the right time to finish the section."

Charlotte held his gaze.

"You've had the data for two months," she said.

"Yes," he said.

"And you've been waiting."

"Yes," he said.

She held his gaze.

"Why," she said.

He was quiet for a moment.

"Because finishing the map means—" He stopped. Then: "Because the map is not finished while I am here."

Charlotte understood.

The map was the record of what they had been building together. Finishing it while he was still here would make it a complete thing, a thing that existed in the past tense, a thing that had been done. As long as it was unfinished, it was still in progress. As long as it was still in progress, so was everything else.

She held his gaze.

"We should finish the map," she said.

He held her gaze. "Yes," he said. "We should."

"Tonight," she said. "The public perception strategy—"

"Can accommodate one evening," he said. "The risk is low if it's once, not a pattern."

Charlotte looked at the door. Then at the map workspace with its thirty-two pages. Then at him.

"Tonight," she said. "After the operational review."

"Yes," he said. "After the operational review."

She walked back to her study.

The workshop was warm.

She could not entirely get back to work.

---

The ore supply bottleneck that Charlotte had been modeling for three days materialized on Sprint 3 day eleven.

Not a crisis — a friction point. The third delivery had been larger than projected, which was good, but the storage infrastructure at the estate had not been scaled for the increased volume, which meant the processing pipeline was backing up. Not critically, but enough to reduce throughput by twelve percent.

Tomas identified it at seven in the morning and brought it to Charlotte before the brief.

She spent twenty minutes with him mapping the immediate fix — redistributing the overflow storage to three secondary locations that had been flagged in the Sprint 2 infrastructure review but not yet implemented. The fix required six hours of labor. She had six people she could assign without disrupting the production schedule.

"Do it," she said. "Start immediately. Update me at noon."

Tomas left.

Charlotte updated the Sprint board: *STORAGE BOTTLENECK: IDENTIFIED AND IN RESOLUTION. THROUGHPUT IMPACT: -12%, PROJECTED CORRECTION BY AFTERNOON.*

Then she updated the Sprint 3 architecture with a new Sprint 4 item: *Storage infrastructure scale-up. Permanent solution for increased volume capacity.*

She had been doing this for weeks — every time a Sprint revealed a gap that wasn't addressable in the current timeline, she flagged it for the next Sprint. The Sprint 4 backlog was growing. Sprint 4 was a planning horizon that existed in her architecture document as a section with placeholder items and no dates.

She had been assuming she would be here for Sprint 4.

She had not, she realized, confirmed that assumption with anyone.

She went to find Kaelen.

---

He was in the entrance courtyard, reviewing the logistics schedule for the ore transport with two of his engineers.

She waited until the engineers were dismissed.

"The storage bottleneck," she said. "Tomas has the fix. It's in hand."

"Good," he said.

"The Sprint 4 backlog is growing," she said. "Storage infrastructure, agricultural market expansion phase two, vineyard scaling, Corporal Vane's replacement certification." She paused. "I'm assuming I'll be here for Sprint 4."

He held her gaze.

"Are you?" he said.

Charlotte held his gaze.

"Yes," she said. "I am."

He was quiet for a moment. "The System," he said. "Sprint 3 ends in thirty-four days. Has the System indicated what happens after Sprint 3?"

"No," she said. "The Sprint 3 objectives were set when Sprint 2 completed. The System hasn't indicated a Sprint 4 condition." She paused. "Which means either the System releases me at Sprint 3 completion, or the System generates a Sprint 4 automatically, or—" She stopped.

"Or?" he said.

"Or the System has already decided and I haven't been watching for the indicator," she said. "Which would be unusual for how it has operated, but not impossible." She made a note. "I'll review the System logs tonight."

"Yes," he said.

Charlotte held his gaze.

"I want to be here for Sprint 4," she said. Not the corporate register, not the operational register. The direct one.

He held her gaze.

"Yes," he said. "I know."

"The Development Council is tomorrow," she said. "Day twelve. I leave at dawn."

"Yes," he said. "I know."

"I'll be back by day fifteen," she said. "The Council runs two days. Travel is one day each way."

"Yes," he said.

Charlotte looked at the courtyard — the entrance courtyard, the operational one, the one where they stood when they were being careful.

"The map," she said. "Tonight."

"Tonight," he confirmed.

She walked back to her study.

The workshop was warm.

She got back to work — the real kind, the kind that was also waiting for the evening.