**Earth: Days 64–66**
The global coordination call took four hours on Day 65. My mother's briefing document ran to twelve pages and had been edited three times before the call began — once by Nassiri for operational framing, once by Sera for Tower-related details she wanted worded carefully, and once by me for the physics, which my mother had gotten substantially right but with two conceptual gaps that would have caused problems in the Q&A.
The reception was not uniform.
The eastern European coordination, which had been dealing with the largest single Hound population density in the world, was not interested in being told the gates were part of a non-malicious organism's feeding reflex. They were interested in being told how the gates would close. When I gave them the timeline — three to four months of contraction, beginning when Zalarus activated the reduction — the response was silence of the kind that communicated *we will decide later whether this is acceptable.*
The North American coordination was more practical: they wanted to know what the creature population dynamics would look like during the contraction. I gave them the honest answer — more aggressive in the short term, decreasing in the medium term, zero in the long term except in the eight percent remote coverage zone — and they started taking notes.
The East Asian coordination asked about the eight percent. Specifically: where. Which geological zones. This was the question I'd been expecting and hadn't fully answered yet, because Zalarus and I hadn't mapped the minimum viable coverage zone to resolution. I told them it would be primarily deep-ocean and remote highland geology, with no overlap with populated zones above threshold. They wanted that in writing.
It would be in writing when I had the anchor conversation necessary to produce it.
I spent Days 64–66 doing three things simultaneously:
First: the anchor conversations. Daily descents, each one building a more detailed map of the root system's minimum viable configuration. What the eight percent actually looked like geographically. Which channels were essential to the organism's maintenance requirements and which were expansion-reflex additions that could retract without physiological harm.
The organism was cooperative in the way that things are cooperative when they understand the stakes and have decided the proposed outcome is better than the alternative. It was not enthusiastic. It was something more useful than enthusiasm: *committed.* It had calculated, in its own temporal and dimensional terms, that the maintenance arrangement was viable, and it had made the decision, and it was now providing the information necessary to implement it.
The root system map, built across three days of anchor conversations, produced a global geological footprint that I transferred to Nassiri's coordination network in daily increments. By Day 66, the global call's follow-up questions had answers.
Second: the lens counter-preparation. The Tower's substrate lens was accelerating — the anchor's dimensional boundary readings showed it now approximately nine days from activation rather than twelve. Whatever I was going to do about the lens activation, I had nine days to be in position for it.
The plan was straightforward in principle and required everything I had in practice: be in the anchor at the moment of activation, use the composite synthesis perception to interface with the incoming focal energy as it entered the substrate, redirect it through the root system's distribution network as unfocused dispersal rather than letting it reach my architecture.
The variables: the exact timing of activation, which I couldn't know with certainty. The lens energy signature, which I was building a model of through the anchor's boundary readings but which remained incomplete. The question of whether the redirect was physically possible — whether the root system's substrate conductivity was adequate for the energy load the Tower's lens would produce.
Zalarus, when I explained what I needed, spent approximately twenty minutes of its temporal time considering. The consideration came back as: *yes, the root channels can handle the load. But the redirect will feel unusual to us. We want you present in the anchor when it occurs.*
Present in the anchor when a Tower substrate lens fired.
I added this to the list of experiences for which I did not have adequate language.
Third: Sera's logistics coordinator.
She found the location on Day 64 — southern sector, embedded in a civilian medical coordination post, presenting as a supply logistics specialist. A Tower operative who had known what the relay stations were, who had been present when the Vassal-Link signal first registered after my transit, and who had been reporting to colonial oversight for sixty-three days.
"I can arrange a meeting," Sera said. "Or I can not arrange a meeting and they continue operating as a passive intelligence asset for colonial oversight without knowing the ground situation has changed significantly."
"What do they know currently," I said.
"What Mardus's report said. Degraded Vassal-Link, relay stations non-functional, no evidence of deliberate interference. Colonial oversight's conclusion from that report: wait for the lens to restore the link."
"So they're waiting," I said. "Not reporting new intelligence, not escalating, just waiting for the lens."
"Yes."
"Then they're not a priority," I said. "The lens is the priority. After the lens is addressed, the logistics coordinator's position becomes irrelevant either way — if the redirect works, there's nothing to report. If it doesn't, then what I am or am not is going to be obvious without their assistance."
She nodded. "I'll continue monitoring."
"One thing," I said. "I need advance notice if their reporting frequency changes. If they start transmitting more often in the window before lens activation, it means colonial oversight is coordinating the timing."
"I'll have it," she said.
---