Local Admin

By the time the sun actually cleared the fog, Priya had made her three copies of the drive — one with a media lawyer she'd worked with on a defamation scare years back, one mailed, absurdly, on physical paper printouts to her own mother's house upstate, one sitting on a server Mara helped her choose specifically because it belonged to nobody Harbor Nine's usual players would think to look at. And Harbor Resilience Partners, exactly as Mara predicted, had already begun the work of making the night's chaos look like something else entirely.

"They're calling it an equipment failure," Priya said, reading from her phone at Mara's kitchen table, voice flat with disbelief. "A joint statement. Harbor Resilience Partners commends the swift response of municipal crews in containing an unprecedented cascading failure across dockside systems. There's a quote from someone at City Hall thanking them for their partnership."

"They're not wrong that crews responded fast," Mara said. "They're just leaving out that the crews were us, and that the failure wasn't unprecedented, it was scheduled."

"They're already positioning for the multiplier," Ilya said. "This is exactly the four incidents from Priya's spreadsheet. Emergency response, retainer payout, everybody claps."

Mara had been quiet for the better part of an hour, staring at her own old shadow-stack dashboard, the one that had paged her back into this mess nine days ago with a single stubborn alert nobody else remembered existed. It occurred to her, watching the graphs still faithfully logging every packet that crossed the harbor's public infrastructure, that she'd been thinking about this all wrong.

"We keep trying to get this evidence to people who might act on it," she said slowly. "Regulators. Journalists. Auditors. All of whom take time, all of whom can be delayed, discredited, or quietly persuaded that the intern who flagged it was mistaken. Harbor Resilience Partners has spent eight months building infrastructure to manufacture crises faster than any oversight body can review them."

"So what's the alternative?" Priya asked.

"We stop asking people to believe us," Mara said, "and just show them."

She pulled up the shadow stack's old admin panel — the same forgotten Vitriform relic that had first caught the anomaly, still technically hers by an authentication chain nobody had bothered to revoke. It had been built, originally, as an internal monitoring tool, never meant for public eyes. But it could render data. It could plot timelines. And critically, it still had a legacy public-facing status page, a relic from an era when Vitriform had briefly tried to look transparent to city contracts by publishing uptime statistics nobody ever read.

"Nobody's looked at this status page in years," Mara said. "It's still live. Still technically authorized. I can push whatever I want to it without asking anyone's permission, because as far as the system knows, I still work here."

"You want to publish the evidence on a dead uptime page," Ilya said.

"I want to publish the evidence somewhere Harbor Resilience Partners doesn't think to look, on a channel that predates their entire operation, using access they don't know still works." Mara was already building the layout as she spoke — a timeline correlating every declared incident with the retainer contract's multiplier triggers, overlaid with the actual packet traces from the tide gates, the crane yard, the seawall exchange, annotated in plain language a City Hall clerk could follow without an engineering degree. "It won't have the reach of a news outlet. But it'll be real, it'll be dated, and it'll be timestamped in a system Harbor Resilience Partners doesn't control and can't quietly edit after the fact."

Priya leaned over her shoulder, reading the draft layout with the practiced eye of someone who'd spent a career making complicated things legible to tired audiences at midnight. "You need a hook," she said. "Nobody reads an infrastructure timeline. People read a story. Lead with the crane. Lead with the worker who almost died last night, not the multiplier clause on page forty of a contract nobody will finish reading."

"I don't have his name."

"I do," Priya said. "Sector 7 supervisor gave a statement to the internal safety line an hour ago, official record. It's how I know they're already trying to bury it as equipment failure — because his statement doesn't match their story, and somebody's going to have to make it disappear or explain the discrepancy." She met Mara's eyes. "Use it. He'll back it up if it comes to that. I already asked."

They built the page together through the rest of the gray morning — Mara's technical timeline, Priya's structural instinct for what a stranger would actually read past the first paragraph, Ilya providing the ground-level detail neither of them had: which wire, which junction, which exact moment the crane's arc had gone from alarming to lethal and back. When it was finished, it read less like a leak and more like an indictment written in the calm, procedural voice of people who had simply decided to stop being quiet.

Mara's finger hovered over the publish control for longer than she expected.

"Once this is live," she said, "there's no version of tonight where I quietly go back to being unemployed and forgotten. They'll know exactly whose access did this. Whose name is on the authentication chain."

"Would you rather stay forgotten?" Priya asked.

Mara thought about the severance deck, the clean laptop wipe, the promise she'd made herself about machines belonging to men with cleaner coats than consciences — and thought, too, about the worker on the catwalk, close enough to the swinging container's arc that another four seconds either way would have written a very different ending to last night.

"No," she said, and pushed publish.

The old status page, dormant for years, blinked awake with a timeline it had never been designed to hold, timestamped and unkillable in a system that belonged, however briefly, entirely to her.