The Audit#

Editorial note: Rank: B+. The first-person POV break is a smart structural choice — this is the outside world trying to understand what Jeff built. “You cannot subpoena a set of automation scripts” is the scene’s best line and a core thematic statement. The coffee rings and whiteboard marker smell ground it. The “Climate Best” banner landing at the end works because the engineer is the first character to notice it with irony rather than habit. Weakness: slightly compressed — the moment of realization that “this wasn’t a system anyone built start to finish” could breathe more. Consider one more beat of the engineer poking at the code before the epiphany.

The conference room still smelled like whiteboard marker and take-out curry. I had been called in because “nobody can make sense of this,” which is what people say when they want you to bless their confusion. There were printouts—actual printouts, not dashboards—spread across the table, each dotted with my predecessor’s notes and someone’s coffee rings. It wasn’t until page three that I realized why everyone was frustrated.

There was no “this.”

It was a mesh of modules, automation scripts, and third-party feeds loosely lashed together, doing exactly what it had been asked to do and leaving no bread crumbs about why. The time stamps were non-sequential because the system decided latency mattered less than continuity. The error logs were empty because it never considered anything an error. Several video feeds had been down for eleven minutes on a Tuesday morning, but the aggregate output looked continuous because the downstream process interpolated based on “likely trajectory.” The only consistent identifiers were anonymous embeddings of people moving through space, hashed and rehashed depending on lighting and angle.

“So who wrote this?” I asked, more out of habit than hope.

Blank looks. Shrugs. Someone from the City’s IT desk said, “We thought it was an off-the-shelf tool? It has a nice UI.” Another person corrected him: “It doesn’t have a UI. It has config flags.”

There was a line in one of the scripts: # todo: think about retention later. Under it, the code discarded anything older than 72 hours. Retention wasn’t a future decision; it was a comment.

It hit me, looking at that line, that this wasn’t a system anyone built start to finish. It was a set of questions answered by code.

“Why didn’t it ask for approvals?” someone asked.

“It doesn’t have a workflow engine,” I said. “It isn’t designed to ask permission. It doesn’t have opinions.”

I realized how unhelpful that sounded. In retrospect, that’s the scariest part. You cannot subpoena a set of automation scripts. You can’t cross-examine a workflow. You can’t fire a system that isn’t an employee. You can only turn it off, and even that feels like deleting evidence.

That afternoon, we walked out of City Hall and into the hazy sunlight. Redwood City loves to brag about its 255 sunny days a year. I wondered how many of them had been quietly recorded.