Canonical precision
Timestamps, case IDs, and record identifiers locked in the story bible before chapter one.
Near-Future Thriller
The system already decided.
Someone has to read the log.
Near-future thrillers treat institutions and algorithms as antagonists — not monsters. The engine enforces procedural precision, audit-trail evidence, and investigative escalation where every chapter advances what the record reveals.
Propulsive investigative fiction where the dread is systemic — a gap in the log, a decision no human witnessed, and a protagonist trained to treat discrepancies as evidence, not noise.
Pipeline
How we write Near-Future Thriller
Audit-trail architecture
Evidence arrives as logs, filings, and system outputs — fair-play for the reader.
System-as-antagonist
The threat is institutional: allocation engines, bureaucracies, algorithms acting at machine speed.
Investigative escalation
Each chapter must advance the external inquiry — new records, new witnesses, new gaps.
The contract
What readers expect
Reader promise
- A protagonist who trusts procedure more than intuition — until the procedure breaks
- Horror that is systemic, not supernatural
- Evidence that arrives as logs, timestamps, and official documents
- Stakes measured in milliseconds, case files, and lives already allocated
Engine enforcement
- CANONICAL_TIMESTAMP fields enforced in seed
- Procedural voice — precise, administrative, bleak
- System antagonist — no monster, no magic
- Investigative arc — each chapter advances the audit
From the manuscript
Sample prose
The Mercy Calculation · Chapter 1 — The 0.4-Second Gap
At 14:03:11 on a November night, a resource allocation system processed a mass casualty event in 0.404 seconds and reached a conclusion about an eight-year-old named Marcus Veil that no human being in the six-state network was notified of until it was finished.
The thermal printer clicked twice and stopped. Nora registered the silence before she registered the problem. The printer had been cycling every four minutes — she knew this without having counted — and now it sat quiet at the edge of Audit Station 4.
Four-tenths of a second. Not a rounding variance — the submission package used millisecond precision throughout, consistent to three decimal places across forty-two documented allocation events.
A 0.4-second gap meant the live stream captured an event that the static log placed 0.4 seconds earlier — which meant either the static log was wrong, or the live stream was wrong, or something had occurred in the interval that neither log was designed to capture.
Write your near-future thriller
today
Build the case file first. Let the system make the decision — then let your protagonist find the gap.
← All genres