A Novel
72 hours to stop an assassination.
A lifetime of secrets behind it.
The Story
Verona, Italy. Eight nations are days away from ratifying the Verona Accords, the first binding international treaty to regulate lethal autonomous weapons systems. For the delegates gathered in the city's most storied halls, it is a historic moment. For Ambassador Helena Whitfield, the treaty's most visible champion, it may be her last.
A contracted shooter has been placed in Verona. Intelligence is fragmentary, the motive unclear, the principals unknown. An operative codenamed MERIDIAN is given a single mandate: identify the shooter before the summit concludes. 72 hours. What follows is a compressed, claustrophobic procedural (backstreet surveillance, layers of cover identity, and a cast of handlers and suspects each running their own agenda) as MERIDIAN works the city's margins while the clock runs down toward a bullet that may or may not be for the Ambassador.
Stopping the shot turns out to be the easy part. Understanding the architecture behind it (who commissioned the contract, why now, and what the Verona Accords were actually designed to protect) takes considerably longer. The trail leads from Verona's cobblestones to Vienna, from treaty text to shell companies, from a briefing room to a truth no handler sanctioned MERIDIAN to find.
"The face in the mirror is the reader's face.
MERIDIAN has no name, no gender, no history you haven't given them."
On the Protagonist Conceit
The Protagonist
MERIDIAN is a codename, not a person, at least not one the reader is allowed to locate. The operative is deliberately ungendered and unnamed. Pronouns are they/them throughout, not as a political gesture but as a craft decision: the blank-slate operative is one of the oldest conventions in spy fiction, and MERIDIAN takes it seriously.
The reader brings the face. They bring the gender, the backstory, the particular flavor of exhaustion that comes from doing this work for too long. What the novel provides is perception, judgment, and a very precise way of moving through a room.
The primary point of view is MERIDIAN's: close third-person, tightly controlled, never omniscient. Interleaved through the novel's 54 chapters are 15 POV interludes, each written from the perspective of a named handler or suspect: the other eyes in the room, the hands on the levers, the people who believe they understand what MERIDIAN is doing and are, in varying degrees, wrong.
The World
The Story Bible behind MERIDIAN is not a vague reference document. It is a structured intelligence architecture, the kind that could support a sequel, a game, or a trial.
Novel × Game
MERIDIAN the novel did not grow from an outline. It grew from Operation Meridian, the real-time spy thriller ARG architected solo in 24 days, with 88 scripted game events, five AI and API integrations, and 154k+ lines of code. The narrative architecture came first: the handler network, the three-tier antagonist hierarchy, the Verona Accords and the fragile coalition around them. The game was built on top of that canon. Then the novel pulled it back out.
This cross-medium design left fingerprints. The rotating POV interludes in the novel directly mirror the game's multi-handler architecture: each handler a distinct voice, each voice shaped by incomplete information about what MERIDIAN is actually doing. The classified-cable register that players received in-game was not invented for the ARG; it was extracted from the same operational grammar that governs how handlers speak in the novel. The Vienna sequence closes threads that players opened.
The two works are designed to be read in either order. The game rewards people who have read the novel. The novel rewards people who have played the game. Neither requires the other, but each one changes what you notice in the other.
Read the full 78,959-word novel as a PDF, or step inside the world and play Operation Meridian, the ARG built on the same canon.
© 2026 Chris Carrier. All rights reserved.