Emergency Operational Directive 7-C, issued following the southern district's habitability threshold crossing: All faction deployments are to be reconfigured around the revised covered zone boundary. Gap territory populations are acknowledged as outside current operational mandate. Association resources cannot be allocated to gap territory support without tier-seven authorization. Residents of the gap territory are encouraged to present at covered zone reception points if operational relocation is available to them.
Issued by: Seolmun Emergency Association Coordination Authority, Year One of the Catastrophe Response.
The sixth revision was finished.
He had completed the final section the previous evening — the network notation's updated entries, the pressure points at their verified positions, the permanently altered spaces category expanded to include the southern district's territory and the secondary gate's section and the corridor from Arc Two's seventh chapter. The settled presences section: the Remnant, location unchanged. The deployment monitoring addendum: the covered zone's boundary in its current configuration, the gap's expanded perimeter, the institutional response's personnel distribution as of the most recent available data.
He took it out and went to find Iseul.
They were at the third pressure point's current position with the population map's seventh revision already in progress — the southern district's displaced residents having settled into the gap territory's expanded interior with enough consistency to produce stable distribution data for the first time since the threshold crossing. The exchange: the sixth revision for the population map's distribution verification figures. Seven minutes. The coordination unremarkable.
Iseul looked at the sixth revision's network notation section. Read the addendum covering the gate formation data that the Institutional Voice's exchange had introduced. Looked at the permanently altered spaces category's expanded entries.
"The map's changing what it's describing," they said.
"The territory changed," he said.
They nodded — the specific nod that received information accurately without requiring further exchange about it. They returned to the population map. He continued.
The function near the second pressure point was still not getting done.
Third morning. He noted this with the same notational precision he applied to everything his ability registered — accurately, completely, without the notation requiring him to perform anything about it. The function was not getting done. This was information. The information's cause was in the category of things the notation was not built to contain. He continued.
The gap territory in its morning configuration received him the way it had been receiving him since Arc Two — the population's informal patterns established, the gathering nodes at their positions, the pressure points at their verified locations. He moved through it with the coverage map's sixth revision in his bag and the seventh preliminary notation beginning to accumulate in his memory.
He was at the northwestern section's edge — the Remnant's settled presence readable at the existential layer from this position, unchanged, the permanent-loss-incorporated-into-architecture quality exactly what it had been since Arc Two's eighth chapter — when the child of the gap territory appeared at the section's northern approach.
They had the sixth revision's printed copy.
Not the full revision — the section covering the gap territory's second through fourth pressure points, the notation system's shorthand visible in the margins, the pressure point positions and their risk configuration ratings recorded in the compressed notation he had developed since Arc Two.
They had, at some point, obtained a copy of the relevant section. He did not know when. He had not tracked them as someone who would obtain it. He noted this as an update to the model his ability had been building of the gap territory's population — the child had been paying more attention to the coverage map's circulation than the model had accounted for.
They looked up from the section when he reached the position.
"How do you determine where these are?" they asked. Not gesturing at the notation. Looking at it.
His ability read their pattern as they asked: someone engaging with the document as a system rather than as a map. The question was about methodology — not about the pressure points' locations, about the process that placed them at those locations. The precision of the question was not the precision of someone asking for more information. It was the precision of someone who had read the document's outputs and wanted to understand the inputs.
"Gate alarm frequency cross-referenced with coverage gradient thickness," he said. "The positions where the gap between the institutional response's coverage and the actual territory's need is most acute."
They nodded. Not the nod of someone receiving information they would store — the nod of someone integrating a method into an existing framework. "So the pressure point moves if the gradient shifts."
"Or if the gate alarm frequency changes in the area."
"Both happened after the threshold crossing," they said. Not a question.
"Yes. The sixth revision reflects the updated positions."
They looked at the section's notation for a moment. "Then between the fifth revision and the sixth, there was a period when the map was recording the old positions while the actual risk configuration had already changed."
He read their pattern as they produced this. The observation was accurate. It was also the observation of someone who understood that documentation systems and the realities they described existed in a specific temporal relationship — that the map was always behind the territory by the duration of its revision cycle, and that this lag produced a specific category of operational gap.
"Yes," he said.
"How long?"
"The lag between the arc's seventh chapter and the sixth revision's distribution. Approximately forty hours from the threshold crossing to the sixth revision's completion."
They looked at the notation again. "The secondary gate event was in that window."
He read the quality of this statement carefully. It was not an accusation. It carried no emotional weight of assignment — no suggestion that the map's lag was culpable for what the lag had contained. It was a factual observation about the temporal relationship between a documentation system and an event that occurred during its revision cycle. The statement treated the coverage map gap as a feature of the system's design rather than as a failure of the system's operation.
He had not encountered this reading of the gap from anyone else in the gap territory. Every other person who knew about the secondary gate's section had produced, in their pattern at the existential layer, some version of the specific emotional weight that came from knowing the gap had cost something. The child's pattern produced no such weight. The gap was information about how the system worked, not about what the system had failed to prevent.
"Yes," he said. "The lag is a structural feature of any documentation system. The revision cycle cannot eliminate it — only reduce it."
"So the goal isn't a perfect map. It's a map whose lag is short enough that the gap between the map and the territory doesn't produce outcomes that the operational response can't work around."
He looked at them.
They were still looking at the sixth revision's notation. The section's margins. The shorthand for permanently altered spaces applied to the secondary gate's area.
"The goal," he said, "is the safety that's available, made more accessible."
They read this. Filed it. Looked up from the notation.
"That's what the map changes," they said.
The morning's remaining operational work: the pressure point verification, the population distribution update from Iseul's figures, the seventh preliminary notation's continued accumulation. He completed each in the sequence the coverage map's methodology required. The child of the gap territory did not follow — they continued in the direction they had been heading before the exchange, the sixth revision's section folded back into whatever they had been carrying it in.
His ability noted, as he completed the circuit: the model had been updated. The child was reading the coverage map as a documentation system with a specific lag feature and a specific operational purpose. This was information about how they thought about systems. It was also, for the first time since Arc Two had established the gap territory's population model, a reading of someone in the gap territory that his ability had not produced a strategic layer for — because the quality of their engagement with the map was not strategic. It was operational. They wanted to understand the system in order to exist in it more accurately.
The same quality as the coverage map itself.
He returned to the apartment at the ordinary hour. The desk. The notebook.
He wrote the day's operational data — the pressure point verification, the distribution figures, the seventh preliminary notation's additions. He wrote the Institutional Voice's data exchange addendum: the gate formation monitoring data integrated into the sixth revision's network section, the first entries produced from the combined reading.
He turned to the margin.
He wrote, in the margin's fourth entry:
Gap territory: continuing. Map: expanding. The safety that's available, made more accessible.
He looked at the last line for a moment.
It was the child's phrasing, received and recorded. Not his notation's usual register — that register produced compression of his own observations. This was a compression of someone else's, arrived at through a twelve-minute exchange about pressure point methodology and documentation lag and what the coverage map actually changed about the gap territory's situation.
He had not produced this formulation himself. He had been given it by someone who asked about the system without the weight of everything the system had failed to prevent.
He closed the notebook.
Outside, the gap territory continued in its evening configuration. The function near the second pressure point was still not getting done. The Remnant was in their corner. Iseul was with the population map's seventh revision. The covered zone's boundary was where it was. The wrong sky held its position above what remained of Seolmun.
The same territory.
He went to sleep.
End of Arc Four, Chapter One.