The morning brief on Sprint 4 day twenty-three ran at seven, exactly as it had run every day since day two.
Charlotte stood at the front of the room. The team was in their positions — Peder at the activation station with his notes, Tomas with the agricultural distribution summary, Fen with the production quality log, Mara with the field indicator readings, Brennan and Oskar at the back with the technical cross-references, Vane at his newly permanent station. Kaelen at the back of the room, in the position he had occupied since day four.
Nothing about the arrangement had changed.
Everything about it had changed.
Charlotte ran the brief. Production metrics. Distribution update. Field indicator status — Mara reported a potential low-pressure system in eleven days, within the warning window. Sprint 4 week three targets. The agricultural market region four pilot launch.
She ran it with the specific efficiency she had been developing for months, and underneath the efficiency, something that had been present as an undercurrent was simply no longer undercurrent. It was present. It was not announced. It was there the way the warmth from the heating elements was there — consistently, without requiring acknowledgment.
After the brief, as the team dispersed, Sera paused beside Charlotte.
She did not say anything. She handed Charlotte a document — the week three distribution schedule — with the expression of someone who had been waiting for something to resolve itself for months and had woken up this morning to find it had.
Charlotte took the document.
Sera walked away.
---
The afternoon review ran from two to four.
They were working through the Obsidian supply chain integration — the specific problem of how the northern ore distribution could complement the southern production without creating the visibility that had been a risk under the Queen's surveillance. The problem was complex because the solution had to work in three simultaneous registers: operationally viable, legally sound, and politically invisible.
Charlotte had three approaches mapped. She walked through them. Kaelen identified two practical complications she had not anticipated — one logistical, one related to the seasonal closure of the Keth valley route — and she adjusted the approaches accordingly.
By the end of the review, approach two had emerged as clearly preferable with three modifications.
Charlotte wrote up the conclusion. Kaelen added two notes.
They had been doing this for months. The specific quality of it — the ease, the complementary angles, the way neither of them spent time defending their position when the other identified a genuine problem — was something she had experienced rarely in her professional life and had not expected to find in Aethelgard.
She looked at the revised approach on the page.
"This is good," she said.
"Yes," he said.
She looked at him.
He looked at her.
There was a specific quality to this moment that was different from the equivalent moments in previous months — not the content, which was the same kind of work they had been doing, but the register. The layer of calculation that had been present, underneath, for most of those months was absent. She had not noticed it when it was there. She noticed its absence now.
"The Harlan correspondence," she said. "He sent a follow-up this morning. Two additional case studies on the crown initiative structures."
"I saw it," Kaelen said.
"Both are useful," Charlotte said. "The second one particularly — it describes the specific mechanism the Church used to reframe a technical process as falling under existing regulatory authority. That is the mechanism Malakai will attempt."
"Yes," Kaelen said. "I was going to mention that."
She looked at him.
"You read the correspondence before I did," she said.
"I read it at five this morning," he said. "The communication array delivers at four-thirty."
She held his gaze.
"You have been reading the incoming correspondence at four-thirty in the morning," she said.
"The operational relevance requires timely review," he said.
Charlotte looked at him for a moment.
"The intelligence network summaries," she said. "You send those at six."
"Yes."
"And the estate communication array delivers at four-thirty."
"Yes."
She held his gaze.
"You have been awake since four-thirty every morning," she said.
He held her gaze with the expression of someone who had been caught doing something they intended to continue doing regardless.
"The perimeter check is at two," he said.
"Yes," she said. "I know."
They held each other's gaze for a moment.
"The Harlan second case study," Charlotte said, returning to the document. "The mechanism he describes. I want to build the legal counter-argument before Malakai's ninety-day window opens."
"Yes," Kaelen said. "How long do you need."
"Two weeks to build a sound argument. One week to have Peder review it for technical accuracy. One additional week for Harlan to review the legal framing." She paused. "Four weeks."
"That is within Malakai's window," he said.
"Yes," she said. "Deliberately."
She picked up her pen.
They worked until six.
---
That evening, the knowledge map session had a specific quality Charlotte had not expected: they were not adding content. The map was at thirty-nine pages and the sections that remained were the winter storm data and the Obsidian eastern face, both of which were not yet available.
They sat with the map.
Charlotte had not sat with the map without working on it since the first week, when the map had been three pages and she had not yet understood what it was becoming.
"Forty-one pages when it's complete," she said.
"Approximately," Kaelen said.
"Plus the Obsidian section."
"Yes," he said.
She looked at the map.
"When I started this," she said, "I thought it was an operational intelligence document."
"Yes," he said. "You told me that. On day twelve, approximately, when I asked what you were building."
She looked at him. "You remembered the day."
"I remember most days," he said. "The early ones particularly."
Charlotte turned this over.
"What do you remember about day four," she said. "The day you said you shifted from watching for evidence of espionage to watching the methodology."
He was quiet for a moment. "You were running the morning brief," he said. "You had been there for four days and you had already reorganized the staff assignments, identified the secondary activation process, and started the production documentation. You stood at the front of the room and asked the team what they noticed about the production flow that was not in the records." He paused. "No one had ever asked them that before. They were not sure what to do with the question."
"Peder answered first," Charlotte said.
"Yes," he said. "He said the preparation stage was the bottleneck and he had known it for three years."
Charlotte looked at the map.
"And that was when you shifted," she said.
"That was when I understood that what you were doing was not what I had been sent to investigate," he said. "What you were doing was something I had not seen before."
She held his gaze.
"What was it," she said.
He looked at the map for a moment.
"You were asking," he said. "Simply asking. Without an agenda beyond the information. And you were receiving the answers as if they mattered — which they did — and acting on them immediately. There was no gap between the asking and the acting."
Charlotte looked at the map.
"That is the methodology," she said.
"Yes," he said. "I know that now. On day four, I only knew that it worked."
She held his gaze.
"You have been applying it since," she said.
"Yes," he said. "With varying results."
"The varying results are the learning," she said.
"Yes," he said. "I know that too."
They sat with the map for a while longer.
At ten, Charlotte said: "The morning brief tomorrow. I am adding a new standing item — a five-minute segment for team members to share what they have noticed that is not in any current document or record. Not the emerging opportunities item. Something smaller — observations, anomalies, things that seem potentially significant but don't fit existing categories."
Kaelen looked at her. "What will you call it."
Charlotte thought about this.
"Noticing," she said.
He held her gaze.
"Yes," he said. "That is the right word."
He said goodnight. She said goodnight. He left.
Charlotte sat at the map.
She thought about day four. She thought about Peder answering first.
She thought about Kaelen, who had been watching her ask questions for five months and had learned to ask them himself, and who had started a morning brief in Obsidian two weeks into the implementation, and who was going to talk to a retired arcanist and ask her what she knew.
She opened the risk register to a fresh page.
She wrote: *Sprint 4, day 23. Added the Noticing item to the morning brief. Kaelen confirmed it was the right word.*
Below it she wrote: *He remembered day four. He remembered Peder answering first. He has been paying attention in the specific way that I have been paying attention, which is the way that means the thing matters to you.*
She looked at the sentence.
Below it she wrote: *I know this. I have known it for some time. It is different to have it confirmed.*
She closed the register.
The workshop was warm.
She got back to work.
---
The new standing item debuted at the day twenty-four morning brief.
Charlotte introduced it simply: five minutes at the end of the brief, for anyone to share something they had noticed that did not fit existing categories. Not a problem requiring solution. Not an opportunity requiring development. Just a noticing.
The team received this with the quality she had come to expect from them when something new was introduced — attentive, not performative.
On day twenty-four, Fen used the five minutes. She had noticed that the pre-activation conditioning process she had developed in Sprint 2 produced slightly different results depending on the temperature of the fragments when they entered the conditioning stage. She had been tracking this for three weeks. The variance was small — less than two percent — but it was consistent. She had not brought it up before because she was not yet certain it was significant.
Charlotte wrote it down. "Is it significant?" she asked.
"I don't know yet," Fen said.
"Then it belongs in the Noticing item," Charlotte said. "When you know whether it's significant, bring it to the main brief."
Fen nodded.
After the brief, Kaelen found Charlotte in the corridor.
"The fragment temperature observation," he said.
"Yes," Charlotte said.
"It may be significant," he said. "The Obsidian winter cold — the fragments from the northern ore deposits would enter processing at a significantly lower temperature than the southern fragments. If the temperature affects the conditioning, the process will need calibration for northern conditions."
Charlotte stopped walking.
She had not thought of this.
"Yes," she said. "You're right."
"Fen should document the variance data," he said. "Before I return to Obsidian."
Charlotte turned to look at him.
"You are thinking about the Obsidian implementation from inside a morning brief about Aurelia production," she said.
"Yes," he said. "The cross-reference is natural."
She held his gaze.
"You have been doing this throughout Sprint 4," she said. "Taking what you observe here and immediately cross-referencing with Obsidian conditions."
"Yes," he said.
"That is why the implementation reports from Obsidian have been improving each week," she said. "Not because the implementation is getting easier. Because your cross-referencing is getting more accurate."
He held her gaze.
"You noticed that," he said.
"Yes," she said. "I have been noticing things about the way you work since approximately day twelve."
He was quiet for a moment.
"What did you notice on day twelve," he said.
Charlotte thought about day twelve. The storm. The afternoon with the tea and the World Rules documentation that she could not read because she already knew what it said. The first conversation that was not about the operation.
"That you described Obsidian in terms of light and color," she said. "Not military terminology. You said the ice forms in layers and changes color as the season progresses. You said the mountain appears to be lit from within in deep winter." She paused. "That was the first time I understood that you were not only a military commander."
He held her gaze.
"What was I," he said.
Charlotte looked at him.
"Someone who had been paying attention to his home for a long time," she said, "without having anyone to tell it to."
The corridor was quiet. The workshop sounds were audible through the wall.
He held her gaze for a long moment.
"Yes," he said, quietly. "That is what I was."
Charlotte turned toward her study.
"Fen's fragment temperature data," she said. "I'll ask her to add it to the Noticing log with the date and measurement conditions. When you're ready to cross-reference with the northern parameters, the log will be there."
"Thank you," he said.
She walked to her study.
Her index finger tapped once against the door frame as she passed through it.
Then she was at her desk, and the Sprint board was running, and there was work to do.
---
The Noticing item produced, over the following week, seven observations from six different team members.
Two of them turned out to be significant enough to move to the main brief and the Sprint board. Three were added to the Noticing log for continued observation. Two were resolved immediately — one was a measurement artifact from a calibration tool that needed adjustment, which Peder identified and fixed the same morning it was raised.
Charlotte reviewed the log at the end of each week. She added her own observations to the team record rather than keeping them separate — something she had started doing in Sprint 3 after noticing that the team responded differently to information that came from her separately versus information that arrived through the same channels as theirs.
She was not separate from the team. She was the architect of the system and a member of the team. Both things were true.
On day twenty-seven, Kaelen added an observation to the Noticing log.
He had never used the item before — he attended the briefs but did not typically contribute to the standing items. The observation was brief: *The northern field fluctuation data from Obsidian winter records shows a pattern of increased variance in the transitional zone during the thirty-day period immediately preceding the spring thaw. Cross-reference with southern field data suggested.*
Charlotte read it. She went to find Mara and Oskar.
By the end of the afternoon, all three of them were in the workshop with the field indicator data and the Obsidian winter records and a cross-reference analysis that Oskar described, with the specific understatement of someone whose work had just located something significant, as *interesting.*
Charlotte looked at the cross-reference.
The pattern Kaelen had noticed in the northern data had a direct southern counterpart — a variance increase in the same thirty-day window before the spring thaw, which none of them had flagged because they had been focusing on storm prediction rather than seasonal transitions. The variance increase was not dangerous. It was, however, informative: it meant the field itself was signaling the seasonal change with measurable advance notice.
"This is a new indicator," Mara said. "Not a storm warning. A seasonal transition marker."
"Yes," Oskar said. "I think so."
"How far in advance," Charlotte said.
"Thirty days," Mara said. "Consistent across both datasets."
Charlotte looked at the cross-reference.
"Add it to the field indicator program," she said. "Sprint 5 backlog, new item: seasonal transition marker development. Mara leads, Oskar and Brennan supporting."
She went to find Kaelen.
He was in the back courtyard.
"The Noticing item," she said. "Your observation. Mara and Oskar found the southern counterpart. It is a new indicator — seasonal transition, thirty days advance notice."
He held her gaze.
"Yes," he said. "I thought it might be."
"You have been watching the northern field data since you arrived," she said.
"Yes," he said. "I have been watching the pattern since the winter records were integrated into the map."
Charlotte looked at him.
"You have been contributing to the field indicator program," she said, "for three months, without calling it that."
He held her gaze.
"Yes," he said. "I suppose I have."
She held his gaze.
"The morning brief," she said. "The Noticing item. It is for observations that do not fit existing categories."
"Yes," he said. "I noticed something that did not fit existing categories."
"You also," she said, "noticed it because you were paying attention to the northern data specifically, which you were doing because you live in the north and the data is relevant to you and you have been paying attention to your home for a long time."
He held her gaze.
"Yes," he said. "That is correct."
Charlotte looked at the courtyard wall.
"April," she said.
"Yes," he said. "April."
She turned toward the door.
The workshop was warm.
She got back to work.
You've reached the end of this chapter
The morning brief on Sprint 4 day twenty-three ran at seven, exactly as it had run every day since day two.
Charlotte stood at the front of the room. The team was in their positions — Peder at the activation station with his notes, Tomas with the agricultural distribution summary, Fen with the production quality log, Mara with the field indicator readings, Brennan and Oskar at the back with the technical cross-references, Vane at his newly permanent station. Kaelen at the back of the room, in the position he had occupied since day four.
Nothing about the arrangement had changed.
Everything about it had changed.
Charlotte ran the brief. Production metrics. Distribution update. Field indicator status — Mara reported a potential low-pressure system in eleven days, within the warning window. Sprint 4 week three targets. The agricultural market region four pilot launch.
She ran it with the specific efficiency she had been developing for months, and underneath the efficiency, something that had been present as an undercurrent was simply no longer undercurrent. It was present. It was not announced. It was there the way the warmth from the heating elements was there — consistently, without requiring acknowledgment.
After the brief, as the team dispersed, Sera paused beside Charlotte.
She did not say anything. She handed Charlotte a document — the week three distribution schedule — with the expression of someone who had been waiting for something to resolve itself for months and had woken up this morning to find it had.
Charlotte took the document.
Sera walked away.
---
The afternoon review ran from two to four.
They were working through the Obsidian supply chain integration — the specific problem of how the northern ore distribution could complement the southern production without creating the visibility that had been a risk under the Queen's surveillance. The problem was complex because the solution had to work in three simultaneous registers: operationally viable, legally sound, and politically invisible.
Charlotte had three approaches mapped. She walked through them. Kaelen identified two practical complications she had not anticipated — one logistical, one related to the seasonal closure of the Keth valley route — and she adjusted the approaches accordingly.
By the end of the review, approach two had emerged as clearly preferable with three modifications.
Charlotte wrote up the conclusion. Kaelen added two notes.
They had been doing this for months. The specific quality of it — the ease, the complementary angles, the way neither of them spent time defending their position when the other identified a genuine problem — was something she had experienced rarely in her professional life and had not expected to find in Aethelgard.
She looked at the revised approach on the page.
"This is good," she said.
"Yes," he said.
She looked at him.
He looked at her.
There was a specific quality to this moment that was different from the equivalent moments in previous months — not the content, which was the same kind of work they had been doing, but the register. The layer of calculation that had been present, underneath, for most of those months was absent. She had not noticed it when it was there. She noticed its absence now.
"The Harlan correspondence," she said. "He sent a follow-up this morning. Two additional case studies on the crown initiative structures."
"I saw it," Kaelen said.
"Both are useful," Charlotte said. "The second one particularly — it describes the specific mechanism the Church used to reframe a technical process as falling under existing regulatory authority. That is the mechanism Malakai will attempt."
"Yes," Kaelen said. "I was going to mention that."
She looked at him.
"You read the correspondence before I did," she said.
"I read it at five this morning," he said. "The communication array delivers at four-thirty."
She held his gaze.
"You have been reading the incoming correspondence at four-thirty in the morning," she said.
"The operational relevance requires timely review," he said.
Charlotte looked at him for a moment.
"The intelligence network summaries," she said. "You send those at six."
"Yes."
"And the estate communication array delivers at four-thirty."
"Yes."
She held his gaze.
"You have been awake since four-thirty every morning," she said.
He held her gaze with the expression of someone who had been caught doing something they intended to continue doing regardless.
"The perimeter check is at two," he said.
"Yes," she said. "I know."
They held each other's gaze for a moment.
"The Harlan second case study," Charlotte said, returning to the document. "The mechanism he describes. I want to build the legal counter-argument before Malakai's ninety-day window opens."
"Yes," Kaelen said. "How long do you need."
"Two weeks to build a sound argument. One week to have Peder review it for technical accuracy. One additional week for Harlan to review the legal framing." She paused. "Four weeks."
"That is within Malakai's window," he said.
"Yes," she said. "Deliberately."
She picked up her pen.
They worked until six.
---
That evening, the knowledge map session had a specific quality Charlotte had not expected: they were not adding content. The map was at thirty-nine pages and the sections that remained were the winter storm data and the Obsidian eastern face, both of which were not yet available.
They sat with the map.
Charlotte had not sat with the map without working on it since the first week, when the map had been three pages and she had not yet understood what it was becoming.
"Forty-one pages when it's complete," she said.
"Approximately," Kaelen said.
"Plus the Obsidian section."
"Yes," he said.
She looked at the map.
"When I started this," she said, "I thought it was an operational intelligence document."
"Yes," he said. "You told me that. On day twelve, approximately, when I asked what you were building."
She looked at him. "You remembered the day."
"I remember most days," he said. "The early ones particularly."
Charlotte turned this over.
"What do you remember about day four," she said. "The day you said you shifted from watching for evidence of espionage to watching the methodology."
He was quiet for a moment. "You were running the morning brief," he said. "You had been there for four days and you had already reorganized the staff assignments, identified the secondary activation process, and started the production documentation. You stood at the front of the room and asked the team what they noticed about the production flow that was not in the records." He paused. "No one had ever asked them that before. They were not sure what to do with the question."
"Peder answered first," Charlotte said.
"Yes," he said. "He said the preparation stage was the bottleneck and he had known it for three years."
Charlotte looked at the map.
"And that was when you shifted," she said.
"That was when I understood that what you were doing was not what I had been sent to investigate," he said. "What you were doing was something I had not seen before."
She held his gaze.
"What was it," she said.
He looked at the map for a moment.
"You were asking," he said. "Simply asking. Without an agenda beyond the information. And you were receiving the answers as if they mattered — which they did — and acting on them immediately. There was no gap between the asking and the acting."
Charlotte looked at the map.
"That is the methodology," she said.
"Yes," he said. "I know that now. On day four, I only knew that it worked."
She held his gaze.
"You have been applying it since," she said.
"Yes," he said. "With varying results."
"The varying results are the learning," she said.
"Yes," he said. "I know that too."
They sat with the map for a while longer.
At ten, Charlotte said: "The morning brief tomorrow. I am adding a new standing item — a five-minute segment for team members to share what they have noticed that is not in any current document or record. Not the emerging opportunities item. Something smaller — observations, anomalies, things that seem potentially significant but don't fit existing categories."
Kaelen looked at her. "What will you call it."
Charlotte thought about this.
"Noticing," she said.
He held her gaze.
"Yes," he said. "That is the right word."
He said goodnight. She said goodnight. He left.
Charlotte sat at the map.
She thought about day four. She thought about Peder answering first.
She thought about Kaelen, who had been watching her ask questions for five months and had learned to ask them himself, and who had started a morning brief in Obsidian two weeks into the implementation, and who was going to talk to a retired arcanist and ask her what she knew.
She opened the risk register to a fresh page.
She wrote: *Sprint 4, day 23. Added the Noticing item to the morning brief. Kaelen confirmed it was the right word.*
Below it she wrote: *He remembered day four. He remembered Peder answering first. He has been paying attention in the specific way that I have been paying attention, which is the way that means the thing matters to you.*
She looked at the sentence.
Below it she wrote: *I know this. I have known it for some time. It is different to have it confirmed.*
She closed the register.
The workshop was warm.
She got back to work.
---
The new standing item debuted at the day twenty-four morning brief.
Charlotte introduced it simply: five minutes at the end of the brief, for anyone to share something they had noticed that did not fit existing categories. Not a problem requiring solution. Not an opportunity requiring development. Just a noticing.
The team received this with the quality she had come to expect from them when something new was introduced — attentive, not performative.
On day twenty-four, Fen used the five minutes. She had noticed that the pre-activation conditioning process she had developed in Sprint 2 produced slightly different results depending on the temperature of the fragments when they entered the conditioning stage. She had been tracking this for three weeks. The variance was small — less than two percent — but it was consistent. She had not brought it up before because she was not yet certain it was significant.
Charlotte wrote it down. "Is it significant?" she asked.
"I don't know yet," Fen said.
"Then it belongs in the Noticing item," Charlotte said. "When you know whether it's significant, bring it to the main brief."
Fen nodded.
After the brief, Kaelen found Charlotte in the corridor.
"The fragment temperature observation," he said.
"Yes," Charlotte said.
"It may be significant," he said. "The Obsidian winter cold — the fragments from the northern ore deposits would enter processing at a significantly lower temperature than the southern fragments. If the temperature affects the conditioning, the process will need calibration for northern conditions."
Charlotte stopped walking.
She had not thought of this.
"Yes," she said. "You're right."
"Fen should document the variance data," he said. "Before I return to Obsidian."
Charlotte turned to look at him.
"You are thinking about the Obsidian implementation from inside a morning brief about Aurelia production," she said.
"Yes," he said. "The cross-reference is natural."
She held his gaze.
"You have been doing this throughout Sprint 4," she said. "Taking what you observe here and immediately cross-referencing with Obsidian conditions."
"Yes," he said.
"That is why the implementation reports from Obsidian have been improving each week," she said. "Not because the implementation is getting easier. Because your cross-referencing is getting more accurate."
He held her gaze.
"You noticed that," he said.
"Yes," she said. "I have been noticing things about the way you work since approximately day twelve."
He was quiet for a moment.
"What did you notice on day twelve," he said.
Charlotte thought about day twelve. The storm. The afternoon with the tea and the World Rules documentation that she could not read because she already knew what it said. The first conversation that was not about the operation.
"That you described Obsidian in terms of light and color," she said. "Not military terminology. You said the ice forms in layers and changes color as the season progresses. You said the mountain appears to be lit from within in deep winter." She paused. "That was the first time I understood that you were not only a military commander."
He held her gaze.
"What was I," he said.
Charlotte looked at him.
"Someone who had been paying attention to his home for a long time," she said, "without having anyone to tell it to."
The corridor was quiet. The workshop sounds were audible through the wall.
He held her gaze for a long moment.
"Yes," he said, quietly. "That is what I was."
Charlotte turned toward her study.
"Fen's fragment temperature data," she said. "I'll ask her to add it to the Noticing log with the date and measurement conditions. When you're ready to cross-reference with the northern parameters, the log will be there."
"Thank you," he said.
She walked to her study.
Her index finger tapped once against the door frame as she passed through it.
Then she was at her desk, and the Sprint board was running, and there was work to do.
---
The Noticing item produced, over the following week, seven observations from six different team members.
Two of them turned out to be significant enough to move to the main brief and the Sprint board. Three were added to the Noticing log for continued observation. Two were resolved immediately — one was a measurement artifact from a calibration tool that needed adjustment, which Peder identified and fixed the same morning it was raised.
Charlotte reviewed the log at the end of each week. She added her own observations to the team record rather than keeping them separate — something she had started doing in Sprint 3 after noticing that the team responded differently to information that came from her separately versus information that arrived through the same channels as theirs.
She was not separate from the team. She was the architect of the system and a member of the team. Both things were true.
On day twenty-seven, Kaelen added an observation to the Noticing log.
He had never used the item before — he attended the briefs but did not typically contribute to the standing items. The observation was brief: *The northern field fluctuation data from Obsidian winter records shows a pattern of increased variance in the transitional zone during the thirty-day period immediately preceding the spring thaw. Cross-reference with southern field data suggested.*
Charlotte read it. She went to find Mara and Oskar.
By the end of the afternoon, all three of them were in the workshop with the field indicator data and the Obsidian winter records and a cross-reference analysis that Oskar described, with the specific understatement of someone whose work had just located something significant, as *interesting.*
Charlotte looked at the cross-reference.
The pattern Kaelen had noticed in the northern data had a direct southern counterpart — a variance increase in the same thirty-day window before the spring thaw, which none of them had flagged because they had been focusing on storm prediction rather than seasonal transitions. The variance increase was not dangerous. It was, however, informative: it meant the field itself was signaling the seasonal change with measurable advance notice.
"This is a new indicator," Mara said. "Not a storm warning. A seasonal transition marker."
"Yes," Oskar said. "I think so."
"How far in advance," Charlotte said.
"Thirty days," Mara said. "Consistent across both datasets."
Charlotte looked at the cross-reference.
"Add it to the field indicator program," she said. "Sprint 5 backlog, new item: seasonal transition marker development. Mara leads, Oskar and Brennan supporting."
She went to find Kaelen.
He was in the back courtyard.
"The Noticing item," she said. "Your observation. Mara and Oskar found the southern counterpart. It is a new indicator — seasonal transition, thirty days advance notice."
He held her gaze.
"Yes," he said. "I thought it might be."
"You have been watching the northern field data since you arrived," she said.
"Yes," he said. "I have been watching the pattern since the winter records were integrated into the map."
Charlotte looked at him.
"You have been contributing to the field indicator program," she said, "for three months, without calling it that."
He held her gaze.
"Yes," he said. "I suppose I have."
She held his gaze.
"The morning brief," she said. "The Noticing item. It is for observations that do not fit existing categories."
"Yes," he said. "I noticed something that did not fit existing categories."
"You also," she said, "noticed it because you were paying attention to the northern data specifically, which you were doing because you live in the north and the data is relevant to you and you have been paying attention to your home for a long time."
He held her gaze.
"Yes," he said. "That is correct."
Charlotte looked at the courtyard wall.
"April," she said.
"Yes," he said. "April."
She turned toward the door.
The workshop was warm.
She got back to work.
You've reached the end of this chapter