The seventh tertiary activation test produced an element with a projected lifespan of 13.5 months.

Charlotte transferred it to the output shelf, noted the result on the calibration log, and looked at the number.

The target was fourteen. She was at thirteen-point-five. The failure mode analysis from the previous six tests pointed to a specific variance in the third frequency band — the same variance she had been adjusting incrementally with each test. The adjustment curve was logarithmic rather than linear, which meant the final step to fourteen was smaller than the distance already covered.

Tomorrow, probably.

She wrote *tomorrow, probably* in the calibration log in the margin beside the official notation, which was a thing she would not have done on day one, and which she had started doing somewhere around week three when the logs had shifted from formal records to working documents.

Kaelen appeared in the workshop doorway at the end of the morning production run.

She knew it was him before she looked up — the specific quality of presence, the slight change in the room's attention. She had stopped cataloguing this as exceptional approximately three weeks ago.

"Tomorrow," she said, without looking up from the calibration log.

"Yes," he said. "Probably."

She looked up.

He was looking at the output shelf — the tertiary element at 13.5 months, sitting beside the secondary proof of concept that she had never moved, the two elements that bracketed six weeks of work. His expression had the quality of someone doing arithmetic that was not about numbers.

"The guild agreements," he said.

"Four and five confirmed this morning," Charlotte said. "Aldren's network came through. Five guilds."

"Five guilds," he said.

"Against a day-one projection of three by Sprint 1 end." She paused. "We exceeded the projection."

He looked at her.

"Yes," he said. "We did."

Charlotte set down the calibration log. "You're thinking about something," she said.

"I'm always thinking about something."

"Specifically."

He was quiet for a moment. Then he set a document on the workbench beside her. Not an intelligence report — she recognized it immediately as something different. The paper quality was different, the notation was different, the headers were in his hand but the structure was unfamiliar.

She picked it up.

---

It was a planning document for Obsidian's economic recovery.

She read it slowly, the way she read everything that required her full attention — starting from the structure, mapping the logic, identifying where the reasoning was sound and where it had gaps.

The structure was hers. The specific way the problems were broken into components, the way the constraints were listed before the solutions, the way each proposed action was tied to a measurable outcome — this was the PO methodology she had been practicing for six weeks in plain sight of someone who had been watching and learning.

The bones were right. There were places where he had misunderstood the application — where he had applied the methodology to a military-logistics problem in a way that worked for the logistics but missed the human-behavior layer that the methodology was designed to address. There were places where he had intuited things about his own operational environment that were more sophisticated than anything she had explicitly taught him.

She read to the last page.

She looked up.

"You wrote this yourself," she said.

"Yes."

"In three weeks."

"Yes."

Charlotte held the document. "You've been watching how I work."

"Yes," he said. "Since day four, approximately. Before that I was primarily watching for evidence of graft or espionage."

She looked at him. "And after day four."

"After day four it became clear that the more productive study was the methodology rather than the intent."

Charlotte set the document down on the workbench. She picked up her pen.

"Page three," she said. "The labor classification section. You've categorized the ice engineers under tactical support, which means their compensation and operational role are determined by military hierarchy rather than technical contribution."

"Yes."

"That's the same category error the Aurelia staff records had when I arrived." She turned to page three. "If you apply the contribution-based classification framework instead, the ice engineers come out as technical specialists. The compensation structure changes, the operational authority changes, and the retention incentive changes." She looked at him. "The Oskar problem — the three engineers who left — the root cause is in this classification."

He held her gaze. "Show me."

She pulled a blank sheet from the workspace and began writing.

They worked through the Obsidian document for two hours — Charlotte identifying the places where the methodology had been applied correctly and the places where it needed adjustment, Kaelen listening and revising with the focused attention of someone who had been waiting for exactly this feedback. Not defensive about the gaps. Not performing understanding he didn't have. Actually adjusting, actually learning, in real time.

By the time the afternoon light shifted, the document had been significantly revised. The labor classification section had been rebuilt from the foundation. The raw material supply chain had a contribution-based incentive structure. The infrastructure maintenance program had a knowledge documentation component that would, if implemented, capture what the ice engineers knew before it was lost again.

Charlotte looked at what they had produced.

