Marcus came back at 2100.
Not 1800, because the eastern mountains marker had not been as simple to locate as Harrow's coordinates had implied. The coordinates put them at the right ridge system but the specific site — the marker embedded in the mountain's natural rock face — required two additional hours of terrain work once they'd identified the geological substrate that Cross had described.
He came back with photographs and a look that said the terrain work had involved more vertical movement than he'd planned for.
Faro came back looking like someone who had spent twenty years not in field contexts and had just confirmed why.
"The site is intact," Marcus said, setting the camera on Cross's table. "The inscription is full-depth — the notation is complete." He looked at Kira. "But the site's accessible approach is compromised."
"Compromised how," she said.
"The ridge access has a Directorate monitoring post," he said. "Established within the last week, from the equipment's installation condition. They're watching the mountain marker."
"They knew about it from Harrow's R&C data," Kira said.
"They've been sitting on the location," he said. "The monitoring post doesn't have operational personnel — it's automated, frequency monitoring equipment only. But it's there." He looked at Cross. "Getting twenty-one bearers to the eastern mountains marker without triggering the monitoring equipment—"
"Is a different planning problem than getting to the coastal cliff or the city underground," Cross finished. She was already loading the photographs onto the translation system. "The monitoring equipment will read the approach signatures. Twenty-one Protocols approaching in any distribution will trigger detection."
"The Directorate knows about the markers," Kira said.
"The Directorate has the coordinates from the R&C data," Marcus said. "They've placed monitoring equipment but not operational response teams. Which means they're watching — not blocking."
"Why would they watch rather than block," Kira said.
Nobody answered immediately.
Then Noa said: "Because they want to know what happens when the second alignment activates. Not to stop it. To observe it."
The room was quiet.
"The R&C Division has been collecting Protocol data for eleven years," Noa said. "The second alignment is the most significant Protocol event in that dataset. Blocking it would end the event. Watching it gives them the data." She paused. "They're letting the alignment happen. They're just making sure they're watching when it does."
Kira looked at the monitoring equipment map Marcus had sketched.
The plan for the second alignment had the bearers arriving at the markers. The monitoring equipment would read the approach. The Directorate would have documentation of every bearer who participated.
"It's the identification provision all over again," she said. "The Fenwick Crossing monitoring — they were building the bearer database. The mountain marker approach gives them a second confirmation pass." She looked at Marcus. "Twenty-one Protocol signatures at three locations simultaneously. All of them documented."
"All of them documented," he confirmed.
Cross had the photographs up and was running the translation alongside her existing notation framework.
---
At 2300, Cross said: "The mountains marker's inscription is different from the other two."
Kira came to the table.
"The coastal cliff marker has the distribution notation," Cross said. "The city underground marker has the distribution notation and the transmission endpoint function description." She looked at the photographs. "The eastern mountains marker has the distribution notation, the barrier endpoint function description, and—" She paused. "A symbol cluster I haven't seen before."
"New notation," Kira said.
"New to my translation framework," Cross said. "The Architect's notation system has symbols I've been working through systematically from the laboratory site photographs. Some clusters I've fully translated. Some I have partial translations. Some I haven't encountered before." She looked at the cluster. "This cluster uses the root symbol for *limit* — I know that root symbol. But the surrounding notation—"
She was quiet for a moment. Working through it.
"The *limit* cluster," she said. "Is associated with — the context suggests — the endpoint function itself. Something about the mountains marker's barrier function having a limiting effect on—" She paused. "I need more time with this."
"How much time," Kira said.
"Hours," Cross said. "The Architect's notation is internally consistent once you have the translation framework, but this cluster's construction is unusual." She looked at Kira. "The secondary symbols around *limit* are in a configuration I've seen in the laboratory site inscriptions, in the section about the dissolution fail-safe." She paused. "I need to cross-reference the dissolution fail-safe notation against this cluster to understand the relationship."
The dissolution fail-safe. The thing Cross had discovered in chapter eleven: if the binding agent failed, the blessing-curse pairs would destructively interfere. Catastrophic detonation.
"The mountains marker has a notation related to the dissolution fail-safe," Kira said.
"Related to the *limit* concept in the same context as the dissolution fail-safe notation," Cross said carefully. "That's not the same thing as having notation about the dissolution fail-safe itself." She looked at Kira. "I need hours. Don't draw conclusions yet."
"Hours," Kira said.
"Hours," Cross confirmed. She was already turning back to the photographs.
---
Kira called Harrow at midnight.
Harrow was awake — Harrow had been awake at midnight every time Kira had needed to reach her, which Kira had stopped questioning. The woman ran on some internal schedule that didn't intersect with conventional sleep timing, which Cross also did, and which Kira attributed to the specific quality of people whose minds were always working through something that couldn't wait.
"The mountains marker inscription," Kira said. "The R&C Division had access to the marker coordinates. Did they photograph the sites?"
"The laboratory sites, yes," Harrow said. "The marker sites — the three non-laboratory sites — the R&C team photographed the coastal cliff site in 2019. The city underground marker was identified but the access was complicated. The eastern mountains marker was photographed from a distance, through long-lens equipment, which didn't produce usable notation detail."
"So the R&C Division had partial photography of one marker and no usable photography of the other two," Kira said.
"Correct," Harrow said. "The notation analysis we had was based on the coastal cliff site and the laboratory site documentation." She paused. "We know the coastal cliff site's inscription describes the marker as an integration endpoint. We know the distribution notation exists. We translated the relevant sections."
"The mountains marker's barrier function," Kira said. "What the R&C translation had."
"Barrier endpoint," Harrow said. "The notation's interpretation — our interpretation — was that the barrier function contained or limited the alignment event's external expression. The primary transmission activates from the three markers simultaneously, and the barrier endpoint constrains the transmission to the network's frequency band rather than broadcasting at a frequency the general population's Protocol-sensitive biology could interact with."
"The mountains marker limits the alignment's reach," Kira said. "Contains it to the network."
"That's our translation of the barrier function, yes," Harrow said.
She heard it. The specific qualifier.
"Your translation," she said.
"R&C's translation of the partial notation from the coastal cliff site's indirect references to the mountains marker function," Harrow said. "It was a derivation from available data, not a direct translation of the mountains marker inscription itself." She paused. "Why?"
"Cross found a symbol cluster in the mountains marker's inscription that has a connection to the dissolution fail-safe notation," Kira said. "She's working on the translation. She said it's related to the *limit* concept."
Harrow was quiet.
"The dissolution fail-safe and the barrier function both involve limitation," Harrow said. "Our analysis considered the possibility that the barrier function was related to the dissolution fail-safe mechanism. The theory we held — incomplete, without the direct inscription data — was that the mountains marker's barrier endpoint might provide a stabilizing function that prevented the alignment event from triggering the dissolution fail-safe conditions." She paused. "If the alignment event generates sufficient binding agent activity, and if the blessing-curse pairs experience the kind of frequency interference that the dissolution fail-safe is designed to prevent—"
"The mountains marker limits that," Kira said.
"That was the theory," Harrow said. "Based on the partial data."
"Which means," Kira said, "that the alignment event without the mountains marker's barrier function could potentially interact with the dissolution fail-safe conditions."
"Theoretically," Harrow said. "Our analysis was not—"
"Confirmed," Kira said.
"Not confirmed," Harrow said. "Theoretical. Based on indirect evidence from an incomplete dataset." A pause. "Kira. What is Cross's current assessment of that notation cluster?"
"She's still translating it."
"Then wait," Harrow said. "Cross's direct translation of the mountains marker's inscription will be more reliable than R&C's derived theory."
"Yes," Kira said. "Thank you."
She ended the call.
She sat with the information.
The mountains marker's barrier function limited the alignment event's expression. Contained the transmission to the network's frequency band. Possibly stabilized the conditions that would otherwise risk the dissolution fail-safe's activation.
The Directorate's monitoring equipment at the mountains marker site would read the bearers' approach signatures and document them. Twenty-one Protocol bearers at three locations simultaneously.
She started thinking.
If the mountains marker's function was to limit the alignment event — to prevent the transmission from triggering dissolution conditions — then the marker group's primary function was containment rather than reception. The barrier bearers — Dorian, the high-curse-accumulation bearers — weren't there to receive the transmission. They were there to prevent the transmission from going wrong.
And the monitoring equipment documented them.
But if the barrier function was available without the full barrier group — if the mountains marker's barrier was a threshold function rather than a continuous-output function — then the monitoring equipment's approach documentation might be less comprehensive if the barrier group arrived at the marker in smaller numbers across a time window rather than all at once.
She was thinking about reducing the signature density of the mountains marker approach. Arriving in pairs, at intervals, staggering the Protocol frequency signatures so the monitoring equipment's documentation was incomplete.
The logic held.
She went to find Marcus.
---
He listened to the full version.
The mountains marker's barrier function as she understood it from Harrow's R&C analysis. The monitoring equipment's approach documentation. The proposed staggered arrival as a method to reduce the signature density.
He was quiet through the full version.
"You called Harrow tonight," he said.
"Yes."
"Before Cross finished the translation," he said.
"Cross needs hours," she said.
"And you needed the information before hours," he said.
She looked at him.
"The translation will take until morning," she said. "The monitoring equipment is in place now. Every hour we wait to think about the approach problem is an hour the Directorate has to add response capacity to the automated monitoring."
"The monitoring equipment didn't have response capacity when I left the site," he said.
"It didn't have response capacity at 1800," she said. "That can change."
He looked at her.
"Cross said don't draw conclusions," he said.
She was quiet.
"The R&C analysis is incomplete," he said. "Harrow said it was based on a derived theory from partial data." He looked at her. "You've built an operational plan around a theory that Harrow qualified three times as incomplete."
She looked at the window.
"The barrier function limiting the approach signature density," she said. "The logic holds regardless of the specific mechanism—"
"The specific mechanism is what Cross is translating," Marcus said. "The specific mechanism might tell us that the barrier function isn't a threshold function. It might tell us that the barrier group's arrival needs to be simultaneous for the function to work. It might tell us something that makes your staggered arrival plan actively harmful." He looked at her. "Wait for Cross."
She looked at the window.
He was right.
She knew he was right before she'd started the call with Harrow, if she was honest about it. The call had been impatience dressed in operational logic — the thing she did when waiting was harder than moving, which was most of the time.
"Wait for Cross," she said.
"Yes," he said.
"You should have led with that," she said.
"You should have called Cross instead of Harrow," he said.
She looked at the window.
"Yes," she said.
He looked at her.
"Get some sleep," he said. "Cross will have the translation by morning." He paused. "And the plan that made sense to you at midnight probably looks different with six hours of sleep."
She looked at him.
"That's a lot of consecutive sentences with 'you' as the subject," she said.
"You noticed," he said.
"I always notice," she said.
She went to sleep.
---
Morning.
Cross's voice at 0700 through the door: "I have the translation."
Kira was awake before the knock. She went to Cross's corner and Cross had the notebook open and two pages of notation analysis beside the photographs and the quality of someone who had been working for seven hours and was satisfied with what the work had produced.
"The *limit* cluster," Cross said. "It's not the dissolution fail-safe." She looked at Kira. "The mountains marker's barrier function description uses the *limit* notation in the context of — the Architect's notation for the barrier function is — it limits the *loss*."
Kira looked at her.
"Not the transmission's reach," Cross said. "Not the dissolution conditions." She looked at the notebook. "The Architect's notation describes the mountains marker's barrier function as a limit on the *cost of the alignment event.* The alignment event — the second alignment — carries a cost for the Protocol bearers. The barrier endpoint's function is to absorb and limit that cost." She looked at Kira. "The high-curse-accumulation bearers. Dorian. The barrier group. They're at the mountains marker to carry the alignment's cost so the transmission endpoint and the integration endpoint bearers can function at full capacity."
"The cost," Kira said.
"The Architect's notation uses the same symbol root as *burden* or *weight,*" Cross said. "The alignment event generates a significant load on the binding agent architecture. Without the barrier endpoint's function, that load distributes across all three groups simultaneously. With the barrier endpoint running, the mountains group carries the alignment's load — so the transmission group at the city underground marker can receive the primary transmission without the load interfering."
"Dorian's curse accumulation," Kira said. "He's been carrying three hundred curses for forty years."
"Yes," Cross said. "And the bearers with the heaviest curse-side loads. The mountains marker needs the highest-capacity burden-carriers." She looked at Kira. "The barrier function is not a threshold. It's not a one-of-many function. It requires the full barrier group at the marker simultaneously to work at the capacity the alignment needs."
"Not staggered," Kira said.
"Not staggered," Cross confirmed. "If the barrier group arrives in intervals, the barrier function runs at partial capacity until the last barrier bearer arrives. The alignment's load distributes into the other groups during the interval." She paused. "The staggered arrival approach would have put the transmission endpoint group — your group — under load that should be going to the mountains marker."
"And I would have been trying to receive the primary transmission under full alignment load," Kira said.
"Yes," Cross said. "Which the notation suggests is — the Architect's word for what happens to the transmission endpoint without barrier support is the same symbol used elsewhere for structural failure." She looked at Kira. "You would have been in the transmission endpoint trying to receive the Architect's message with the full weight of the alignment event on the binding agent architecture that you generate."
She sat with that.
The plan she'd built from Harrow's R&C analysis. The logic that had held at midnight. The operational move that would have, if she'd executed it, put the transmission endpoint at risk of the specific failure mode the barrier function was designed to prevent.
"The monitoring equipment," Kira said.
"Is a problem," Cross said. "But the solution isn't a staggered arrival. The solution is arriving in a way the monitoring equipment can't meaningfully use." She paused. "Which is different."
"How," Kira said.
"The monitoring equipment reads Protocol signatures. The signature density at the mountains marker triggers the documentation flag. But—" Cross looked at the relay display, where Yael's integration blessing was maintaining its steady active maintenance. "The mountains marker's barrier group at full simultaneous arrival would saturate the monitoring equipment's frequency reading with the barrier function's startup. The equipment is calibrated for individual Protocol frequencies. The barrier function generates a collective frequency that the R&C calibration — which was derived from individual bearer data — hasn't modeled."
"The barrier function saturates the monitoring equipment," Kira said.
"Potentially," Cross said. "The equipment reads the startup of the barrier function as an anomalous frequency rather than individual Protocol signatures." She paused. "It documents the event. But it doesn't document twenty-one individual identifications."
"Cross," Kira said.
"Yes," Cross said. "I know. I should have had this translation before you called Harrow at midnight." She paused. "But also — you didn't execute the staggered arrival plan. You went to sleep."
"Marcus told me to wait," Kira said.
"Marcus was correct," Cross said.
"Yes," Kira said. "He was."
She looked at the notebook. At the full translation she'd had to wait for. At the plan that had seemed airtight at midnight and had contained a structural flaw that a full translation would have revealed.
"The alignment," she said. "When."
"The approach problem is manageable," Cross said. "The barrier function saturation provides some coverage at the mountains marker. The coastal cliff site's approach is unmonitored. The city underground is access-controlled but not frequency-monitored." She looked at Kira. "I'd say two days. Enough time to brief the full barrier group on the mountains marker's specific function and prepare the simultaneous arrival coordination."
"Two days," Kira said.
"Two days," Cross confirmed.
She looked at the relay display. At 13.3%, stable under Yael's maintenance.
Two days to the second alignment.
Two days to the Architect's primary transmission.
Two days to the message the test had been building toward.
She'd almost damaged it last night with a plan that had good logic and wrong data. Marcus had stopped her. Cross's translation had confirmed why.
Both at once. The near-miss and the recovery from it.
She went to find Marcus and tell him she'd been wrong.
[INTEGRATION: 13.3% — SECOND ALIGNMENT: T-MINUS 48 HOURS — BARRIER FUNCTION: CONFIRMED]
