Chapter 3
The Constant Variable
The Constant Variable
Jun's apartment looked larger when the walls were covered in maps.
Not because the room had changed. Bed, sink, folding table, one chair. The same single window facing the low-Indexed street. The same old terminal humming as it processed public Chronicle data a fraction slower than the units in central districts. But the walls were no longer blank enough to make the room feel like a container. They were occupied now. Coverage diagrams taped edge to edge. Sector maintenance notices. Rift schematics printed in grayscale because his terminal's color cartridge had failed months ago and replacing it cost more than he was willing to spend.
Node positions. Field overlaps. Repair delays. His own notes in tight, spare handwriting.
Rift 1174-T1: corridor flicker, SI-■ for less than 0.2 seconds. Rift 2031-T1: Node Three failure, estimated lapse 2.8-3.1 seconds, observed output inconsistent with SI-4.
He stood in the middle of the room and looked at the pattern he had built from public data and two impossible moments.
Older Rifts first. Deferred maintenance. Narrow architecture. Bad overlap at turns, shutters, level changes. The same kinds of places, repeated across the sector map until repetition stopped looking accidental.
His terminal chimed.
Not the dull system tone of an assignment update. A direct message ping. Internal Chronicle routing, but from a sender field that displayed only a clearance block.
Jun did not move for three seconds. Then he crossed to the table and opened it.
One attachment. No greeting. No signature.
He expanded the file.
A probability graph filled the screen. Sector deployments over the last two years. Team composition on the horizontal axis, expected clearance efficiency on the vertical, actual outcomes marked as points. Most clustered where they should. A dense cloud of ordinary results.
Seven points were boxed in red.
Jun read the site codes first. Rift 1902. Rift 2031. Rift 1174. Four others he recognized only after a second pass, operations where nothing memorable had happened except a feeling he had not known how to name at the time: lighter air, dimmer Displays, one step taken too fast, one crate caught before it should have slipped.
All seven had one constant variable.
Support Staff: Han Jun
At the bottom of the screen, a note appeared in plain text.
Your sector is an outlier. You are the constant variable. We should meet. Supply Depot 6, East Logistics Ring. 19:40.
Jun read it twice, then closed the probability graph and opened the sender data.
Restricted. Routed through three internal relays. No traceable department code.
He checked the time. 18:57.
The room stayed silent around him. On the wall, his printed maps held still in the terminal glow. Seven boxed anomalies on one screen. Seven times the Record had called something routine when the numbers did not support routine at all.
Jun shut down the terminal, took his jacket from the chair back, and left.
Supply Depot 6 sat behind a freight spur near the eastern logistics ring, the kind of place built for containers and inventory rather than people. The yard lights were half power. Older Nodes watched the perimeter from poles mounted too far apart. Their indicator strips glowed steady blue, but Jun saw the slight delay in one of the western units before he reached the entrance gate.
Inside, rows of sealed crates climbed toward the high ceiling. The depot smelled like dust, metal, and insulation warmed by old wiring. Forklifts were parked in charging lanes. Most of the evening staff had already cycled out.
A woman stood beside a loading pallet near the rear wall, a data pad in one hand.
Mid-thirties. Thin enough that her Authority coat hung in straight lines from her shoulders. Sharp face, dark hair tied back without interest in style. Her wrist Display read C-4.
Not the balanced C-tier spread of an operative. Jun was close enough to read the details when she turned the pad toward him.
SI-11. RG-3. CT-112. SR-87.
Analyst profile. Lopsided and expensive.
"You came," she said.
Jun stopped two meters away. "You sent internal Chronicle traffic to an F-0 porter."
"Yes."
Her voice was flat, irritated by default, as if conversation itself were a task she had already decided was inefficient. She held out the data pad. The same graph from the message filled the screen, but now each red box could be selected. She tapped one.
Rift 2031-T1. Team classification spread. Expected injury range. Expected clearance time. Environmental variance tolerance. Then the result.
"Your team should have taken longer to clear the lower corridor after the Node loss," she said. "The recorded outcome exceeds projected efficiency by 18.4 percent. That's too high for noise."
She tapped another box. Then another.
"Seven operations. Same anomaly profile. Same support assignment."
Jun looked at the numbers, then at her face. "Who are you?"
"Kara Voss. Pattern Integrity Division."
He knew the name only as a department line from public Authority notices. Pattern Integrity reviewed Record consistency. The people who checked whether the Chronicle remembered itself correctly.
Voss studied him with the focus of someone examining a crack in reinforced glass.
"Your Classification is wrong," she said.
No build. No soft entry. Just the conclusion.
Jun said, "I know."
For the first time, her expression changed. Not surprise exactly. More like a calculation she had run privately had just returned external confirmation.
"How long?" she asked.
"Ten years."
Voss lowered the data pad by a few centimeters. "Ten years."
"Yes."
She looked at him for another second, then began moving through files on the pad so quickly the screen blurred. Personnel history. Assignment logs. Medical certifications. One classified item opened after a biometric check from her thumb.
Her eyes stopped moving.
"What happened ten years ago?" she said.
Jun did not answer.
Voss turned the pad and showed him the screen.
His file. Older than the assignment records. Trainee-porter designation. One entry expanded at center.
Rift Collapse 01 Status: Sole Survivor Recording Loss Due to Node Destruction Event Reconstruction: Standard Post-Event Classification Assigned: F-0
Below that, one line of summary text.
Non-Combatant Survivor. Zero Contribution. Survived by sheltering in sealed equipment chamber until extraction.
Jun looked at the words and felt the familiar, flat pressure of seeing a lie presented in the Chronicle's font.
"I didn't hide in a chamber," he said.
"You remember that?"
"I remember not remembering." He kept his eyes on the file. "Forty-seven minutes gone. Then a medical room. Then this." He lifted his wrist slightly.
F-0 glowed in the depot light.
Voss said, "Standard reconstruction means there was no usable Record. The system interpolated from partial data and protocol assumptions."
"I know."
"Which means your Classification after the Collapse was built on a guess."
Jun nodded once.
Voss went still in the exact way a person does when many years of private suspicion suddenly acquire a body standing in front of them.
"I've logged 1,247 anomalies in fifteen years," she said. "Forty-three statistically impossible enough to require formal review. Seven tied to you. Every report vanished into archive reassignment." Her mouth flattened. "I thought the system had errors. I did not think the error would know about itself."
Jun said nothing.
That seemed to suit her. She angled the pad again and brought up a sector map dense with coverage geometry.
"I pulled public maintenance records first," she said. "Then unauthorized overlays from internal Node diagnostics. Your assignment pattern tracks degradation zones too consistently to be accidental. You seek older coverage. Lower overlap density. Why?"
Jun looked at the map. She had done in fifteen minutes what had taken him two nights: turned scattered defects into a usable shape. Her overlays were cleaner than his. Better scaled. More precise at the margins.
"Because I feel different there," he said.
Voss waited.
"The Display doesn't change for long," he said. "Sometimes not at all. But when coverage drops, my body stops listening the same way."
That was the closest he had come to saying it aloud. He expected the sentence to sound wrong once spoken. It did not. It sounded clinical. Observed.
Voss absorbed it without flinching. "You think enforcement weakens in degraded zones."
"I think the number holds harder where the Nodes are stronger."
"And weaker where they aren't."
"Yes."
She stared at the map again, but Jun could see she was no longer looking at the lines. She was looking through them, into whatever architecture connected them all.
Then she said, "There is a Tier-2 site in outer East that has been underperforming maintenance tolerance for eleven months."
Jun looked up.
She split the map and opened a second panel: Rift 2031's larger neighbor, an older industrial breach with a branching lower structure.
Rift 2118-T2 Public Coverage Integrity: 74% Actual Edge-Sector Overlap: 41% Unrepaired Node Desynchronization, eastern branch
"Forty-one percent?" Jun said.
"At lowest cycle. Higher most of the time. But the dip is regular." Voss zoomed to the branch corridor. "If my model is right, you'll get intermittent de-indexing in pulses rather than a total lapse. Not enough for a clean read. Enough for oscillation."
Jun's gaze settled on the corridor geometry. A turn. A service split. Bad line of sight for wall mounts. He could already feel how the space might behave.
Voss watched him watching the map.
"You were going to find this eventually," she said. "Slower. Less safely. Possibly dead."
"Probably," Jun said.
That earned the smallest possible acknowledgment from her, not warmth, just agreement with a correctly stated variable.
She closed the personnel file but not before Jun saw one more line beneath the Collapse record.
Recovered memory integrity: incomplete
Forty-seven minutes. A gap in him and in the system, same size.
Voss said, "I don't care about your feelings about any of this."
Jun looked at her.
She continued, "I care that the Chronicle's Record of a foundational event was fabricated and that your current Classification is downstream of that fabrication. If the data says the Record is wrong, I follow the data. You happen to be where it leads."
"Understood."
Another brief pause. Then, almost as if testing whether he would break pattern, she asked, "Are you offended?"
"No."
"Good." She held out the pad. "Then we work."
Jun took it.
Her coverage model was denser than anything he had built. Node cycling intervals. probable overlap failure windows. Historical repair deferrals cross-indexed against deployment schedules. She had even marked support staffing patterns to show how an F-0 porter could enter without drawing attention.
He said, "You built all this from public logs?"
"And things I wasn't authorized to access."
"Why risk it?"
Voss's expression returned to its default edge. "Because bad data offends me."
That, Jun believed immediately.
He handed the pad back. "What do you want first?"
"The truth of the forty-seven minutes," she said. "But before that, more numbers. Controlled numbers. I need to see what you register in partial de-indexing with a proper time stamp and external recording." She tapped Rift 2118 again. "This is the best available test site before someone repairs it."
Jun looked at the corridor map one more time.
Forty-one percent. Oscillation.
He asked, "When?"
Voss's answer came without delay. "Tomorrow."
A forklift charger clicked somewhere in the depot. One of the older Nodes at the western wall flickered and recovered. Neither of them looked at it. They were already looking at the larger flaw behind it.
Voss tucked the pad under one arm. "I'll transmit a support assignment path that puts you on the roster without triggering review. Do not reply to the message. Do not change your normal pattern tonight. If anyone asks, you don't know me."
"I don't."
For the first time, her mouth moved in a shape close to humor, though it never became one.
"Correct," she said. Then: "Han Jun."
He paused.
"You said you've known for ten years."
"Yes."
She studied him with that same hard analytical focus, but now there was something else under it. Not sympathy. Recognition of another method, another person who had spent years watching the system and refusing to accept what the screen said simply because the screen said it.
"Then let's find out what happened," she said.
Jun left the depot with the map of Rift 2118 fixed in his head and the old pressure in his chest altered into something narrower, sharper, and more useful.
For ten years the lie had belonged only to him.
Now it belonged to the numbers too.