It was better than what he had brought her. Better in the specific way that things became better when someone who understood the problem from the inside and someone who understood the methodology from the outside worked on it together.

"This is your project," she said. "Not mine. I'm advising on the methodology."

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

She held his gaze. "You're going to implement this in Obsidian."

"Yes."

"When."

"When the conditions are right." A pause. "When I have enough of the methodology understood to implement it without producing the same errors that produced this document's first draft."

Charlotte looked at the revised document. Then at him.

"You don't need to understand the full methodology," she said. "You need to understand the application to your specific context. Which you already do better than you think — the intuited sections on pages six and seven are more accurate than anything I could have written about Obsidian's operational environment."

He looked at the pages she indicated.

"Because I know the place," he said.

"Because you know the place," she confirmed. "I know the methodology. You know the place. The document works because both are present."

He held her gaze.

"As here," he said.

Charlotte looked at the revised Obsidian document, and at the knowledge map visible through the open doorway of the study, thirty-one pages of exactly the same dynamic applied to Aethelgard.

"As here," she said.

---

The knowledge map session that evening was different from every previous session.

They were not building the Aethelgard map. They were building the Obsidian document — working through the second section, which covered the border fortress infrastructure and the ward system maintenance program that the Church had been trying to acquire. Charlotte was adapting the knowledge documentation protocol she had developed for Aurelia to the specific requirements of a magical defense infrastructure.

It was his project. She was working on his project.

She noticed this at approximately nine in the evening, in the way she had started to notice things that were true without needing to process them through a framework.

Kaelen was describing the ward system maintenance cycles — the specific knowledge that the ice engineers carried about which wards degraded in which conditions and how — and she was translating it into a documentation protocol that would capture that knowledge before the people who held it were gone. She had done this for Aurelia. She was doing it for Obsidian. The work was the same. The context was his.

"The apprenticeship record system," she said, looking at the protocol draft. "In Aurelia, I found that the institutional knowledge was often held by people who had apprenticed under someone who was gone. The knowledge was present but orphaned — nobody knew it existed because the person holding it had no formal designation."

"In Obsidian the same," Kaelen said.

"So the protocol needs a discovery component, not just a documentation component." She made a note. "You need to find who holds the knowledge before you can document it. Which means someone needs to ask."

He held her gaze. "Yes," he said. "Someone needs to ask."

The silence that followed had the warm quality she had stopped analyzing because it was simply the texture of being in a room with him working.

"The implementation timeline," she said. "Realistically — how long from the current state to a functional version of this program."

He considered. "If I have the documentation framework complete before I return to Obsidian, and if I can identify the key knowledge holders in the first three months — six months to the first functional implementation. Twelve months to stability."

"That's aggressive," Charlotte said.

"Yes," he said. "I learned aggressive timelines from someone."

She looked at him.

"That person," she said, "would tell you that aggressive timelines require contingency planning and defect rate monitoring and a clear protocol for when the timeline needs to be revised downward."

"I know," he said. "She has told me."

Charlotte held his gaze.

"When you return to Obsidian," she said carefully.

"Yes."

"Sprint 2 ends in thirty-three days. Sprint 3 in forty-five after that."

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

"After Sprint 3."

He held her gaze. The amber eye. The blue one.

"I don't know what happens after Sprint 3," he said. Not evasive — honest. The same honest quality he used when he said things that were true and not strategic. "I know what I want to happen. I know what I am going to work toward." He paused. "The document is one part of that."

Charlotte looked at the Obsidian document — the revised pages, the documentation protocol, the knowledge capture framework she had been helping him build.

She understood what he was telling her.

"The implementation timeline," she said. "Six months to first functional implementation."

"Yes."

"That's concurrent with Aurelia's Sprint 4, approximately."

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

The silence lasted approximately ten seconds. It was the specific silence of something being said in the space between the words — not unspoken, but said in the way some things were said, through the mathematics of timelines and the logic of documents and the specific weight of the phrase *concurrent with.*

Charlotte turned to the next section of the document.

"Page nine," she said. "The supply chain incentive structure. You have the framework right, but the specific incentive thresholds need to be calibrated to northern conditions. Let me show you."

He picked up his pen.

They worked until midnight.

