By 4:00 PM, Marcus had discovered new and exciting ways for a human body to feel uncomfortable while sitting still.
His lower back was a knot of tension. His shoulders ached from hunching over the laptop. His eyes felt scratchy and dry from staring at screens and windows without enough blinking. The coffee that had seemed like a good idea at 11:00 AM was now making his hands shake slightly and his heart rate feel vaguely wrong.
His status screen was no longer subtle about it:
STATUS EFFECTS:
- Prolonged Focus (Moderate): -5% PER, +10% mental fatigue
- Physical Discomfort (Moderate): -5% STR, -3% AGI
- Caffeine Overload (Light): +5% mental speed, -5% fine motor control
- Deprecated (56h 42m remaining)
The penalties were stacking. His perception was down 5%. His strength and agility were compromised. The System was literally quantifying how much continuous monitoring sucked.
This is what test engineers feel like during overnight stability tests, Marcus thought. Except usually the penalty for falling asleep isn't missing data that could save two hundred lives.
Activity Index: 0.12 (Critical)
No change since 3:15. Marcus checked the time: 4:02 PM. Forty-seven minutes since the last update. Close to the previous interval.
He stood up-needed to move, needed to do something other than sit-and walked to the window.
Team Seven was rotating shifts. Through the ground floor windows, Marcus could see the new crew arriving: four fresh people replacing Rivera's group. The shift change was smooth, professional, the kind of logistics Chen excelled at organizing.
Santos was leaving, looking tired but not miserable. Rivera was briefing her replacement-a woman Marcus didn't recognize, Level 3 Synthesist based on her class tag.
The building still looked occupied. Still active. Still generating the signals that should tell the System: this structure is maintained, don't deprecate it.
But the Activity Index was still at 0.12. Still labeled Critical.
What if 0.12 is the ceiling? The thought was intrusive, unwelcome. What if we can't generate enough activity to cross the threshold? What if the System requires something we're not doing-combat, crafting, System-sanctioned events-and just occupying the building isn't enough?
Marcus pushed the thought away. Too early for failure analysis. The metric was moving in the right direction. They just needed more time.
At 4:17 PM, something changed.
Not the Activity Index. Something else.
The shimmer disappeared.
Marcus almost missed it. He was looking down at his notes, documenting his observations, and when he looked back up the building just looked... normal. No distortion. No heat-haze effect. Just solid, ordinary brick and concrete.
His heart rate spiked.
He pulled up the status panel with hands that suddenly forgot how to be steady.
Structure ID: UTX-A-2847
Classification: Administrative
Status: Active
Occupancy: 12
Activity Index: 0.14 (Monitored)
Threat Level: Minimal
Not flagged.
Status: Active.
Not "Flagged for Deprecation." Not "Critical threshold." Just... Active.
The deprecation notice was gone. The countdown had disappeared. A new notification appeared:
[STATUS UPDATE: Structure UTX-A-2847]
Previous Status: FLAGGED FOR DEPRECATION
Current Status: ACTIVE (Monitored)
Activity Index: 0.14 → 0.16
Note: Deprecation flag rescinded due to activity threshold restoration.
The building had been pulled from the queue. And for the first time, they had proof-not just circumstantial evidence, but a System acknowledgment that their intervention had worked.
Marcus read it three times. Then three more times. Then checked the timestamp to make sure he wasn't hallucinating from caffeine overdose and six hours of sustained focus.
4:17 PM.
The building had dropped off the deprecation list at 4:17 PM.
Exactly six hours and seventeen minutes after Team Seven had moved in.
He pulled up his notes file with hands that were actively shaking now and typed:
4:17 PM - CRITICAL STATUS CHANGE
BUILDING 2847 NO LONGER FLAGGED FOR DEPRECATION.
Status: "Flagged for Deprecation" → "Active"
Activity Index: 0.14 (labeled "Monitored" not "Critical"-threshold appears to be between 0.12-0.14)
Shimmer: GONE. Visual deprecation marker no longer visible.
Deprecation notice: REMOVED FROM QUEUE
THE EXPLOIT WORKS.
Timeline from implementation:
- 12:00 PM: Team Seven occupancy begins (Occupancy: 0 → 12)
- 2:31 PM: First Activity Index increase (0.03 → 0.08) [2h 31m]
- 3:15 PM: Second increase (0.08 → 0.12) [44m]
- 4:17 PM: Status changed to Active, flag removed (0.12 → 0.14) [62m]
Total intervention time: 6 hours 17 minutes
Activity threshold: Approximately 0.14 (±0.02 margin)
CONCLUSION: Activity-based deprecation theory confirmed. Increasing structure activity above maintenance threshold removes deprecation flag. Exploit is reproducible and documented.
His phone was ringing. Chen.
Marcus answered. "Chen-"
"I saw the status change. You're absolutely sure?"
"Completely sure." Marcus heard his own voice-it sounded strange, higher than normal, tight with adrenaline and relief and exhaustion. "Status flipped from Flagged to Active at 4:17. Shimmer's gone. The building is off the deprecation queue. Activity Index hit 0.14, labeled Monitored instead of Critical. The threshold is somewhere between 0.12 and 0.14."
"How long did it take?"
"Six hours seventeen minutes from initial occupancy to flag removal. Three metric increases total before the flip."
Chen was quiet for a moment. When he spoke again, his voice had changed-still controlled, but with an edge of something Marcus couldn't quite identify. Wonder? Disbelief? "You did it, Webb. You actually did it."
"We did it. Team Seven generated the activity. I just watched and documented."
"Don't downplay this. You found an exploitable pattern in the System's architecture and proved it could be leveraged. That's..." Chen trailed off. "That's the first time anyone's reversed a System process. Do you understand that? The first time we've actually won something."
Marcus stared at the building-solid, real, no longer condemned. Twelve people inside who were probably on their shift rotations and had no idea they'd just made history.
"We need to tell them," Marcus said.
"Already on it. I'm heading to 2847 now. You stay on monitoring-document the next few hours, make sure the status stays stable. Julie will relieve you at 8:00 PM." Chen paused. "Good work, Webb. Really good work."
This tale has been unlawfully lifted without the author's consent. Report any appearances on Amazon.
The line went dead.
Marcus sat back in his chair and looked at his status screen.
[Quest Active: Integration Assessment]
Progress: 2/3 mechanics identified, 1/1 exploit documented, 37/72 hours survived
Two mechanics now. The deprecation timing pattern. The activity-based flagging system. One more to go.
Through the window, Marcus could see Chen arriving at Building 2847. Watched him enter. Watched Team Seven gather-first floor, visible through the break room windows-as Chen told them what they'd accomplished.
He couldn't hear the conversation, but he could see the reactions. Santos's expression shifting from bored resignation to surprised excitement. Patterson's quiet nod, like he'd expected nothing less. The Level 3 Synthesist who'd replaced Rivera actually jumping slightly, fist-pump of victory.
They'd saved a building.
They'd proven the System could be fought.
And somewhere in whatever infrastructure powered reality now, something was taking notes.
The Victory
By the time Julie arrived to take over monitoring at 8:00 PM, Marcus had documented six hours of stable "Active" status, confirmed that the Activity Index was holding at 0.16 with full shifts, and consumed enough coffee to violate several workplace safety regulations.
"Go eat," Julie said, setting down her own laptop. "You look like death. Chen wants you at the council briefing in an hour, which gives you exactly enough time to shower, consume actual food, and pretend to be a functional human."
"I'm functional," Marcus protested.
"You have four different status penalties including 'Severe Exhaustion' and something called 'Reality Strain' that I've never seen before. Go. I'll watch your building."
Marcus yielded the chair and stumbled toward the dorms on legs that had forgotten how walking worked. His status screen was, admittedly, getting alarming:
STATUS EFFECTS:
- Prolonged Focus (Severe): -10% PER, severe mental fatigue
- Physical Exhaustion (Major): -15% STR, -10% AGI
- Sleep Deficit (Moderate): -10% INT
- Reality Strain (Unique): Perception slightly unstable
- Deprecated (54h 19m remaining)
Reality Strain. That was new. Apparently staring at a potentially-disappearing building for eight hours straight did things to your psyche that the System felt compelled to quantify.
Marcus showered-the hot water felt like a religious experience-ate something that might have been pasta, and made it to the council briefing at 8:57 PM feeling approximately 40% human.
The room was packed. Not just council members-word had spread. Team leads, scouts, synthesists, anyone who had a stake in the cluster's infrastructure. The energy was different from this morning's meeting. Less skeptical. More electric.
Vasquez called it to order at exactly 9:00 PM. "Webb, Chen-summary for the record."
Chen stood. "Building UTX-A-2847 was flagged for deprecation with forty-one hours remaining on the notice. We implemented increased activity protocols: twelve-person occupancy on rotating shifts, continuous operations, sustained presence and resource use. At 4:17 PM, six hours and seventeen minutes post-implementation, the building's deprecation status was rescinded. It's now marked as Active with an Activity Index of 0.16, labeled Monitored. The exploit is confirmed reproducible."
The room erupted-not chaos, but controlled excitement. People asking questions, confirming details, already thinking about applications.
Rodriguez: "What's the minimum threshold? How much activity do we need to maintain to keep buildings safe?"
Marcus fielded that one. "Threshold appears to be between 0.12 and 0.14 Activity Index. We crossed it at 0.14 and the flag was removed. To maintain safety margin, I'd recommend keeping buildings above 0.16 if possible, but 0.14 should be sufficient for deprecation prevention."
"How many people does it take?" Someone from the back.
"We used twelve on rotating shifts-four on-site at any given time. Don't know if that's minimum requirement or overprovisioned. We can test with smaller groups to establish parameters, but twelve worked reliably."
"How long does it take to reverse a flag?"
"Six hours seventeen minutes in our test case, but that may vary depending on starting Activity Index and intensity of operations. Lower starting values might take longer. Higher activity might work faster."
Patel, the Synthesist with taped glasses, raised her hand. "Can we reverse deprecations that are already in progress? If someone's building hits the seventy-two-hour countdown, can we still save it?"
Marcus glanced at his own timer-54 hours, 3 minutes remaining. "My working hypothesis: yes, if we intervene before the final processing window. But I can't prove it yet. That would require testing with an individual deprecation, not a structure."
The room went very quiet.
Vasquez looked at Marcus for a long moment. "You want to test that with your own deprecation."
"If it works, I survive and we prove we can rescue individuals, not just buildings. If it doesn't work..." Marcus kept his voice level. "If it doesn't work, you've lost one analyst and proven the intervention window is shorter than we thought. Either way, data."
"That's not-" Patel started.
"That's exactly the right approach," Vasquez interrupted. "Webb's already under countdown. Testing with his status gives us individual-level data we can't get any other way, and it's data we need. But we're not sending him back to his building alone." She looked at Chen. "Organize an escort team. Whatever resources he needs. If we can reverse an individual deprecation, that changes the scope of what's survivable."
Chen nodded. "Understood. Webb, we'll coordinate logistics tomorrow. For now, let's focus on building protection."
The meeting continued for another hour-implementation planning, resource allocation, priority rankings for at-risk structures. Which buildings to staff first, how many people each needed, how to balance protection with other cluster operations.
Marcus contributed where he could, but his brain was running on fumes and residual adrenaline. The Severe Exhaustion penalty was making thinking feel like moving through mud.
When the meeting finally ended at 10:30, Marcus was ready to sleep for approximately sixteen hours.
Chen caught him in the hallway. "You did good tonight. The council's on board, we have authorization to expand the program, and you're officially the cluster's deprecation specialist."
"Great. Do I get a title plaque?"
"You get first priority for any resources you need to test your own survival." Chen's expression was serious. "I meant what I said in there. We're not letting you walk back to East Austin alone. Tomorrow we plan the escort logistics. Tonight, you sleep."
"Can't argue with that."
"Good. Because you look like death warmed over, and if you collapse from exhaustion before we test your theory, I'm going to be very annoyed." Chen clapped him on the shoulder. "Get some rest, Webb. You earned it."
Marcus made his way back to the dorms, navigating the cluster's nighttime routine on autopilot. His body was running on fumes, his brain was made of static, and his deprecation timer was counting down with mechanical precision.
But they'd saved a building.
They'd proven the System could be fought.
Tomorrow he'd find out if that victory came with a price.
The Cost
Marcus slept like the dead-which was ironic given his circumstances-and woke up at 6:47 AM with his body's internal clock apparently synchronized to the System's deprecation cron timing.
His deprecation timer read 48 hours, 14 minutes.
Outside his window, the cluster was already moving. Guard rotations. Supply runs. The ambient noise of two hundred people surviving another day.
Marcus got dressed, grabbed his phone, and was halfway to the coordination center when the notification appeared.
Blue text. System message. Priority flag in his peripheral vision that made it impossible to ignore.
[SYSTEM NOTICE: Behavioral Analysis]
Cluster ID: UTX-CAMPUS-01
Pattern Classification: Anomalous
Activity Signature: Irregular manipulation detected
Status: FLAGGED FOR REVIEW
Note: Unusual metrics detected in structure utilization patterns. This cluster has been added to the monitoring queue for behavioral analysis. Continued anomalous activity may trigger escalated response protocols.
- System Integrity Division
Marcus stopped walking.
Read it again.
Flagged for review. Monitoring queue. Behavioral analysis. Escalated response protocols.
The System had noticed.
Not just noticed-formally flagged the entire cluster as exhibiting "anomalous" behavior. Irregular manipulation. The kind of language that suggested the System distinguished between normal user activity and exploitative gaming of its mechanics.
We saved a building, Marcus thought. And the System's response is to put us on a watchlist.
His deprecation timer read 48 hours, 13 minutes.
He pulled out his phone and screenshot the notification, then continued to the coordination center at a slightly faster pace.
Chen was already there-third floor analysis space, laptop open, coffee in hand, looking like he'd been awake for hours.
"You saw the notification," Chen said without preamble.
"Hard to miss. Blue text, priority flag, ominous implications about escalated response protocols." Marcus sat down. "When did it appear?"
"Around 2:00 AM, based on other people's reports. Julie was on night monitoring-she saw it first, woke me up." Chen pulled up something on his screen. "I've been documenting response across the cluster. Everyone got the same message. Cluster-wide flagging, not individual."
"That's worse."
"That's strategic." Chen leaned back. "The System isn't targeting individuals. It's monitoring the group. Watching for patterns of coordinated exploitation. Which means it's sophisticated enough to distinguish between one person finding an exploit and a whole cluster systematically applying it."
"Great. We're being analyzed by software that can recognize organized behavior." Marcus read the notification again. Escalated response protocols. "What do you think that means?"
"Unknown. Could be increased entity deployment in our sector. Could be restrictions on exploits we've found-like patching the lane marking trick or blocking the deprecation reversal. Could be nothing-just a warning shot to see if we change behavior." Chen's expression was unreadable. "The question is: do we?"
"Do we what?"
"Change behavior. Stop testing exploits. Stay under the radar."
Marcus thought about Building 2847, sitting stable with an Activity Index of 0.16 and no deprecation flag. Thought about the three other structures that could now be saved using the same methodology. Thought about his own countdown timer, ticking away in his peripheral vision.
"No," he said. "We keep going. The System's already watching-stopping now doesn't change that. And if we can't test exploits, we can't survive. The only way forward is understanding the rules well enough to play the game."
"Agreed." Chen pulled up a new document. "But we need to be smart about it. Document everything. Monitor for escalation signals. Accept that the cost of success is increased System attention. We're not playing under the radar anymore. We're playing under active scrutiny."
"Nothing I love more than being watched by omniscient software with unclear motives."
"Get used to it. You're officially interesting to the System now." Chen stood up. "Come on. We need to brief the council on the flagging and plan your deprecation reversal test. If we're being monitored anyway, might as well give them something worth watching."