The contract was filed on the morning of Sprint 6 day eight.
Not destroyed — archived. Charlotte had thought, briefly, about whether to destroy it, and had decided against it. The contract was a record of a specific moment: the moment when something that could not yet stand on its own needed a structure to stand in. The moment had passed. The structure was no longer necessary. But the record of the moment was real, and real records were worth keeping.
She put it in the archive file with the other Sprint 1 documents and closed the drawer.
Then she went to find Kaelen.
He was in the study, reading through the Sprint 7 scope document they had been building together. He had been adding to it since the sprint review — small additions, specific details from the Obsidian operational context that refined the combined scope in ways that the Aurelia perspective alone could not have seen.
"The contract is archived," she said.
He looked up.
"Yes," he said.
She sat down in the chair across from him.
"When you signed it," she said, "you did not negotiate."
"No," he said.
"You said the terms were fair," she said. "You said negotiating against fair terms was inefficient."
"Yes," he said.
She held his gaze.
"I had prepared for three rounds of negotiation," she said. "I had the priority lists and the walk-away thresholds and the acceptable compromise positions."
"Yes," he said. "I saw your working notes. You had not cleared them from the table."
She looked at him.
"You saw my working notes," she said.
"Yes," he said. "They were organized by clause number."
Charlotte held his gaze.
"The terms were fair," she said.
"Yes," he said.
"I wrote them to be fair," she said.
"Yes," he said. "I know."
She held his gaze.
"I wrote clause nine to protect you," she said. "Before I knew I was doing it."
"Yes," he said. "I know."
She held his gaze.
"It has been in the record since the day you signed it," she said.
"Yes," he said.
She held his gaze.
"Now it is in the archive," she said.
"Yes," he said.
"Because it served its purpose," she said.
"Yes," he said.
She held his gaze.
"And we do not need it anymore," she said.
He held her gaze.
"No," he said. "We do not."
She looked at him.
"I want to be clear about that," she said. "You are here because you want to be here. Not because of a contract. Not because of a sprint review. Because you want to be here."
He held her gaze.
"Yes," he said. "That is correct."
She held his gaze.
"Good," she said.
She picked up the Sprint 7 scope document.
"Page four," she said. "The cross-domain activation training protocol. You have noted that Vane's certification process could serve as the model for Obsidian's first independent certifications."
"Yes," he said.
"The timeline you have proposed is aggressive," she said.
"Yes," he said. "But achievable."
"Based on what," she said.
"Based on watching Vane's development from the day I arrived," he said. "And on the comparative data from Peder's progression. The activation methodology is learnable in a specific time window if the foundation is correct. At Obsidian, the foundation is now correct."
Charlotte held his gaze.
"You have been tracking Vane's development," she said.
"Yes," he said. "I read the activation log daily."
"At four-thirty," she said.
"Yes," he said.
Charlotte looked at page four.
"The timeline is achievable," she said.
"Yes," he said.
She picked up her pen.
"Then we use it," she said.
---
On day nine, Fen presented the seventh design concept to the advisory domains.
She did it via the communication array — a format they had been developing for situations where physical presence was not possible. Bertram's domain and the second advisory domain both received the presentation simultaneously.
Charlotte attended. Kaelen attended. They sat in the back of the room where Fen had set up her presentation materials, and Fen stood at the front, and the room was quiet while she talked.
She did not perform. She described.
She started with the observation — the crystalline structure she had noticed in the byproduct material three months ago. She described what she had noticed, what she had not understood at the time, what she had tested, what had failed, what the failure told her, and what she had tried next.
By the time she reached the seventh design, the presentation had been running for forty minutes.
Charlotte looked at the room. Kaelen beside her. The team, Peder and Vane and Tomas and Mara and the others who had been here long enough to have heard Fen's previous presentations and who were watching this one with the specific quality of people who knew they were seeing something different.
They were right. It was different.
The previous presentations had been product demonstrations. This was a methodology demonstration. Fen was not showing the thing she had built — she was showing how she had built it.
After the presentation, the response from Bertram's domain came via relay: three questions, all specific, all focused on the observation-to-test process rather than the product outcome.
They understood what they had seen.
Charlotte wrote in the advisory notes: *Fen presentation: confirmed methodology transfer at practitioner level. The receiving domains asked about process, not product. That is the correct question.*
After the session, Fen came to Charlotte.
"The questions they asked," Fen said.
"Yes," Charlotte said.
"They were the right questions," Fen said.
"Yes," Charlotte said.
Fen held her gaze.
"Because I showed the right thing," Fen said.
"Yes," Charlotte said. "Because you showed the right thing."
Fen held her gaze.
"I have been showing the wrong thing," she said. "All the previous presentations. I was showing the product."
"Yes," Charlotte said. "The product was important. The process is transferable."
Fen held her gaze.
"I will redo the documentation for the previous six concepts," she said. "With the process included."
"Yes," Charlotte said. "That would be valuable."
Fen returned to her station.
Charlotte found Kaelen in the corridor.
"Fen," he said.
"Yes," she said.
"She understood the difference," he said.
"She has been here long enough to understand the difference," Charlotte said. "She needed the right context to apply the understanding."
"The presentation," he said.
"Yes," she said. "The presentation was the context."
He held her gaze.
"You did not tell her to present the process," he said. "You only told her to present."
"Yes," she said. "She chose what to present."
He was quiet for a moment.
"She chose correctly," he said.
"She chose correctly," Charlotte said, "because she has been watching how the methodology works for eleven months. She understood what the right choice was."
He held her gaze.
"And in eleven months at Obsidian," he said.
She held his gaze.
"Yes," she said. "In eleven months at Obsidian."
She turned toward the workshop.
"The seventh design production integration," she said. "I want to review the data this afternoon."
"Yes," he said. "After the advisory follow-up letters."
They walked to the workshop together.
The workshop was warm.
She got back to work.
---
The afternoon of day nine was warm in the specific way of summer afternoons at Aurelia — the light at the angle Charlotte had been describing to Kaelen for months, the temperature holding, the workshop bright through its narrow windows.
Charlotte was reviewing the seventh design production integration data when Kaelen came in from the courtyard.
He had been doing something she had noticed developing over the past week: spending time in the courtyard in the afternoon. Not the back courtyard, which was theirs in the specific way that things became yours through repeated use. The main courtyard, where the estate activity happened, where the staff and Legion engineers moved through on various tasks.
She had not asked about it.
He set a document on her desk — the sprint review follow-up items that he had been working through.
"The courtyard," she said, without looking up.
"Yes," he said.
"You have been there in the afternoons," she said.
"Yes," he said.
She looked up.
"I have been watching," he said. "The way you watched me at Obsidian in the morning brief. I have been watching how Aurelia moves when it is not being directed."
Charlotte held her gaze on him.
"What does it look like," she said.
He considered this.
"Like a place that has found its rhythm," he said. "Tomas adjusts the distribution schedule without asking anyone. Mara and Oskar move between the field room and the workshop at specific times that are not posted anywhere but that everyone seems to know. Fen's quality station is always running — she never leaves for lunch, she eats at the station. Vane and Peder's activation sequences are synchronized in a way that I cannot identify anyone teaching."
Charlotte held her gaze on him.
"They learned it from each other," she said.
"Yes," he said. "When did that happen."
"Sprint 3," she said. "Approximately. When the throughput started compounding — that was when they stopped thinking of themselves as individuals running sequences and started thinking of themselves as a synchronized system."
He held her gaze.
"You did not direct that," he said.
"No," she said.
"How," he said.
Charlotte looked at the production data.
"I stopped directing individual decisions and started directing the environment," she said. "The morning brief creates the shared context. The noticing item creates the permission structure. The pay review created the recognition that work was seen. The operational autonomy — the decision to let Tomas adjust the schedule, to let Mara pursue the boundary shift study, to let Fen develop her own design sequence — those were choices about what not to control."
He held her gaze.
"The environment is the product," he said.
"Yes," she said. "The operation is what the environment produces."
He was quiet for a moment.
"At Obsidian," he said. "I have been making the same decisions — the morning brief, the noticing item, the recognition of Joris and Sanna and Wren. But I have not seen the compounding yet."
"You are at Sprint 1," she said.
"Yes," he said.
"The compounding starts in Sprint 3," she said. "When they stop thinking of themselves as individuals and start thinking of themselves as a system. You are building the foundation for that."
He held her gaze.
"How will I know when it starts," he said.
"You will see Wren and Joris doing something together that neither of them was asked to do," she said. "Something that serves the operation and that you did not plan for. That is when it starts."
He held her gaze.
"Yes," he said. "I will watch for that."
She turned back to the production data.
"The seventh design integration," she said. "The efficiency gain is compounding with the conditioning protocol in a way that Fen's testing projected but that I did not fully believe until I saw the actual throughput numbers."
He looked at the data.
"The projection was correct," he said.
"The projection was correct," she said. "I should have believed it. I have been underestimating Fen's projections since Sprint 2 and they have been correct every time."
He held her gaze.
"That is a pattern worth updating," he said.
"Yes," she said. "It is."
She made a note: *Fen's projections: accurate. Stop discounting. Treat as high-confidence inputs.*
She showed him the note.
He read it.
"You are updating your model in real time," he said.
"Yes," she said. "That is the work."
He held her gaze.
"The methodology applied to itself," he said.
"Yes," she said. "Always."
She put the note in the implementation file.
The workshop was warm.
She got back to work.
---
On day ten, Charlotte and Kaelen had dinner with the full Aurelia team.
She had not planned it — Aldric had arranged it, apparently on the basis that ten days of Kaelen's visit warranted an occasion and that the occasion should be the long table in the staff dining hall and the kitchen producing the flatbread that the Legion engineers had developed a specific preference for and the Aurelia wine from Calla's distribution.
It was the second dinner like this. The first had been on the night Sprint 1 completed.
Charlotte sat at one end. Kaelen sat at the other. Between them: Peder and Tomas and Fen and Vane and Mara and Brennan and Oskar and Sera and the distribution staff and the Legion engineers who had been at Aurelia long enough to have opinions about the food and Aldric at the head of the table nearest the kitchen door.
The conversation moved the way it always moved in this space: operational and personal and technical and incidental, the specific texture of people who had been working together long enough that the categories had blurred.
At some point — Charlotte did not notice exactly when — the conversation at Kaelen's end of the table had settled into something she could not hear clearly. She watched it from her end: Peder was speaking, Kaelen was listening, two other people had leaned in.
After dinner, when the table was clearing, Peder found her.
"I was telling him about day two," Peder said.
"Yes," Charlotte said.
"He knew about it already," Peder said. "He said he had read the implementation document."
"He read all the implementation documents," Charlotte said.
Peder held her gaze.
"He knew about the secondary activation methodology," Peder said. "And the activation timeline. And the first test." He paused. "I told him what it felt like, on day two, when someone asked what I knew."
Charlotte held her gaze.
"What did you tell him," she said.
"That it felt like being found," Peder said. "After a very long time of being in the same place."
Charlotte held his gaze.
"Yes," she said. "That is what it was."
Peder nodded.
He went back to the clearing table.
Charlotte looked at Kaelen across the room, where he was helping Aldric move the chairs back — not because it was required, because it was happening and he was there.
She thought about what Peder had said.
*Being found.*
She thought about day one, and the cold room, and the clock that ran on fireflies. She thought about arriving in a body that was not hers with a 34 percent probability of success and telling herself it was just a project.
She thought about what had found her, and what she had found.
She picked up the last glass from the table.
The workshop was warm.
She got back to work.
---
On day eleven, Wren arrived at Aurelia.
She had traveled from Obsidian — not with the Legion column that had accompanied Kaelen, separately, on her own initiative. She arrived on horseback with a travel pack and the specific quality of someone who had a reason to be somewhere and had made it happen.
Charlotte met her at the gate.
"The cross-domain development team," Wren said. "For the second-generation field indicator system. Mara and I have been planning the joint session via relay for three weeks. I wanted to attend the first one in person."
Charlotte held her gaze.
"Kaelen knows you are here," she said.
"I told him I was coming," Wren said. "He said you would understand why."
Charlotte held her gaze.
"Yes," she said. "I understand why."
She brought Wren to the workshop. Mara was already at the field data station. Oskar was cross-referencing the northern and southern boundary shift projections. Three of the Aurelia distribution engineers had been added to the development team after Tomas identified their logistical knowledge as relevant to the system's implementation requirements.
The joint session ran four hours.
Charlotte attended for the first hour and then left them to it.
She found Kaelen in the back courtyard.
"Wren," she said.
"Yes," he said.
"She came on her own initiative," she said.
"Yes," he said. "I did not ask her to. I told her about the joint session. She decided to attend in person."
Charlotte held his gaze.
"That is the noticing item," she said. "She noticed that her presence would add something the relay session could not. She acted on the noticing."
"Yes," he said.
Charlotte looked at the courtyard wall.
"Three weeks ago she was contributing to the Obsidian morning brief for the first time," she said. "Now she is traveling independently to attend a cross-domain technical session because she decided it was the right thing to do."
"Yes," he said.
Charlotte held her gaze on the wall.
"Sprint 3," she said. "At Obsidian. Not calendar Sprint 3 — the equivalent moment. The compounding has started."
He held her gaze.
"Yes," he said. "I think you are right."
She turned to look at him.
"You watched for it," she said.
"Yes," he said. "You told me I would see Wren and Joris doing something together that neither of them was asked to do."
"Wren alone," she said.
"Yes," he said. "The principle is the same."
Charlotte held his gaze.
"Sprint 3," she said.
"Yes," he said.
She looked at the wall.
"It will compound from here," she said. "The same way it did here. Slowly, and then all at once."
"Yes," he said.
They stood in the back courtyard in the summer afternoon.
"The second-generation system," Charlotte said. "The joint session is running."
"Yes," he said.
"We should attend the last hour," she said.
"Yes," he said.
They walked back toward the workshop.
The workshop was warm.
She got back to work.
You've reached the end of this chapter
The contract was filed on the morning of Sprint 6 day eight.
Not destroyed — archived. Charlotte had thought, briefly, about whether to destroy it, and had decided against it. The contract was a record of a specific moment: the moment when something that could not yet stand on its own needed a structure to stand in. The moment had passed. The structure was no longer necessary. But the record of the moment was real, and real records were worth keeping.
She put it in the archive file with the other Sprint 1 documents and closed the drawer.
Then she went to find Kaelen.
He was in the study, reading through the Sprint 7 scope document they had been building together. He had been adding to it since the sprint review — small additions, specific details from the Obsidian operational context that refined the combined scope in ways that the Aurelia perspective alone could not have seen.
"The contract is archived," she said.
He looked up.
"Yes," he said.
She sat down in the chair across from him.
"When you signed it," she said, "you did not negotiate."
"No," he said.
"You said the terms were fair," she said. "You said negotiating against fair terms was inefficient."
"Yes," he said.
She held his gaze.
"I had prepared for three rounds of negotiation," she said. "I had the priority lists and the walk-away thresholds and the acceptable compromise positions."
"Yes," he said. "I saw your working notes. You had not cleared them from the table."
She looked at him.
"You saw my working notes," she said.
"Yes," he said. "They were organized by clause number."
Charlotte held his gaze.
"The terms were fair," she said.
"Yes," he said.
"I wrote them to be fair," she said.
"Yes," he said. "I know."
She held his gaze.
"I wrote clause nine to protect you," she said. "Before I knew I was doing it."
"Yes," he said. "I know."
She held his gaze.
"It has been in the record since the day you signed it," she said.
"Yes," he said.
She held his gaze.
"Now it is in the archive," she said.
"Yes," he said.
"Because it served its purpose," she said.
"Yes," he said.
She held his gaze.
"And we do not need it anymore," she said.
He held her gaze.
"No," he said. "We do not."
She looked at him.
"I want to be clear about that," she said. "You are here because you want to be here. Not because of a contract. Not because of a sprint review. Because you want to be here."
He held her gaze.
"Yes," he said. "That is correct."
She held his gaze.
"Good," she said.
She picked up the Sprint 7 scope document.
"Page four," she said. "The cross-domain activation training protocol. You have noted that Vane's certification process could serve as the model for Obsidian's first independent certifications."
"Yes," he said.
"The timeline you have proposed is aggressive," she said.
"Yes," he said. "But achievable."
"Based on what," she said.
"Based on watching Vane's development from the day I arrived," he said. "And on the comparative data from Peder's progression. The activation methodology is learnable in a specific time window if the foundation is correct. At Obsidian, the foundation is now correct."
Charlotte held his gaze.
"You have been tracking Vane's development," she said.
"Yes," he said. "I read the activation log daily."
"At four-thirty," she said.
"Yes," he said.
Charlotte looked at page four.
"The timeline is achievable," she said.
"Yes," he said.
She picked up her pen.
"Then we use it," she said.
---
On day nine, Fen presented the seventh design concept to the advisory domains.
She did it via the communication array — a format they had been developing for situations where physical presence was not possible. Bertram's domain and the second advisory domain both received the presentation simultaneously.
Charlotte attended. Kaelen attended. They sat in the back of the room where Fen had set up her presentation materials, and Fen stood at the front, and the room was quiet while she talked.
She did not perform. She described.
She started with the observation — the crystalline structure she had noticed in the byproduct material three months ago. She described what she had noticed, what she had not understood at the time, what she had tested, what had failed, what the failure told her, and what she had tried next.
By the time she reached the seventh design, the presentation had been running for forty minutes.
Charlotte looked at the room. Kaelen beside her. The team, Peder and Vane and Tomas and Mara and the others who had been here long enough to have heard Fen's previous presentations and who were watching this one with the specific quality of people who knew they were seeing something different.
They were right. It was different.
The previous presentations had been product demonstrations. This was a methodology demonstration. Fen was not showing the thing she had built — she was showing how she had built it.
After the presentation, the response from Bertram's domain came via relay: three questions, all specific, all focused on the observation-to-test process rather than the product outcome.
They understood what they had seen.
Charlotte wrote in the advisory notes: *Fen presentation: confirmed methodology transfer at practitioner level. The receiving domains asked about process, not product. That is the correct question.*
After the session, Fen came to Charlotte.
"The questions they asked," Fen said.
"Yes," Charlotte said.
"They were the right questions," Fen said.
"Yes," Charlotte said.
Fen held her gaze.
"Because I showed the right thing," Fen said.
"Yes," Charlotte said. "Because you showed the right thing."
Fen held her gaze.
"I have been showing the wrong thing," she said. "All the previous presentations. I was showing the product."
"Yes," Charlotte said. "The product was important. The process is transferable."
Fen held her gaze.
"I will redo the documentation for the previous six concepts," she said. "With the process included."
"Yes," Charlotte said. "That would be valuable."
Fen returned to her station.
Charlotte found Kaelen in the corridor.
"Fen," he said.
"Yes," she said.
"She understood the difference," he said.
"She has been here long enough to understand the difference," Charlotte said. "She needed the right context to apply the understanding."
"The presentation," he said.
"Yes," she said. "The presentation was the context."
He held her gaze.
"You did not tell her to present the process," he said. "You only told her to present."
"Yes," she said. "She chose what to present."
He was quiet for a moment.
"She chose correctly," he said.
"She chose correctly," Charlotte said, "because she has been watching how the methodology works for eleven months. She understood what the right choice was."
He held her gaze.
"And in eleven months at Obsidian," he said.
She held his gaze.
"Yes," she said. "In eleven months at Obsidian."
She turned toward the workshop.
"The seventh design production integration," she said. "I want to review the data this afternoon."
"Yes," he said. "After the advisory follow-up letters."
They walked to the workshop together.
The workshop was warm.
She got back to work.
---
The afternoon of day nine was warm in the specific way of summer afternoons at Aurelia — the light at the angle Charlotte had been describing to Kaelen for months, the temperature holding, the workshop bright through its narrow windows.
Charlotte was reviewing the seventh design production integration data when Kaelen came in from the courtyard.
He had been doing something she had noticed developing over the past week: spending time in the courtyard in the afternoon. Not the back courtyard, which was theirs in the specific way that things became yours through repeated use. The main courtyard, where the estate activity happened, where the staff and Legion engineers moved through on various tasks.
She had not asked about it.
He set a document on her desk — the sprint review follow-up items that he had been working through.
"The courtyard," she said, without looking up.
"Yes," he said.
"You have been there in the afternoons," she said.
"Yes," he said.
She looked up.
"I have been watching," he said. "The way you watched me at Obsidian in the morning brief. I have been watching how Aurelia moves when it is not being directed."
Charlotte held her gaze on him.
"What does it look like," she said.
He considered this.
"Like a place that has found its rhythm," he said. "Tomas adjusts the distribution schedule without asking anyone. Mara and Oskar move between the field room and the workshop at specific times that are not posted anywhere but that everyone seems to know. Fen's quality station is always running — she never leaves for lunch, she eats at the station. Vane and Peder's activation sequences are synchronized in a way that I cannot identify anyone teaching."
Charlotte held her gaze on him.
"They learned it from each other," she said.
"Yes," he said. "When did that happen."
"Sprint 3," she said. "Approximately. When the throughput started compounding — that was when they stopped thinking of themselves as individuals running sequences and started thinking of themselves as a synchronized system."
He held her gaze.
"You did not direct that," he said.
"No," she said.
"How," he said.
Charlotte looked at the production data.
"I stopped directing individual decisions and started directing the environment," she said. "The morning brief creates the shared context. The noticing item creates the permission structure. The pay review created the recognition that work was seen. The operational autonomy — the decision to let Tomas adjust the schedule, to let Mara pursue the boundary shift study, to let Fen develop her own design sequence — those were choices about what not to control."
He held her gaze.
"The environment is the product," he said.
"Yes," she said. "The operation is what the environment produces."
He was quiet for a moment.
"At Obsidian," he said. "I have been making the same decisions — the morning brief, the noticing item, the recognition of Joris and Sanna and Wren. But I have not seen the compounding yet."
"You are at Sprint 1," she said.
"Yes," he said.
"The compounding starts in Sprint 3," she said. "When they stop thinking of themselves as individuals and start thinking of themselves as a system. You are building the foundation for that."
He held her gaze.
"How will I know when it starts," he said.
"You will see Wren and Joris doing something together that neither of them was asked to do," she said. "Something that serves the operation and that you did not plan for. That is when it starts."
He held her gaze.
"Yes," he said. "I will watch for that."
She turned back to the production data.
"The seventh design integration," she said. "The efficiency gain is compounding with the conditioning protocol in a way that Fen's testing projected but that I did not fully believe until I saw the actual throughput numbers."
He looked at the data.
"The projection was correct," he said.
"The projection was correct," she said. "I should have believed it. I have been underestimating Fen's projections since Sprint 2 and they have been correct every time."
He held her gaze.
"That is a pattern worth updating," he said.
"Yes," she said. "It is."
She made a note: *Fen's projections: accurate. Stop discounting. Treat as high-confidence inputs.*
She showed him the note.
He read it.
"You are updating your model in real time," he said.
"Yes," she said. "That is the work."
He held her gaze.
"The methodology applied to itself," he said.
"Yes," she said. "Always."
She put the note in the implementation file.
The workshop was warm.
She got back to work.
---
On day ten, Charlotte and Kaelen had dinner with the full Aurelia team.
She had not planned it — Aldric had arranged it, apparently on the basis that ten days of Kaelen's visit warranted an occasion and that the occasion should be the long table in the staff dining hall and the kitchen producing the flatbread that the Legion engineers had developed a specific preference for and the Aurelia wine from Calla's distribution.
It was the second dinner like this. The first had been on the night Sprint 1 completed.
Charlotte sat at one end. Kaelen sat at the other. Between them: Peder and Tomas and Fen and Vane and Mara and Brennan and Oskar and Sera and the distribution staff and the Legion engineers who had been at Aurelia long enough to have opinions about the food and Aldric at the head of the table nearest the kitchen door.
The conversation moved the way it always moved in this space: operational and personal and technical and incidental, the specific texture of people who had been working together long enough that the categories had blurred.
At some point — Charlotte did not notice exactly when — the conversation at Kaelen's end of the table had settled into something she could not hear clearly. She watched it from her end: Peder was speaking, Kaelen was listening, two other people had leaned in.
After dinner, when the table was clearing, Peder found her.
"I was telling him about day two," Peder said.
"Yes," Charlotte said.
"He knew about it already," Peder said. "He said he had read the implementation document."
"He read all the implementation documents," Charlotte said.
Peder held her gaze.
"He knew about the secondary activation methodology," Peder said. "And the activation timeline. And the first test." He paused. "I told him what it felt like, on day two, when someone asked what I knew."
Charlotte held her gaze.
"What did you tell him," she said.
"That it felt like being found," Peder said. "After a very long time of being in the same place."
Charlotte held his gaze.
"Yes," she said. "That is what it was."
Peder nodded.
He went back to the clearing table.
Charlotte looked at Kaelen across the room, where he was helping Aldric move the chairs back — not because it was required, because it was happening and he was there.
She thought about what Peder had said.
*Being found.*
She thought about day one, and the cold room, and the clock that ran on fireflies. She thought about arriving in a body that was not hers with a 34 percent probability of success and telling herself it was just a project.
She thought about what had found her, and what she had found.
She picked up the last glass from the table.
The workshop was warm.
She got back to work.
---
On day eleven, Wren arrived at Aurelia.
She had traveled from Obsidian — not with the Legion column that had accompanied Kaelen, separately, on her own initiative. She arrived on horseback with a travel pack and the specific quality of someone who had a reason to be somewhere and had made it happen.
Charlotte met her at the gate.
"The cross-domain development team," Wren said. "For the second-generation field indicator system. Mara and I have been planning the joint session via relay for three weeks. I wanted to attend the first one in person."
Charlotte held her gaze.
"Kaelen knows you are here," she said.
"I told him I was coming," Wren said. "He said you would understand why."
Charlotte held her gaze.
"Yes," she said. "I understand why."
She brought Wren to the workshop. Mara was already at the field data station. Oskar was cross-referencing the northern and southern boundary shift projections. Three of the Aurelia distribution engineers had been added to the development team after Tomas identified their logistical knowledge as relevant to the system's implementation requirements.
The joint session ran four hours.
Charlotte attended for the first hour and then left them to it.
She found Kaelen in the back courtyard.
"Wren," she said.
"Yes," he said.
"She came on her own initiative," she said.
"Yes," he said. "I did not ask her to. I told her about the joint session. She decided to attend in person."
Charlotte held his gaze.
"That is the noticing item," she said. "She noticed that her presence would add something the relay session could not. She acted on the noticing."
"Yes," he said.
Charlotte looked at the courtyard wall.
"Three weeks ago she was contributing to the Obsidian morning brief for the first time," she said. "Now she is traveling independently to attend a cross-domain technical session because she decided it was the right thing to do."
"Yes," he said.
Charlotte held her gaze on the wall.
"Sprint 3," she said. "At Obsidian. Not calendar Sprint 3 — the equivalent moment. The compounding has started."
He held her gaze.
"Yes," he said. "I think you are right."
She turned to look at him.
"You watched for it," she said.
"Yes," he said. "You told me I would see Wren and Joris doing something together that neither of them was asked to do."
"Wren alone," she said.
"Yes," he said. "The principle is the same."
Charlotte held his gaze.
"Sprint 3," she said.
"Yes," he said.
She looked at the wall.
"It will compound from here," she said. "The same way it did here. Slowly, and then all at once."
"Yes," he said.
They stood in the back courtyard in the summer afternoon.
"The second-generation system," Charlotte said. "The joint session is running."
"Yes," he said.
"We should attend the last hour," she said.
"Yes," he said.
They walked back toward the workshop.
The workshop was warm.
She got back to work.
You've reached the end of this chapter