At the end, he looked at what they had built — the Obsidian economic recovery document, more complete than he had brought it, more accurate than either of them could have made it alone.

"I did not know this could be done," he said, quietly. In the northern speech — the formal register, the one he used when the professional layer had thinned past its usual depth.

Charlotte looked at him.

"Now you know," she said. The formal register back — the one she had been living in for six weeks, the language of the body she had inhabited and the place she had chosen. It felt natural. It felt like hers.

He held her gaze.

"Because of you," he said.

Charlotte held his gaze.

"Because you learned," she said.

The silence that followed was the longest of the evening and the warmest.

Then she said: "The knowledge map needs the eastern border section. Tomorrow evening, if you have time."

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

He said goodnight. She said goodnight. He left.

Charlotte sat with the Obsidian document for a moment — twenty-two pages of someone learning how to build something.

Then she turned to the Sprint 2 board and the Aurelia documentation and the knowledge map waiting for its next session, and she got back to work.

The workshop was warm.

---

The morning brief the following day had a specific quality Charlotte had started to recognize as the quality of a team that was operating above its own expectations.

Vane reported on his activation certification progress — third test tomorrow, projected to pass based on current calibration accuracy. Mara and Brennan presented the field indicator week-two validation results: all four indicators confirmed, storm warning window holding at 89% confidence. Fen presented the three-point housing production data: eighteen percent time reduction confirmed over a full week's run.

Charlotte listened and thought: this runs without me now.

Not entirely — the activation sequencing still required her direct oversight for the tertiary process, and the Sprint architecture required her strategic direction. But the production floor, the quality control, the field indicator program, the housing design improvements — all of it was running on the team's own momentum. She had built a thing that was running.

She thought about what that meant for what came next.

After the brief, she stayed at the board for a moment after the team dispersed. The Sprint 2 metrics were tracking above projection on every KPI. The ore supply problem she had identified was still outstanding — she had begun the preliminary analysis but had not yet found a viable solution that didn't require the territorial agreement. That was the unresolved item.

Kaelen appeared at her shoulder.

"The ore supply," he said.

"I know," she said.

"We have thirty-one days."

"I know." She looked at the board. "I don't have a solution yet that doesn't trigger the the Queen's surveillance."

"We'll find one," he said.

She looked at him. He said it with the same quality as the previous evening — not strategic, not calculated. The statement of what they would do.

"Yes," she said. "We will."

She turned back to the board. Then, without looking at him: "The document. The Obsidian document. You should know — it's good work. The foundation is sound. The gaps were in application, not understanding."

He was quiet for a moment. "You're telling me this now."

"I'm telling you this now because you should hear it from me directly rather than inferring it from the revisions." She paused. "The document is good. The implementation is achievable. You have the capability to do this."

Another pause. Longer.

"Why does it matter that I hear it directly," he said.

Charlotte looked at the board.

"Because you have been told what you were worth by people who defined your worth by your military utility," she said. "And you built something using a methodology you developed by watching me work for six weeks, and it was good, and you should know that clearly." She paused. "Not inferred. Told."

The silence that followed had the specific quality of something landing in a register he had not been using.

"Charlotte," he said. Quietly. The name — her name, the one from Dublin, the one he had said twice before and both times without knowing what he was doing.

She turned around.

He was looking at her with the amber eye and the blue one, and the morning light was coming through the workshop window, and she had been waiting — she realized now, standing here — not for the question to be answered but for this: for him to see her as clearly as she had started to see herself.

"Lyra," she said.

"Lyra," he agreed. The way he said it — not a correction, not a concession. The specific quality of someone saying a name that was right.

She turned back to the board.

"The ore supply problem," she said. "I have three candidate approaches. None of them are clean. I want to walk through them with you this afternoon."

"Yes," he said.

"Two o'clock."

"Two o'clock," he confirmed.

He left.

Charlotte stood at the board for a moment.

Then she opened the Sprint 2 architecture document and started on the ore supply section.

The workshop was warm.

She got back to work.

---

The two o'clock meeting ran until five.

Charlotte had prepared three approaches to the ore supply problem: the Obsidian territorial agreement route, the eastern independent supplier route, and a third option she had flagged as low-probability but worth examining — a consortium model where multiple small independent suppliers collectively provided the raw material, distributing the supply relationship across enough parties that no single agreement created a visible political signal.

