Jordan Quinn Rivers
Author of The Morrison Protocol — a five-book techno-thriller series about surveillance, identity, and the terrifying cost of knowing too much.
“Every conspiracy starts with someone who knew too much — and someone who needed them silent. I write about the space between those two people.”
Jordan Quinn Rivers spent fifteen years working in data security and intelligence consulting before leaving to write full-time in 2015. That background — the classified briefings, the surveillance architectures, the human cost of systems designed to watch without being seen — is the foundation of everything in The Morrison Protocol.
The series began as a single question: what would it feel like to discover that a government program had been watching you your entire life — and that the people running it believed they were doing the right thing? That question became five books, a cast of characters Jordan describes as "the most morally complicated people I've ever spent time with," and a world that keeps expanding the more you look at it.
Last Witness, the first book in the series, took four years and seven drafts to complete. Jordan lives in the Pacific Northwest and is currently writing Book Two.
How the Books Get Made
Jordan's approach to writing The Morrison Protocol — from research to final draft.
Research First
Every book starts with 3–6 months of research. For Last Witness, that meant deep dives into COINTELPRO, PRISM, and the history of classified government programs. The technology in the series is extrapolated from real systems — nothing is invented from scratch.
Location as Character
Every city in the series was visited before it was written. The Berlin safehouse in Book One is based on a real building in Mitte. The New Orleans archive is modeled on an actual warehouse district. Place is never backdrop — it's always active.
Multiple Drafts
Last Witness went through seven complete drafts over four years. The first draft was 140,000 words. The published version is 387 pages. The cuts were the hardest part — and the most important.
Series Architecture
All five books were outlined before Book One was written. Every planted detail, every foreshadowed connection, every character who appears in Book One and matters in Book Five — it was all mapped before a single chapter was drafted.
The Road to Last Witness
Begins career in data security consulting
First short story published in a genre anthology
Leaves consulting to write full-time
First draft of Last Witness completed
Signs with literary agent; begins series planning
Last Witness published — The Morrison Protocol begins
Who Shaped the Writing
The authors and works that most directly influenced The Morrison Protocol.
John le Carré
The moral weight of espionage
Daniel Suarez
Technology as a thriller engine
Tom Clancy
Operational authenticity
Donna Tartt
Character depth in genre fiction
Richard Morgan
Identity and consciousness
Cormac McCarthy
Prose economy and tension
What Critics Are Saying
“Rivers writes with the precision of a systems architect and the instincts of a born storyteller. Last Witness is the debut thriller of the year.”
“A masterclass in controlled tension. Every chapter ends with you needing the next one immediately.”
“The Morrison Protocol is the kind of series that makes you feel like you've been let in on a secret. Compulsive, intelligent, and genuinely frightening.”
The Story Behind the Story
Six questions about where the Morrison Protocol came from, how it was built, and what Jordan Quinn Rivers actually wants you to feel when you read it.
Where did the idea for the Morrison Protocol actually come from?
It started with a real document. In 2013, I was doing consulting work for a mid-size data firm and I came across a reference — buried in a footnote of an internal audit — to a government program that had been quietly discontinued in the early 2000s. The program had a name, a budget line, and a three-sentence description that raised more questions than it answered. I spent six months trying to find out more and hit a wall every time.
That wall is what became the Morrison Protocol. Not the program itself — I never found out what it actually was — but the feeling of finding a thread and watching it disappear. Nathan Morrison is me in that moment, except he pulls harder than I did.
It started with a real document. In 2013, I was doing consulting work for a mid-size data firm and I came across a reference — buried in a footnote of an internal audit — to a government program that had been quietly discontinued in the early 2000s. The program had a name, a budget line, and a three-sentence description that raised more questions than it answered. I spent six months trying to find out more and hit a wall every time.
That wall is what became the Morrison Protocol. Not the program itself — I never found out what it actually was — but the feeling of finding a thread and watching it disappear. Nathan Morrison is me in that moment, except he pulls harder than I did.
“The Morrison Protocol is fiction. The infrastructure it describes is not. That gap is where I want readers to sit for a while.”
Get the next chapter of the story
Release dates, behind-the-scenes notes, and the occasional classified detail that doesn't make it into the books. No noise — just the signal.