Zero POV
He does this every night.
Roof access, twenty minutes, systematic. He built the habit in his first week when he understood that the Game rewards information above almost everything else and that most Players die not because they are weak but because they are surprised. He does not get surprised. He has arranged his entire existence here around that single principle.
His VOID SOVEREIGN interface opens across his vision in layers: a map overlay, faction territories marked in dim colors, active Player signals as small lights, mission flags as geometric shapes, and the Architect's behavioral patterns as a current he has learned to read the way sailors read wind.
He starts in the northeast quadrant. Methodical. Left to right.
He is seventeen seconds in when he realizes he is thinking about the dungeon.
Specifically: the ceiling that became a wall. The ninety-degree redirect. The way her hands came up before she knew she was moving, the way the GLITCH read the trap's mechanic and didn't copy it so much as argue with it, repurpose it, turn the Game's own structure back on itself.
He has spent two years learning the Game's grammar. She has been here seventy-two hours, and she is already conjugating verbs that the system doesn't know exist.
He goes back to the northeast quadrant. Starts again.
Thirty seconds in: the Patch situation.
He is honest with himself about the Patch situation, because dishonesty in self-assessment is a liability he cannot afford. The boy is not a threat. He is also not useful in any immediate tactical sense. A SCOUT class with no offensive capability and four months of accumulated map knowledge is an asset in theory and a dependent in practice, and dependents are weight, and weight is the thing that gets Players killed when the Game decides to escalate.
He told her this with three words. She overrode him with three different words.
And then she held his gaze.
He has looked at a lot of people in this Game in a way that ends conversations. It is not something he does intentionally, or rather, it started intentionally and is now simply the natural consequence of two years of being the most dangerous Player on the map. People look at him and find somewhere else to be. Quickly.
She looked back.
Not aggression. Not a challenge, exactly. Just a refusal to move. The kind of stillness that isn't passive but is not quite active either. The stillness of someone who has decided where they are standing and sees no reason to discuss it further.
He starts the northeast quadrant a third time.
He gets further this time. Three full minutes of actual work, faction movements logged, two new mission flags catalogued, a shift in the Architect's activity pattern in the southern district that he marks to revisit.
Then, from two floors below, through the roof access door, he left it slightly open for airflow: her
voice.
He cannot make out the words. He can make out the shape of them easily and low, the rhythm of someone telling a story. And then Patch's response, louder, more tangled, and then something that resolves into laughter.
He stops.
He does not mean to stop. His hands are still raised, the interface still open, the northeast quadrant half-catalogued. He stops anyway.
He has not heard laughter in he does the math automatically, the way he does all math, four hundred and nineteen days. He knows the exact number because he knows the last time, which was his brother laughing at something on their mother's television while Zero stood in the kitchen pretending he was not listening, pretending the sound didn't do the thing it did.
Four hundred and nineteen days.
He looks at the open roof door.
He tells himself: this observation is neutral. It is data. A Player who can generate that kind of sound from that kind of day dungeon trial, Tier 4, unclassified ability firing twice, the information about the faction and the girl who killed her, and still laugh at something in a kitchen forty-eight hours into being dead, that is data. That tells him something about her psychological architecture that is tactically relevant.
He tells himself this is why he is still standing here listening.
He catalogs the observation.
He catalogs the fact that he is cataloging it.
He catalogs the fact that this is the second time tonight he has lost his place.
Then he turns back to his interface because the northeast quadrant will not finish itself, and
sentiment is the thing that gets people killed, and he is not sentimental; he has not been sentimental in two years. He is precise and strategic, and the laughter from two floors down is just sound, and sound is just data, and
His interface flags something.
He goes still.
New signal. Northeast district, which is why it's appearing now, he was already looking there when it registered. But this is not a signal he has seen in this configuration before. Not a standard faction pattern. Standard factions are loose, opportunistic, their territory markers bleeding and irregular.
This one is clean.
Geometrically clean, like someone sat down with intention and drew the boundaries on purpose. Organized. Funded, in Game terms, mission reward accumulation that implies coordination, resource sharing, and infrastructure. The kind of faction that doesn't happen accidentally. The kind that has a backer.
He pulls the signal closer.
At the faction's center, a single Player marker. Separate from the leadership cluster. A liaison position between the faction core and something outside it.
He reads the profile.
MIKA.CLASS: DECEIVER.FACTION STATUS: ARCHITECT-ADJACENT.CURRENT LOCATION: NORTHEAST DISTRICT.BOND STATUS: NONE.
He reads it twice.
Architect-adjacent.
Not a Player faction with Architect tolerance. Not a group that has found a way to coexist with
The game's mechanics.
Adjacent. Linked. Operating in proximity to the Architect's own structure by design.
Mika. DECEIVER class. Working a liaison position between a clean, funded, intentionally-built faction and the entity that runs the Game. Four months in, which means she was here before Nova arrived. Which means she knew the Game. Which means she knew exactly what she was doing when she
Two floors below him, the laughter has stopped.
He looks at the Player marker on his map. At the clean geometric territory. At the word DECEIVER in plain white text.
He thinks about Nova's hands going still on the counter.
He thinks about: I'm aware.
He closes the northeast quadrant. Opens a new file. Starts documenting.
The Architect does not build adjacent relationships without purpose.
Whatever Mika was sent here to do, and she was sent, he is certain of that now. The faction is too clean to be a coincidence; it has something to do with the GLITCH class Player sleeping two floors below him, who can copy the Game's own mechanics and turn them inside out.
He documents.
He does not go downstairs.
He wants to.
That is new.
He documents that too.