The bunk was fine - better than fine, actually, compared to his apartment's IKEA mattress that had developed a permanent depression shaped exactly like his body. The cluster had converted a UT dormitory into emergency housing, and whatever students had lived here before the System arrived had invested in decent bedding. The pillow actually had structural integrity. The sheets smelled like industrial detergent rather than three weeks of unwashed despair.
But his brain wouldn't stop running.
The solid lines. The pathfinding constraint. The way the Spawns had responded when he'd tested the boundary. The timing of the override - thirty to forty seconds before the behavior anomaly triggered. The way the System had flagged his presence, tracked his movement, assessed threat levels in real-time.
It wasn't just a bug. It was a pattern.
And patterns meant there were more. Hidden in the System's architecture, waiting to be found by anyone who knew how to look.
Marcus pulled up his status screen in the darkness, letting the soft blue glow illuminate the ceiling of Bunk 247. Through the thin walls, someone was snoring - a rhythmic, mechanical sound that somehow made the silence feel louder.
[Quest Active: Evacuation Protocol]
Progress: 100%
Status: Complete
Reward: Survival (claimed)
The quest had auto-completed when he'd entered the campus safe zone. No fanfare, no XP notification that made you feel like you'd accomplished something meaningful - just a quiet status change, like someone had updated a database field from "in_progress" to "complete" and moved on to the next record.
Which was interesting, because the System loved notifications. Every action, every level gain, every minor achievement triggered some dopamine-optimized message designed to make you feel like you'd done something worth doing. User engagement 101. Keep them hooked with constant feedback.
So why skip the reward ceremony for completing your first real quest?
Hypothesis: Evacuation Protocol is considered baseline expectation, not achievement. System doesn't reward you for meeting minimum viable performance.
Marcus filed it away in the mental repository that had replaced his whiteboard. Added it to the growing list of observations about how the System structured its feedback loops, what it chose to highlight and what it treated as unremarkable.
Through the window - real glass, not the depression-era wire mesh his apartment had featured - the UT tower glowed faintly against the night sky. Someone had gotten the emergency lights working, probably repurposing a backup generator that had been installed for hurricane season and never expected to outlive civilization. Around the tower, the cluster sprawled across several blocks: barricades marking the perimeter, watch fires burning at the corners, the low hum of two hundred people existing in close proximity.
Two hundred people, give or take, trying to survive a performance review from something that might be God or might just be really aggressive enterprise software.
Marcus was betting on the software.
He closed his eyes and tried to think like a developer.
If I built a system that managed millions of users across a planetary deployment, how would I optimize it? What shortcuts would I take to make it scale?
Reuse existing data structures - don't build new ones when you can repurpose infrastructure that's already there. Road geometry as pathfinding constraints. Building databases as deprecation targets.
Batch processing - don't evaluate every user action individually when you can queue them up and process in bulk. More efficient. Less resource-intensive.
Lazy evaluation - don't compute anything until you absolutely have to. Delay decisions. Cache results.
All the tricks that made software scalable also made it predictable.
The System wasn't magic. It was engineering.
And engineers made mistakes. They shipped with bugs. They implemented quick fixes that became permanent technical debt. They hardcoded values that should've been configurable. They reused code from old projects without checking if the assumptions still held.
Marcus had spent ten years finding those mistakes. Documenting them. Exploiting them in test environments to prove they could be exploited in production.
The System was just the biggest test environment he'd ever worked with.
And it was definitely production code that should've never left beta.
Morning in the cluster arrived with the smell of questionable coffee and the sound of two hundred people trying to organize themselves into something resembling a functional society.
Marcus gave up on sleep - his deprecation timer read 67 hours, 14 minutes, counting down with the inexorable precision of a cron job - and made his way to the communal bathroom.
The showers still worked, which was one of those small miracles that made you wonder what infrastructure the System actually needed to function. Power was on. Water was on. Sewage worked, as far as Marcus could tell without investigating deeper than he wanted to. But internet was sporadic at best, cell towers were dead, and GPS had stopped working around Day Four.
The System needs human infrastructure but not human communication networks, Marcus noted mentally. Implies it has its own communication layer. Probably doesn't want users coordinating too effectively.
The shower was lukewarm and lasted exactly four minutes before the water shut off automatically. Someone had installed a timer, probably to prevent people from monopolizing the hot water. Good systems design, actually. Enforce limits at the infrastructure level rather than relying on users to self-regulate.
Marcus dried off with a towel that smelled like industrial bleach and made his way to the dining hall.
The dining hall was chaos.
Not the violent kind - the organizational kind, which in some ways was worse. Lines had formed, though nobody seemed to agree on what they were lines for. Someone was trying to implement a ticket system using handwritten numbers on scraps of paper. Someone else was arguing that the ticket system was unnecessarily complex and people should just queue like civilized humans. A third person was suggesting they implement assigned meal times based on bunk numbers.
Marcus recognized the pattern immediately: three engineers in a room, four opinions about architecture.
He found the back of what appeared to be the breakfast line and settled in to wait.
The woman in front of him turned around. She was maybe sixty, gray hair pulled back in a practical bun, wearing a fleece jacket that had a faded "UT Athletics" logo. Her status screen, visible at the edge of Marcus's perception, showed Level 3 Crafter.
"You're new," she observed. Not hostile, just stating facts.
This book is hosted on another platform. Read the official version and support the author's work.
"Arrived yesterday. Token 247."
"Eastern edge dorms. Not bad. Better than the gym overflow." She shifted her weight - her stance suggested knee problems, the kind that came from age more than injury. "I'm Helen. Been here since Day Six."
"Marcus."
"What's your story, Marcus Token 247?"
He'd learned in the past three weeks that "what's your story" was the apocalypse's version of "what do you do for a living." A way to categorize people by their survival value rather than their pre-System credentials.
"Logician class. Analyst archetype. My building got deprecated, so I walked here from East Austin."
Helen's eyebrows rose. "East Austin? That's... what, three miles?"
"Closer to two point six. But yes."
"Alone?"
"Until the underpass. Met someone from the cluster. She helped with the last mile."
"Entity encounters?"
Marcus thought about the Stalker on the rooftop. The Swarm circling 6th Street. The seven Spawns in the underpass that had tested the lane marking boundary until one had glitched through. "Several. None that ended badly."
"You got lucky."
"I got smart. There's a difference."
Helen studied him for a moment, reassessing. "You're going to fit in with the library group."
"That's the analysis team?"
"Among other things. Chen runs it - Level 4 Logician like you, but Strategist archetype. He coordinates research, collects data, tries to figure out what the hell the System actually wants from us." She paused as the line shuffled forward. "Fair warning: the library group burns through people. Too much thinking, not enough surviving. Some folks can't handle the cognitive load while their deprecation timers count down."
Marcus's status screen flickered at the mention.
Status: Active (DEPRECATED - 67h 09m remaining)
"I've got sixty-seven hours," Marcus said. "I'm planning to use them."
"Good." Helen nodded approvingly. "The ones who shut down are the ones who give up. You don't strike me as the giving-up type."
"I'm the 'be annoying about documentation until someone fixes the bug' type."
"Close enough."
They reached the front of the line. Breakfast was oatmeal - the instant kind, mixed with water because fresh milk was a luxury that belonged to the before-times - and something that might have been powdered eggs reconstituted into a substance with approximately the right color and texture if you squinted. Marcus ate it anyway. Calories were calories, and his STR 8 body needed fuel.
He found a spot at one of the long tables and pulled out his phone. 64% battery. The charging station was in the library, according to the orientation sheet they'd given him with his token. He'd need to get there soon.
But first, he opened his notes app and reviewed yesterday's observations.
EXPLOIT CONFIRMED: Solid Lane Markings
Description: Low-level entities (Glitch Spawns, tested; Stalkers, untested) cannot cross solid white lane markings. Appears to be pathfinding constraint - System is using road geometry as collision data.
Reproduction: Stand between solid lane markings. Entities will approach but stop at boundary.
Limitations:
- Time-limited (30-40 seconds before override triggers)
- May not work on higher-level entities (untested)
- Requires clearly marked roads (worn paint may not register as valid geometry)
Applications: Highway travel, underpass navigation, temporary safe zones
Questions:
- What determines override threshold? Time-based? Frustration metric?
- Do other road markings work? (crosswalks, stop lines, turn arrows)
- Can players create artificial boundaries using paint?
Status: REPRODUCIBLE, HIGH VALUE
Good documentation. Questions listed. Follow-up tests identified.
He added a new entry.
OBSERVATION: Quest completion feedback
Evacuation Protocol auto-completed with minimal notification. No XP fanfare, no achievement unlock, no "congratulations" messaging. Status just changed from "in progress" to "complete."
Contrast with normal System behavior: usually over-communicates achievements, leverages dopamine feedback loops.
Hypothesis: Quest was baseline expectation, not achievement. System doesn't reward minimum viable performance. Implications for quest design: it distinguishes between "required" and "optional" objectives at the reward level.
Follow-up: Compare reward structures for other quests. Do all baseline survival quests skip fanfare?
His oatmeal was gone. The powdered eggs sat half-finished on his plate, and he couldn't bring himself to eat more. They tasted like sadness mixed with chemicals.
Marcus cleared his tray, deposited it in the washing station - someone had organized a whole system, complete with gray water recycling - and headed for the library.
The walk across campus gave Marcus his first real look at the cluster's organization.
People moved with purpose. That was the first thing he noticed. Not wandering, not aimless - moving with specific destinations and tasks. A group carrying crates toward what looked like a supply depot. Two people with clipboards doing rounds of the barricades, checking structural integrity. Someone with a Level 5 Scout designation marking a map.
The barricades themselves were impressive in a post-apocalyptic engineering kind of way. Someone with actual construction knowledge had designed them - probably multiple someones, working together. Cars formed the base layer, positioned to create interlocking defensive positions. Furniture and building materials filled the gaps. Rebar and chain-link fencing reinforced the top.
It wasn't pretty. But it was functional, which was better than pretty.
Marcus spotted guard posts at regular intervals. Most were staffed by people whose status screens showed combat classes: Enforcers, Wardens, a few Guardians. Level 4 to 7, mostly. High enough to handle entity encounters without dying immediately.
Kira was at one of the posts near the library entrance. She spotted him and gave a small nod - acknowledgment, not greeting. Marcus returned it. She'd saved his life yesterday. That bought her at least a semester's worth of nods.
The library building itself was classic UT architecture: brick and glass, large enough to hold hundreds of students back when studying was something people did for reasons other than "figuring out how to not die." Now it held something else.
The entrance had been fortified. Heavy tables blocked the ground-floor windows. The main doors were propped open but guarded - a bored-looking Level 3 Warden sat reading a paperback, machete across his lap.
"Library's open access," he said without looking up. "Analysis team is third floor, east wing. Coordination is second floor, west wing. Don't touch anything in Special Collections unless you want Chen to murder you."
"Noted," Marcus said.
Inside, the library smelled like old books and ozone and the particular scent of too many people working in close quarters with inadequate ventilation. The emergency lighting was on - someone had rigged the backup generators to support critical infrastructure - casting everything in a harsh fluorescent glow that made Marcus's eyes water. Beneath the voices and paper-shuffling, the building's generators maintained a constant low-frequency hum that made his teeth ache.
The ground floor was crowded. People working at tables, spreading out maps, having quiet conversations. Someone had set up a charging station using solar panels and car batteries, the kind of jury-rigged solution that suggested either an engineer or someone who'd watched a lot of YouTube tutorials.
Marcus plugged in his phone and headed for the stairs.
The second floor was quieter.
More organized, too. Someone had implemented actual office-style organization: desks arranged in clusters, whiteboards on rolling stands covered in handwriting, filing cabinets that looked salvaged from UT's administrative offices. One wall had a massive map of Austin pinned up, marked with colored pins and string connecting different locations.
Marcus paused to study the map.
Red pins: deprecation sites. He counted seventeen, including his building and Building 12. All on the eastern side of the city, forming a rough cluster.
Blue pins: safe zones. The UT cluster. Two others - one near the Capitol, one south near Zilker Park.
Yellow pins: entity hot spots. The I-35 corridor had a lot of yellow.
Green pins: resource locations. Grocery stores, pharmacies, hardware stores. Most had lines drawn through them - already looted.
Someone had written notes directly on the map in permanent marker: "High spawn density after dark," "Stalkers patrol rooftops," "Avoid Lamar after 8 PM."
This is good data collection, Marcus thought. Someone's actually doing systems analysis.
"You're the new Analyst."
Marcus turned. The speaker was a woman, maybe late twenties, Southeast Asian, with black-framed glasses and the kind of intense focus that suggested she'd been surviving on coffee and spite for at least a week. Her status screen read Level 3 Logician, Synthesist archetype. She had a habit of tapping her pen against her notebook in a precise rhythm - three beats, pause, repeat - like her brain was processing in the background.
"Marcus Webb," he introduced himself.
"Julie Tran. Archivist." She said it like a title rather than a description. "Chen said you figured out the lane marking exploit independently."
"Pattern recognition. Observed entity behavior, formed hypothesis, tested it."
"And nearly died when the override triggered."
News traveled fast in a cluster of two hundred. "Learning experience. Now I know the safe duration threshold."
Julie's expression shifted slightly. Not quite a smile, but approval. "Chen's going to like you. He gets tired of people who need their hand held." She gestured toward the stairs. "Third floor. He's expecting you."
Marcus climbed to the third floor and immediately understood why Chen had claimed it for analysis work.
The space was quiet.
Not silent - there were people working, keyboards clicking, the rustle of paper - but quiet in the way a good library reading room was quiet. The kind of focused silence that let you think without distraction.
The third floor was smaller than the first two, which helped. Study carrels lined the windows, most occupied by people bent over laptops or notebooks. Whiteboards covered every available wall space, dense with handwriting that ranged from neat technical documentation to frantic brainstorming scrawl.
And in the center, at a desk that looked like it had been assembled from three different office furniture sets, sat Chen.