They worked through all three.

The territorial agreement was dismissed quickly — not because it was operationally inferior, but because the the Queen's surveillance made the political exposure too high for the current phase. They set it aside.

The consortium model had merits but required three months of relationship-building before the first supply delivery could be guaranteed. The Sprint 2 timeline did not accommodate three months of pre-supply work.

The eastern independent supplier remained the most viable: fast enough, clean enough, visible to Tristan who had already identified the lead candidate. The obstacle was working with Tristan directly, which meant a level of commercial proximity to him that the current public perception strategy was designed to prevent.

Charlotte and Kaelen looked at the three approaches.

"The eastern supplier," Charlotte said. "Through Tristan."

"Yes," Kaelen said.

"The public perception strategy requires that my commercial relationships appear purely transactional. Working with Tristan directly is transactional — it does not create a personal signal to the the Queen." She paused. "What it creates is a commercial relationship with someone who knows the situation more clearly than a standard trading partner."

"Tristan's assessment of the situation," Kaelen said. "He sent the ore inquiry because he assessed that we needed the supply solution and that offering it would be useful."

"Yes," Charlotte said. "He's competent."

"He is also," Kaelen said, with the specific precision of someone choosing their words carefully, "still interested."

Charlotte held his gaze. "In the commercial relationship," she said.

"Yes," Kaelen said. "In the commercial relationship."

The silence lasted two seconds.

"The commercial relationship is what I am offering," Charlotte said. "That is clear in the inquiry response I drafted. It will be clear in every subsequent communication." She held his gaze. "The the Queen's surveillance is the risk we are managing. Tristan's orientation is not."

Kaelen held her gaze.

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

"Then we proceed with the eastern supplier approach."

"Yes," he said. "We proceed."

She wrote it on the decision log. They moved on.

At five, the meeting ended and the decision was made and Charlotte had the contact request to Tristan drafted and ready. She sent it before dinner. His response arrived the following morning: immediate, direct, the introduction would be made by end of week.

Efficient. She had expected nothing else.

---

The evening after the two o'clock meeting, the knowledge map session covered the eastern border section — specifically the trade routes toward the independent supplier territories Tristan had identified, which they were now planning around rather than merely documenting.

Kaelen was quiet during the session. Not withdrawn — present, contributing, accurate. But quieter than usual.

Charlotte noticed it at approximately eight-thirty and did not remark on it until nine, when she set down her pen and said: "The Tristan conversation this afternoon."

He looked up.

"You handled it well," she said. "The commercial relationship distinction."

"I handled it," he said, "with approximately sixty percent of the equanimity I would prefer to have had."

Charlotte held his gaze.

"The remaining forty percent," she said.

He looked at the map. "Is not relevant to the decision, which was correct."

"No," she said. "It isn't relevant to the decision." She paused. "It is relevant to the thing the decision is protecting."

He held her gaze.

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

Charlotte looked at the map — the eastern border section, the trade routes toward the ore supply, the thing they were building together in all its practical and operational reality.

"Thirty-three days," she said. "Sprint 2."

"Yes."

"Forty-five after that. Sprint 3."

"Yes."

She held his gaze.

"The forty percent," she said. "I see it." A pause. "I'm asking you to hold it for seventy-eight days."

He was quiet for a long moment.

"Yes," he said. "I can do that."

She turned back to the map.

"The eastern route through the Keth valley," she said. "If the supplier relationship is established by Sprint 2 week six, we can route the first delivery before the valley closes for winter."

"Yes," he said. He picked up his pen.

They worked through the eastern border section until eleven.

When he said goodnight and she said goodnight and he went to the door, he paused — not the threshold catalogue, but a real pause, standing in the doorway with the evening light behind him.

"Seventy-eight days is a long time," he said.

Charlotte looked at him.

"It is not," she said. "We have been building for forty-two."

He held her gaze.

Then he said goodnight again, and left.

Charlotte sat at the map.

Then she opened the risk register and wrote: *Seventy-eight days remaining in Sprints 2 and 3. I asked him to hold the forty percent. He said yes.*

Below it she wrote: *I am holding the same forty percent.*

She closed the register.

The workshop was warm.

She got back to work.