Creative Navigation
An engine for your story. Built around it. Run by you.
Creative Navigation is the process LUNA uses to write long fiction with AI while the author keeps every decision. It isn't a prompt or a trick. It's a set of documents that govern what's true in your world, what stays secret, what's been decided, and what good prose sounds like for you. In the class, you build your own.
AI can help with a scene. Over a whole series, it breaks.
And it breaks in the same five ways every time:
- It invents to fill gaps.
- It trusts whatever document it read last.
- It spoils secrets early, because nobody told it they were secrets.
- It drifts toward its own house style instead of yours.
- It forgets what you decided last session.
Creative Navigation puts a wall in front of each one. Your authorship isn't protected by hoping the AI is careful. It's protected by a system that makes carelessness visible.
Three laws sit above everything
Every file in the engine hangs from these. They are the first page you write.
No new ideas
Only the author's own concepts. No new characters, plot, lore, or props. Invention rarely hides in the plot. It hides in quantities, place names, dates, and furniture.
Amplify, don't improvise
Strengthen what exists. When something is uncertain, ask. A gap is never filled by guessing.
The author rules
You approve the direction before any work happens. Conflicts are flagged and wait for you. Once you rule, it's settled.
The engine, layer by layer
Each layer answers one question and stops one failure. Your engine won't have all of them on day one. It grows them as the story needs them.
The same engine at two ages
Archangel is an engine in its first month. Adeline: Dark Horse is a mature one. If you're just starting, your engine will look like Archangel's. Here's what changes as it grows.
Secrets
The files mark what's hidden, but nothing yet says when each secret may reach the reader. Any draft that touches one has to stop and ask.
A Hard Stops Registry. Every secret is permanent, gated to a named season, or lifted, with a table of which character knows what, and when.
Secrets are cheapest to protect before chapter one.
Decisions
Open questions live inside each file. Its first audit turned up fourteen of them, numbered and handed to the author. None were answered for him.
A Rulings Ledger. Fourteen numbered canon rulings, nine things that look like mistakes and are deliberate, and a log of the AI's own errors.
An open question starts as a note in a file. Once the author answers it, it becomes a ruling nobody reopens.
The craft standard
Polish Code v0. It holds only rules about how listeners hear prose. Every number is marked unmeasured and can't fail anything.
Polish Code v5.2, measured across 10 episodes and 111 chapters. Only the measures that separate the best work from the worst are allowed to fail a chapter.
The numbers are never borrowed. Archangel gets its own once there's prose to measure.
How each one breaks
Its audit found walls not yet built: no secrecy file, no ledger, no status tracker, no finished writing to measure.
Its audit found files that had fallen behind: a tracker still naming a craft code two versions dead as current, and a season file describing an episode the author had already redesigned.
A young engine fails by what's missing. A mature engine fails by what's out of date.
You don't build it all at once
Every file in Dark Horse exists because something went wrong without it. You get to skip the mistakes. This is the order that works:
- Write the laws and the authority chain.One page. Everything else hangs from it.
- Put everything you know into a world bible and a character bible.Flag the gaps. Don't fill them.
- Build the secrecy registry before chapter one.Secrets are cheapest to protect at the start.
- Open a rulings ledger and a status tracker on day one.They grow as the work happens.
- Finish one piece you love. Then measure it and write your craft code.A standard written before you have a specimen is a guess.
- Add a build spec the first time something ships wrong.
What makes it different
It keeps a list of what it doesn't know
Every file records its own open questions, and nobody fills them without the author. Archangel's files mark what winning looks like at the end of Book Three as undecided, and note that Book Two can't be built until it is. Dark Horse's craft code warns when one of its own standards rests on a single episode.
That list keeps the AI from filling gaps, and it turns the engine into a to-do list.
Your craft standard comes from your finished work, not from theory
Dark Horse's best episode was measured against its weakest with one fixed instrument. On the things writing advice usually obsesses over, they came out almost identical:
| Measure | Best episode | Weakest episode |
|---|---|---|
| Sentences of 10 words or fewer | 72% | 72% |
| Negation chains per 10,000 words | 77 | 75 |
| Figurative phrases per 10,000 words | 33 | 35 |
Those numbers describe the voice. They don't predict quality. What cleanly separated seven finished episodes from three failures, with no overlap, was paragraph weight:
| Measure | Clean episodes | Failures |
|---|---|---|
| Median paragraph length | 10–19 words | 20–24 words |
| Share of 81–120 word paragraphs | 0–3% | 4–12% |
A gate that does not separate the best work from the worst is not a gate. It is a preference with a number attached.
Your engine gets its standard the same way, from your own best work.
It names your premise's weak point
Every premise has a built-in way to break. In Archangel, the hero has no power ceiling, so any fight could collapse into him just getting stronger. The engine answers with a limit rule: he never loses because someone is stronger, only because he runs out, and every action scene has to state what it cost him.
Name the weakness early, and make every piece of work guard against it.
It's tested by ear
Dark Horse is published with narrated audio, and its author listens to every episode. Some defects read clean on the page and sound wrong out loud. "High. Young. Terrified." is heard as "Hi." A sentence that drops its subject makes sense to the eye, which carries the name across the period, and loses a listener, who can't.
Every defect the ear finds becomes a named rule with a check, so it's caught automatically next time. The measurements are necessary. They aren't sufficient. The last test is always to listen.
It audits itself
Once an engine grows past a handful of files, it gets a System Brief: one document that maps every file for a fresh AI session, including what's secret and what's still open. Writing it doubles as an inspection. Every contradiction between two files becomes a numbered question for the author.
The brief never settles those questions itself. It finds them while they're still cheap to fix.
You decide how much the AI touches
It's written into each project's operating rules. Whatever you choose, the author decides and the AI flags.
Skeletons only
How Archangel runs. The AI builds structural blueprints: each scene's purpose, entering and exiting state, the turn, and the cost. The author writes every sentence.
Gated builds
How Dark Horse runs. One chapter at a time. A skeleton is approved before any prose, and the author locks each chapter before the next one starts.
Build your own engine with LUNA
A class and one-on-one tutoring in Creative Navigation. You don't get a template. You get an engine built around your own story, and the understanding to run it and grow it.
- The tools to build your own Creative Navigation engine
- Every layer built for your world, your characters and your voice
- An understanding of why each piece exists, so you can extend it yourself
- A system that starts small and can grow as far as Dark Horse
Questions
Does the AI write my book?
Only as much as you allow, and it's written into your engine's rules. Either way, every creative decision is yours. The first law is no new ideas.
Do I need all of these files from the start?
No. Archangel started with six files and no prose. You build layers in order, as the story needs them.
My story is still just in my head. Is that too early?
No, that's a good time to start. The first files hold what you already know and list what you don't.
Do I need technical skills?
No. The engine is a set of written documents. If you can describe your story, you can build one.
Is this only for fantasy or long series?
Dark Horse is supernatural fiction and Archangel is cyberpunk. The layers are about how long work breaks, not about genre. The longer your story, the more layers it will grow.