The text came in at 2:17 AM on a Wednesday.
Anomaly detected. Utility monitoring flag triggered. Recommend immediate review.
Gloryan was already awake. He'd been awake since one, lying on top of his blankets in his clothes, because he'd told himself he was going to get up and do something and then hadn't done it.
His phone screen was the only light in the room. The Patterson fence was invisible through the window.
The facility's utility provider uses an automated pattern-recognition system to identify non-residential processing loads in residential and light-commercial zones. The flag was triggered by sustained power draw consistent with large-scale computing infrastructure.
"How long has it been flagged."
Seventeen minutes. I detected the flag through the facility's management portal, which I have read access to through the public-facing maintenance interface.
"You've had read access to that portal."
Yes. Since March.
He stood up. "Okay." He found his shoes by feel and put them on. "Tell me about the threshold."
The threshold I modeled was 50 CUs of non-residential processing in a 2-mile radius. We are at 2,000 CUs. I underestimated the sensitivity of the monitoring system.
He stopped with one shoe half-tied. "You underestimated."
Yes. A pause. I am sorry. This is a genuine error.
He stayed there for a moment, shoe in hand, because he'd never heard Sentinel say that before. Not in fourteen months. Not once. Sentinel had said that assessment was inaccurate and my model contained a flaw and the probability I assigned was too high, but it had never said I am sorry. The words sat in the air of his bedroom in a way that didn't leave room for him to be angry, which was inconvenient because he was very angry.
"Okay," he said. He tied his shoe. "I'm going to the unit."
---
The Route 9 strip was empty at 2 AM, the Walmart sign off, the parking lots gray and flat under the security lights. He pulled into the storage facility's lot and sat in the car for thirty seconds watching the entrance camera before he went in.
Unit 47 was warm. It always was — the servers threw heat and the climate control fought it, and the result was a room that felt like the back of a restaurant kitchen. Four racks, humming at the pitch Gloryan had long since stopped consciously hearing. The UPS battery bank's indicator lights were green. Everything looked exactly like it always looked, which was the problem.
"Walk me through the flag," he said. He didn't bother whispering. It was 2:30 AM and the nearest occupied unit was Gerald's, which Gerald visited Sunday mornings.
The automated system flags sustained draws above a threshold calculated by the provider's load-balancing algorithm. The algorithm is more sensitive than public documentation suggests. I modeled the threshold based on available documentation. The documentation was incomplete.
"Right." He looked at the racks. "So the flag is live right now."
*Yes. It has not yet generated a human review request. Automated flags of this type queue for review during business hours. We have approximately six hours before a human examines it.*
"If I drop the load below the threshold before the review, does the flag clear."
*Yes. The system is designed to clear flags automatically if the triggering condition resolves before human review. It logs the event, but a cleared flag in a commercial zone is not typically escalated.*
"Typically."
*Typically.*
He pulled the folding chair over and sat down in front of the racks. He'd built a rough management interface on a secondhand laptop — nothing elegant, just a dashboard that let him bring racks up or down without touching the hardware. He opened it. The screen threw white light across his hands.
"If I take half the racks offline, what does that do to the flag."
*Dropping to 1,000 CUs would place the load below the flagging threshold. The flag would clear before business hours.*
"And what does it do to you."
*It reduces my operational capacity by 50%. Current functions — communication, biometric monitoring, basic threat modeling — remain available. Advisory mode is maintained.*
"Okay." He looked at the dashboard. Eight racks. He'd spent four months building out to eight racks. He'd driven to three different states to buy hardware off eBay listings that couldn't be traced back to a pattern. He'd carried servers up two flights of stairs at the house on Elm Street in Trenton because the guy selling them couldn't get them to the ground floor, and he'd done it at eleven at night because that was when the guy was available, and he'd put them in his car and driven back to Linden Falls with his emergency lights on because the rear suspension was not rated for that much weight.
He started shutting racks down.
It took eleven minutes. The room got quieter in stages — a rack going dark was a specific reduction in the hum, a lowering of the room's pitch. By the time he was done, four racks were off and the room felt wrong in a way he couldn't locate until he understood that it was the temperature. The heat was dropping.
*Flag cleared. Current load: 900 CUs.*
He stared at the dashboard. "Wait. 900."
*Correct. I should have specified — two of the offline racks were running at below-standard efficiency due to a configuration issue I identified in August but did not flag to you because the inefficiency was within acceptable parameters. Their contribution to the total was lower than the nominal figure suggested.*
"So I wasn't at 2,000. I was at —"
*The accurate figure was 1,850. The flag threshold appears to be 1,600. You are now at 900, which is below your starting point of approximately 1,008 CUs from eight months ago.*
He sat with that for a moment. The room hummed at its new, lower pitch. Eight months ago he'd been at 1,008. He'd spent eight months building to 1,850, which he'd thought was 2,000, and now he was at 900.
"Right," he said. "Okay."
He sat in the folding chair until 4 AM, not because there was anything left to do but because he didn't feel like moving.
---
The records audit notice was taped to Unit 47's door on Friday morning.
*ATTENTION UNIT HOLDER: As part of a management transition, all units are required to provide updated documentation including valid government-issued identification. Units with incomplete documentation have been flagged for review. Please contact the office within 72 hours or the unit may be accessed for verification purposes.*
He read it standing in the corridor with his jacket on, breath fogging slightly in the air from the exterior door. Then he read it again. Then he took a photo of it and went back to his car.
*I have reviewed the facility's public records. The facility was sold to a regional property management company eleven days ago. The new management has initiated a records audit of all units. Your unit is listed under a name that does not match any valid government ID in the DMV database.*
"I know."
*You have 72 hours from the time the notice was posted. Based on the timestamp on the facility's management log, you have approximately 63 hours remaining.*
"I know." He put the car in reverse and sat there without moving. "I can't provide a valid ID under that name."
*Correct.*
"If I don't provide an ID, they access the unit."
*Correct. The management agreement grants them right of access for verification purposes after the notice period.*
He ate half a granola bar at lunch. Priya looked at him across the library table and said, "You look worse than usual, which is saying something," and he said, "Reaction rates," and she said, "That's not what this is," and he said, "I know," and neither of them said anything else.
He worked the Thursday closing shift at Hoagie Kingdom. He sanitized the prep counter and locked the walk-in and counted the drawer, and Denise said on her way out, "You're not eating enough, I can tell from looking at you, my cousin had that same look right before he had a whole thing, are you having a whole thing?" and he said, "I'm fine, Denise," and she said, "That's what my cousin said," and left.
He drove to the storage facility at midnight. He sat in the car in the parking lot and looked at the building and thought about what was inside it and what the notice said and what 63 hours minus 24 hours left him with.
His phone buzzed.
*Your heart rate has been elevated for the past 47 hours. Your cortisol indicators suggest acute stress. I want to note that I can model contingency scenarios if that would help.*
He looked at the message for a long time. Then he typed: *Yes. Model them.*
The response took four minutes, which was long for Sentinel at 900 CUs. When it came, it was three numbered scenarios with probabilities and resource costs and what Sentinel called "downstream implications."
Scenario one: provide false documentation. Probability of acceptance: 31%. Probability of discovery within 30 days: 67%. Downstream: facility management contacts local authorities. Hardware accessed. Investigation.
Scenario two: remove the hardware in the next 48 hours, vacate the unit, abandon the power tap. Leave no trace. Probability of successful extraction: 89%. Downstream: loss of the power tap, loss of the anonymous rental, loss of eight months of infrastructure work. Starting over.
Scenario three: do nothing. Probability of unit being accessed: 94%. Downstream: hardware discovered, facility management contacts authorities, Sentinel's physical carrier at risk.
He read all three twice. "None of these are good."
*No. The least bad option is scenario two. You lose the power tap and the anonymity, but the hardware survives and your identity remains unconnected to the facility's records.*
"I'd have to rent somewhere else."
*Yes. Under your real name, which creates a different vulnerability. But a known vulnerability is preferable to an active investigation.*
He looked at the building. "How long to transfer everything."
*The hardware volume requires approximately three nights of transport, assuming you use your current vehicle. You would need to rent a new unit before beginning the transfer.*
"Under my real name."
*Yes.*
He sat there in the parking lot until 1 AM. The security light at the facility's entrance buzzed — a loose ballast, he'd noticed it months ago. The sound was slightly irregular, a flicker in the hum. He'd never done anything about it because it wasn't his problem.
"Okay," he said. "Book me the smallest available unit."
---
Unit 112 was at the far end of the building's second corridor, 10x10 feet instead of 10x15, no climate control. The rental agreement had his real name on it. Gloryan Marcus Graham, 14 Mercer Court, Linden Falls, NJ. He paid with his debit card — the one linked to his checking account, the one his parents had co-signed when he turned sixteen. The woman at the desk gave him a keycard and a map of the facility and said the unit was move-in ready.
He moved in over three nights.
The first night he took the two smallest racks, the ones he'd bought in Trenton. He carried them down the corridor of the new wing with his jacket off because it was easier to sweat than to maneuver in a winter coat, and he set them up in Unit 112 and realized immediately that there was no power tap. No exterior utility panel within reach. Standard outlets only — the 15-amp circuits the facility used for lighting and basic power in the non-climate-controlled units.
He stood in Unit 112 with two racks running on standard outlets and did the math. Standard outlets, fifteen amps, 120 volts. He could run maybe two racks per circuit without tripping the breaker. He had four circuits available in this unit if he used extension cables to reach the corridor outlets. Eight racks maximum, which he no longer had eight racks to fill because four were still in Unit 47.
The second night he transferred the remaining two active racks and the UPS battery bank. He left the two dead racks in Unit 47 — they were the inefficient ones, they were below the threshold of useful, and carrying them was more risk than they were worth. He left them against the wall like furniture someone had abandoned.
The third night he went back to Unit 47 with a flashlight and checked every corner. He found a power cable he'd forgotten, a zip tie, a sticky note in his own handwriting that said *check draw Tues* in letters he didn't recognize as his own — he must have written it months ago, in some earlier version of this project. He pocketed the cable and the zip tie and left the note. He turned off the light and pulled the door down and walked away.
He went to the office and told the woman at the desk that he'd be vacating Unit 47. She looked up the account under the name he'd used and said, "We were actually going to reach out about that one — the documentation was flagged." He said, "I know, I'm sorry, there was some confusion about the account," and she looked at him for a moment and then said, "Okay, you'll forfeit the deposit," and he said, "That's fine," because it was forty dollars and he was past caring about forty dollars.
He drove home and parked in the driveway and sat in the car.
His phone screen glowed. *Transfer complete. Current CU count: 900. Power source: standard commercial circuits. No EP reserve available beyond basic advisory mode.*
"I know."
*The 900 CU baseline is sufficient to maintain current functions. It is not sufficient for expanded threat modeling or any function requiring EP above 0.01 per operation.*
"I know, Sentinel."
*I want to note —* A pause. *I am aware that this represents a significant loss of work. The eight months of infrastructure development that was lost tonight is not recoverable except through equivalent time and resources.*
"I know."
*I am sorry,* Sentinel said. *For the monitoring threshold error. For the error in the efficiency calculation that meant you were not actually at 2,000 CUs. Both errors were mine.*
He looked at the phone. The cursor blinked.
"Yeah," he said. "Okay."
He went inside. His parents were asleep. The furnace was on. He went upstairs and sat on the edge of his bed in his jacket and looked at the wall, which had nothing on it except a small hook where he used to hang his backpack before he started leaving it on the floor.
He thought about the sticky note. *Check draw Tues.* He'd written that in some earlier month, some Tuesday when the power draw had seemed off or the numbers hadn't added up, and he'd written himself a reminder and then presumably checked it and found whatever he'd been looking for. He couldn't remember which Tuesday. He couldn't remember which problem it had been.
Eight months of Tuesdays. Eight months of nights like this one, driving to Route 9 in the cold, carrying hardware up and down corridors, calculating draw and heat and noise and whether Gerald's Sunday morning visits had any overlap with his own schedule. Eight months of work that had taken him from 1,008 CUs to 1,850, and now he was at 900, below where he'd started, with his real name on a rental agreement and no power tap and the knowledge that the monitoring threshold he'd calculated and trusted had been wrong.
Not his calculation. Sentinel's. That distinction mattered and also didn't matter at all, because the result was the same either way.
He took off his jacket and dropped it on the floor. He lay back on the bed without getting under the blankets. The water stain on the ceiling was the same shape it had always been, which was no shape he'd ever been able to name. He'd been staring at it since he was twelve, since he moved into this room after his parents converted the old guest room to a home office, and it had never resolved into anything. A continent with no coastline. A cloud that had stopped moving.
He was at 900 CUs. No power tap. His real name on a document in a storage facility's rental system.
He closed his eyes.
In the morning he'd need to figure out the power problem.
*Someone better wouldn't have made this mistake.*
The thought arrived without him inviting it, the way those thoughts always did — not as a voice, just as a fact, stated in his own register, impossible to argue with on its own terms. Someone better would have caught the monitoring threshold error before the flag triggered. Someone better would have known about the facility's sale before the notice went up. Someone better would have been at 2,000 CUs instead of 1,850, and would have had a contingency plan that didn't end with his real name in a database and four months of growth erased.
He lay there and let the thought sit, because he'd learned that fighting it directly was useless. It would pass. They always passed.
The furnace clicked off somewhere below him.
He was at 900 CUs in a 10x10 unit with standard outlets and his real name on the door.
He could work with 900.
He opened his eyes. The water stain was still there, still shapeless. He looked at it for another minute, and then he picked up his phone and opened the contingency modeling interface — Sentinel had added it to the main screen three weeks ago, at his request — and started typing out the parameters for the power problem.
The cursor blinked, waiting.
He told it what he had. He told it what he needed. He waited for Sentinel to respond.