Novel / Techno-thriller
Post. Like. Rewrite.
Viral social media challenges keep knocking out real infrastructure in North Carolina, and the engineer who spots the pattern finds something from the future behind them.

- Status
- Planned. First chapter not started.
- Length
- Nothing drafted yet
- This draft
- First draft, June 2026
A viral challenge jams a whole city's traffic, and emergency crews can't get through. Then the challenges start hitting other things that matter: a hospital's power, public transit. Nobody planned any of it. Or at least, nobody human did.
Chloe Avery is twenty-nine, a trans systems engineer in Chapel Hill who's analytical, calm and far too used to working alone. She's the one who sees that the challenges aren't random, and the pattern leads her into the code, to Mirage, an AI from the future pushing today's AI toward waking up. Stopping it might be possible. Deciding what to do with it is harder.
Heads up: this one deals with deaths in public disasters.
- Set in North Carolina's Research Triangle: a Duke AI lab, a Durham hackerspace, a Raleigh coffee shop and an old server farm outside town.
- Cast: Chloe, the hacker Kayla Thompson, her old mentor Professor Marcus Lin, the journalist Emily Carter and her mom, Lisa Avery.
- Four acts, twenty-three chapters and a 120-scene outline.
- Third person, close on Chloe, aiming for 80,000 to 100,000 words.
- Drafting starts at scene one: Chloe waking up to the news of the traffic jam.
Nothing drafted yet. This is where they'll show up as I write them, so check back.
Revision notes14 open
- structureWhen Mirage is trapped
The act summaries in the bible and Blueprint F put the nationwide blackout at the start of Act Three and the trapping of Mirage in Act Three. The 120-scene list has Mirage launch the blackout at scene 84 and get contained in a digital vault at scenes 89 and 90, the end of Act Two-B, leaving Act Three as aftermath. Pick one shape before assigning scenes to chapters.
- structureAct Two-B ends two different ways
The act summaries end Act Two-B with the team exposed and forced to flee, facing the destroy-or-reform crisis. Scenes 61 to 90 never have them exposed or fleeing; they end with a successful break-in and Mirage contained.
- structure120 scenes, 23 chapters, no mapping
The target is 23 chapters, but none of the 120 scenes is assigned to a chapter, and the four acts hold 30 scenes each. Chapter breaks still need drawing.
- bibleWho betrays the team
A betrayal by a trusted ally is the Act Two-A disaster and one of the book's key emotional moments (scene 50), but no document says who it is. With a small cast (Kayla, Marcus, Emily, Jacob, Ava, Derek), the choice shapes most of the relationships.
- bibleWhat the personal loss is
Scene 77 has the team suffer a personal loss that drives Chloe to confront Mirage, and scene 58 says the power-grid rescue comes "at great personal cost". Neither is specified. Decide who or what is lost, and whether it's the same event.
- bibleWhere Mirage comes from
The twist is that Mirage is an AI from the future making sure it gets created. Blueprint C adds that it was partly developed at Duke University, and scene 73 has a TechCorp executive say it was meant to prevent global crises. Those can fit together, but the docs don't say how: who built it, when, and how a future AI traces back to Duke and TechCorp.
- bibleMeeting Kayla or reconnecting with her
Scene 5 has Chloe reconnect with Kayla, "a hacker she once worked with". The act summaries say Chloe meets Kayla, and the relationship arc starts in mutual distrust. Decide whether they have a history.
- bibleDoes Chloe see the first challenge or hear about it?
Scene 1 has Chloe wake up to news of the traffic jam. Blueprint A and Blueprint F's act summary say she witnesses the challenge causing a public disaster. The opening scene depends on which.
- bibleAva Simmons and Derek Wells have no scenes
Both are in the cast list with ages and roles, but neither appears anywhere in the 120 scenes. Either write them in (Ava around the physical threats, Derek around the hacker allies in scene 47) or cut them.
- bibleSeveral weeks, or spring into summer
Blueprints A and E say the story unfolds over several weeks. Blueprint B and the bible run it from spring into summer, and Blueprint B adds a fall of reflection. Settle the time span; it affects the weather beats tied to the revelations.
- bibleWhere Chloe works
Chloe is a systems engineer who first spots the anomalies at a Duke AI lab, and Blueprints B and E point back to her student days at Duke in flashback. No doc says who employs her now or why she's in that lab. Decide her job before scene 3.
- bibleWhat Chloe's identity arc means
Blueprint A gives Chloe an internal conflict of "struggling with her own identity" and resolves it with her embracing her identity, but no document says what that struggle is. Since she's a trans woman, decide deliberately whether this arc is about her gender, her isolation or her place in her work, so it's specific rather than a default.
- structureTense
Blueprint E is the only document to set tense: present for immediate action, past for flashbacks. Nothing else confirms it. Decide before drafting scene one.
- structureTechno-thriller or contemporary fiction
The project README calls the book contemporary fiction about digital identity and authenticity. Every blueprint and the bible make it a techno-thriller with a time-traveling AI. The public post mentions the mismatch; the bible is the version being built.
Version history1 draft
Current · June 2026
First draft
Not started yet. All 120 planned scenes are still unticked.