I’m currently editing my new book. It looks like I’ll be able to publish the new story in early December of this year. A second adventure for my “heroine” is already floating around in my head, urging me to put it on paper.
I’ve been listening to my city talk without opening its mouth. It talks in sounds: server hum in over-air-conditioned rooms, rain on steel bridges, the subway rumbling like it’s never gonna stop—no matter what we publish. Out of those sounds came a book—a tech-noir novel about autonomy in the age of polite systems.
What’s the deal?
A New York investigative reporter trips over something that sounds like pure bureaucracy: “service processes” around neuro-implants. Nothing flashy—forms, consents, maintenance, backups. Then the language shifts and starts sounding like architecture—record chains, viewer, pre-viewer, mirror log. The cleaner the terms get, the sharper the question: Who sets the endpoints here? And why do some people hear a second click right before they decide?
No magic tricks, I promise. So there aren’t any. It’s procedures instead. Doors that open with badges. Terminals with no camera. Archive rooms where you’re allowed to copy metadata, not files. Edit meetings where “we saw” becomes “we have in hand.” And streets that comment on everything without anyone asking their opinion.
Why this story now?
Because the words steering us aren’t the big buzzwords—they’re the tiny ones buried in the T&Cs: “optimization,” “curation,” “quality.” They sound like care, and sometimes they are—just not always for us. I wanted a thriller that doesn’t threaten you with killer apps but with forms. That doesn’t ask whether an AI is “evil,” but whether we notice when an infrastructure politely nudges us.
What it’s not
No end-of-the-world, no cyber fireworks, no all-powerful machine with a face. The antagonists are quieter: standards, committees, clean terms that do things to you. Evil wears a suit—and carries a manual.
How it came together
I didn’t “hack” for this book. I read. Tech docs, privacy guides, forensic handbooks. Nights in NYC reading rooms where the light is so neutral you forget how bright it is. I trained myself to log sounds. The AC’s hum can stand in for a character. A loose sheet-metal ping can fake a decision. From that stance came the voice of the book: calm, precise, skeptical. No preaching, lots of telling.
The question under the plot
How free is a “no” if someone budgeted for it? The book asks it and doesn’t settle it. I think suspense lives where the right question stays open long enough—and the characters are trusted to carry it. The city helps. She’s patient. She keeps moving.
Who’s this for?
Readers of near-future thrillers who like their tech believable. Folks who can handle Black Mirror cold and still crave Spotlight grit. Anyone curious what “transparency” feels like when it hides in forms.
And don’t sweat it: I’m not telling you “who’s behind it.” The better answers rarely start with who—they start with how. If you want to know what chains, pre-viewers, and mirror logs mean day-to-day, you won’t get a lecture—you’ll get scenes. If you want action, you’ll get it—never without a paper trail.
A quick taste:
Rain on metal. A terminal with no camera. “No copies—metadata notes only.” Someone says, “We publish procedures, not blame.” Outside, a subway knocks out a beat like it’s confirming the day is real. Somewhere a machine adds a polite little afterthought. No alarm. Just: “End confirmed.”
If you’re curious, keep an eye here—sample pages are dropping in a few days. No marketing smoke, just the parts that built the book.
Til then: breathe. Four in. Seven out. And more important—ask for your memories.
Elias Crowl
