Chen had set it up in a second-floor office directly across the street from Building 2847. The room had clearly been an administrative office once - desk pushed against the window, filing cabinets along one wall, a motivational poster about "synergy" that someone had crossed out and replaced with "survival" in black marker.
Through the window, Marcus had an unobstructed view of the target structure - a three-story administrative building that looked like every other piece of UT's brick-and-concrete architecture. Rectangular, functional, completely unremarkable.
Except for the shimmer.
It was faint - you had to know what to look for - but once Marcus saw it, he couldn't unsee it. A distortion at the edges, like heat haze or bad chromatic aberration. The visual marker of a structure flagged for deletion.
The room smelled like old paper and fresh coffee - Chen had brought a full thermos, plus a backup. The desk had been cleared except for a laptop (charged), a notebook (empty pages waiting), three pens (black, redundancy in case of failure), a portable phone charger, and a radio on Channel 7.
"Baseline observation window starts at 11:00 AM," Chen said, setting up the laptop. "Team Seven moves in at noon. We document pre-implementation status, then monitor continuously through the deprecation notice deadline."
Marcus sat down at the desk, testing the chair height. It was one of those mesh ergonomic numbers that campus IT had everywhere, surprisingly comfortable. The window angle was perfect - he could see the building's main entrance, most of the ground floor windows, and enough of the perimeter to track movement.
His deprecation timer read 59 hours, 47 minutes.
"Document every thirty minutes minimum," Chen said, pulling up a spreadsheet template. "Shimmer intensity, status panel changes, visible activity. If you see anything anomalous, log it immediately."
"What counts as anomalous?"
"Anything that doesn't match expected behavior. Entity activity, System notifications, status changes, strange visual effects." Chen pointed at the radio. "Channel 7 if there's trouble. Guard post will respond. I'll check in every four hours during the day. Julie's taking night monitoring - she doesn't sleep much anyway."
Marcus adjusted the laptop angle. The view was perfect. He could see Team Seven when they arrived, track their movements, document the test in real time.
Forty-one hours, he thought. Forty-one hours to see if I'm right. And if I am, eighteen hours left on my own timer to figure out if the exploit works for individuals too.
A lot of assumptions. A lot of variables. A lot of ways this could go wrong.
But that was fine. QA was about finding failure cases. This was just a higher-stakes test environment than usual.
Chen seemed to read his mind. "You okay?"
"Define 'okay.'"
"Capable of sitting here for forty-one hours and producing reliable documentation."
"Then yes. I'm okay." Marcus opened the logging spreadsheet. "I'll call if anything breaks."
Chen hesitated like he wanted to say something else, then apparently decided against it. "Good luck, Webb. Hope your theory's right."
"Me too."
Then Chen was gone, and Marcus was alone with a laptop, a countdown timer, and a building that might or might not survive the next two days.
He pulled up the status panel for Building 2847.
Structure ID: UTX-A-2847
Classification: Administrative
Status: Flagged for Deprecation
Occupancy: 0
Activity Index: 0.03 (Critical)
Deprecation Notice: 40h 52m remaining
Threat Level: Minimal
Activity Index: 0.03. That was new - the panel hadn't shown that metric before, or Marcus had missed it in earlier documentation.
Critical. That was probably the threshold indicator. Below whatever value the System considered "maintained."
Marcus added a note entry:
11:03 AM - Baseline observation
Status: Flagged
Activity Index: 0.03 (Critical threshold)
Shimmer: Visible, moderate intensity, heat-haze effect at edges
Occupancy: 0
Note: Activity Index metric newly visible in status panel. May have always been present but not displayed until flagging occurred. Suggests System shows different data at different lifecycle stages. Will monitor for additional metrics appearing.
He checked the time. 11:03 AM. Team Seven would arrive in fifty-seven minutes.
Marcus poured coffee from the thermos - it was strong enough to strip paint, exactly how he needed it - and settled in to wait.
The room was quiet except for the faint hum of a generator somewhere below and the occasional sound of footsteps in the hallway. Through the window, Austin looked like a normal college campus frozen in time. Trees swaying slightly in the breeze. Sidewalks empty of students. The particular stillness of a place that should be full of life but wasn't.
Marcus took a sip of coffee. It burned going down.
Fifty-six minutes until the test began.
He opened his notebook and started documenting baseline environmental conditions, because if you were going to run a test, you documented everything.
Waiting, Marcus discovered over the next hour, was its own particular kind of torture.
Not the dramatic kind, where time stretched unbearably while something terrible approached. More like the low-grade cognitive friction of monitoring something that might not change for hours. The special hell of watching paint dry when the paint was reality itself and drying meant deletion.
At 11:30, Marcus logged observations. Shimmer: still visible. Status: still flagged. Activity Index: still 0.03. Nothing had changed, which was expected, but the lack of change still felt vaguely ominous.
At 11:47:23, the exact moment the System ran its deprecation cron job - Marcus held his breath and watched the status panel with the intensity of someone watching a bomb timer tick down.
Nothing changed.
No new notices. No updates. The flagged structures stayed flagged, the safe structures stayed safe, and the System's scheduled maintenance ran invisibly in whatever infrastructure powered reality now.
This story has been unlawfully obtained without the author's consent. Report any appearances on Amazon.
Marcus made notes:
11:47:23 UTC - Deprecation cron execution
No visible changes to Building 2847 status
No new deprecation notices cluster-wide (per Chen's coordination check)
Conclusion: Deprecation notices are sent when structures are ADDED to the queue, not during daily batch job processing. The 11:47:23 routine likely handles final garbage collection, not initial flagging. This implies longer intervention windows than initially thought - structures can be flagged for days before the notice goes out, if they stay below threshold long enough.
That was useful. Meant there was more time to save buildings than he'd thought. The System wasn't watching in real-time and immediately flagging abandoned structures - it was probably checking periodically and adding new candidates to a queue.
Marcus checked the time. 11:49 AM. Eleven minutes until Team Seven arrived.
He used the bathroom. Refilled his coffee. Checked his phone battery (57%). Returned to the window.
His status screen showed a new debuff:
STATUS EFFECTS:
- Anticipatory Stress (Moderate): -5% PER, mild anxiety
- Deprecated (59h 22m remaining)
Apparently the System tracked emotional states now. Great. Nothing like having your anxiety quantified and displayed as a stat penalty.
At 11:58, Marcus spotted movement. Team Seven approaching from the east - twelve people, carrying bags and equipment, moving with the purposeful casualness of people who'd been briefed on expectations.
Rivera led the group, Patterson beside her. Behind them: Santos (the nervous Runner), Kim (the skeptical Medic), Okoye (the quiet Scout). Others Marcus recognized from the briefing but whose names he was still learning.
They reached the building's entrance. Rivera unlocked it - Chen must have provided keys - and the group filed inside.
Through the ground-floor windows, Marcus watched lights turning on. Movement. People setting up stations in what looked like a former break room.
He pulled up the status panel.
Structure ID: UTX-A-2847
Status: Flagged for Deprecation
Occupancy: 12
Activity Index: 0.03 (Critical)
Deprecation Notice: 40h 48m remaining
Occupancy had updated immediately - from 0 to 12 the instant Team Seven entered. The System was tracking presence in real-time, probably through the same mechanisms that tracked player position for quest and combat purposes.
But Activity Index hadn't changed yet. Still 0.03.
Lag, Marcus thought. Metric probably updates on a delay, not instantly. Could be minutes, could be hours. Need to monitor frequency.
He logged it:
12:02 PM - Implementation begins
Team Seven on-site: 12 confirmed
Occupancy updated: 0 → 12 (IMMEDIATE response, real-time tracking confirmed)
Activity Index: Still 0.03 (no change yet - delay in metric calculation likely)
Shimmer: Still visible, unchanged intensity
Hypothesis: Occupancy is real-time. Activity Index updates on delay, frequency unknown. Monitoring for first change to establish update intervals.
Now came the hard part: waiting to see if anything happened.
Marcus poured more coffee and settled in for what might be the longest forty hours of his life.
Hour One: Baseline
The first hour passed with the speed of continental drift.
Marcus documented Team Seven's visible activity through the windows. Rivera and Patterson were setting up what looked like inventory stations on the ground floor - moving boxes, checking contents, generating the kind of routine logistics activity that would signal "maintained facility" to any monitoring system.
Santos was on second-floor patrol, visible through windows as he walked circuits. Regular movement. Predictable patterns. The kind of thing automated monitoring would flag as "active presence."
Kim had set up what looked like a medical station in a first-floor room - probably unnecessary for the test, but it gave her something to do and added to the appearance of facility operation.
Through the main entrance, Marcus could see someone had turned on all the lights. The building looked occupied. Lived-in. The opposite of abandoned.
At 12:47 PM, Marcus checked the status panel.
Activity Index: 0.03 (Critical)
No change.
Could take longer, he reminded himself. System might batch-process activity metrics. Updates could be hourly, could be on a different schedule entirely.
He made coffee. Logged observations. Watched Team Seven through the windows.
At 1:00 PM, Rivera appeared at the ground floor window and waved - a casual gesture that meant we're still alive, everything's boring, carry on.
Marcus waved back.
His status screen showed new penalties:
STATUS EFFECTS:
- Prolonged Focus (Light): -2% PER
- Deprecated (58h 47m remaining)
The monitoring was starting to grind on him. Not dramatically - he'd done longer QA sessions - but sitting still and watching for changes that might not happen for hours activated a particular kind of low-grade mental fatigue.
Marcus stood up. Stretched. Walked a circuit around the small office to keep blood flowing. Sat back down.
1:30 PM. Still 0.03.
Outside, clouds were moving in from the west. The light was changing, getting flatter. Good for visibility, actually - less glare on the windows.
2:00 PM. Still 0.03.
Marcus logged the lack of change, because negative data was still data.
And then, at 2:31 PM, something shifted.
Activity Index: 0.08 (Critical)
Marcus blinked. Refreshed the panel. Checked again.
0.08. Not 0.03. The number had changed.
Still labeled "Critical" - still below whatever threshold counted as "maintained" - but it was movement. The metric had responded to Team Seven's presence.
His hands were shaking slightly as he logged it:
2:31 PM - FIRST METRIC CHANGE
Activity Index: 0.03 → 0.08 (+60% increase)
Still flagged as "Critical" (threshold unknown but clearly above 0.08)
Occupancy: Still 12
Shimmer: Still visible, unchanged intensity
SIGNIFICANT: Activity metric is responsive to occupancy and behavior. Confirms activity-based flagging theory. Update delay approximately 2h 29m from initial occupancy. Threshold for "maintained" status unknown but clearly above 0.08. Monitoring for continued increases.
He pulled out his phone and texted Chen: Activity Index increased. 0.03 to 0.08. Theory validated. Metric is responsive. Still flagged but moving in right direction.
Chen's response came thirty seconds later: Excellent work. Keep monitoring. Document update frequency.
Marcus stared at the status panel.
The number had moved. That meant the System was watching. Processing activity data. Evaluating whether the structure deserved to stay in the deprecation queue.
Now he just had to wait to see if 0.08 was enough - or if they needed to push harder to cross whatever threshold marked "safe."
Hour Two: Doubt
By 3:00 PM, Marcus was starting to understand what "cognitive load of sustained observation" actually meant.
It wasn't just boredom. It was the particular exhaustion of forcing your brain to pay attention to something that might not change, might change slowly, might change in ways you could miss if you blinked at the wrong moment.
His eyes hurt from staring at the screen. His back hurt from the chair that had seemed comfortable three hours ago but now felt hostile to human spinal architecture. His coffee had gone lukewarm.
Activity Index: 0.08 (Critical)
Still the same. No additional movement since 2:31.
Maybe it updates every two and a half hours, Marcus thought. Maybe the next change comes at 5:00. Or maybe 0.08 is as high as it goes and we're not generating enough activity.
That was the thought that kept circling back. What if twelve people wasn't enough? What if the threshold was higher than they could reach? What if he'd gotten the theory right but the implementation wrong?
Through the window, Team Seven was still moving. Still active. Santos was on ground floor now, visible through the break room window, apparently playing cards with Kim. Rivera was doing another inventory circuit. Patterson was on perimeter patrol.
They were doing everything Marcus had asked. Generating presence, movement, activity. And the metric had moved - just not very much.
Give it time, he told himself. Two and a half hours for the first change. Maybe it accelerates. Maybe it needs sustained activity to trigger the next update.
At 3:15 PM, the Activity Index ticked up again.
Activity Index: 0.12 (Critical)
Relief hit Marcus like cold water. Not a huge jump - 0.08 to 0.12 was only 50% - but it was another change. The metric was still responding. Still increasing.
Update interval: 44 minutes. Faster than the first change.
Marcus logged it:
3:15 PM - Second metric change
Activity Index: 0.08 → 0.12
Update interval: 44 minutes (faster than initial 2h 29m - suggests accelerating response or cumulative activity measurement)
Still flagged "Critical"
Shimmer: Still visible
Pattern suggests System may be measuring cumulative activity over time, not just instant occupancy. Metric acceleration possible as sustained activity builds "weight" in the calculation.
Another text to Chen: Second increase. 0.12 now. Updates seem to be accelerating.
Chen: Good sign. Suggests sustained activity matters more than instant occupancy.
Marcus leaned back in his chair and let himself feel a moment of optimism. The theory was working. Slowly, incrementally, but working. The System was responding to their activity exactly as predicted.
Now you just have to wait another thirty-seven hours to see if it's enough, his brain supplied helpfully.
Marcus ignored that thought and focused on the data.