Story Core

A story bible the AI actually reads.

Story Core holds your premise, themes, voice, cast, and outline in one place — and every AI suggestion is grounded in it. Not a folder of notes you maintain for yourself, but living context the Muse uses on every request.

One home for your book's truth

Premise, themes, voice notes, characters, and outline live together — not scattered across documents you forget to update.

Read on every AI request

Story Core isn't decorative. The Muse reads it before it writes, so suggestions stay consistent with your world and cast.

Grows with the draft

Update a character's arc once and every future suggestion respects it. The context evolves as your story does.

Notes that do work, not notes that gather dust

Most writers keep a story bible somewhere — a Scrivener folder, a Notion page, a notebook. The problem isn't keeping notes; it's that the notes never reach the place where you write. You still have to hold the whole book in your head while drafting.

Story Core closes that gap. It's the same premise-themes-cast-outline structure writers already keep, except it lives inside the editor and is fed to the Muse on every request. The context does work instead of gathering dust.

What lives in Story Core

Premise and themes — the spine of the book the AI keeps in view. Voice notes — the register and rhythm you want protected. Cast — characters with the traits, relationships, and contradictions that make their dialogue theirs. Outline — the structure, so suggestions know where the chapter is headed.

You decide how much to fill in. A one-line premise already sharpens every suggestion; a full cast and outline make the Muse feel like it has read your manuscript twice.

How it compares to a Story Bible or Codex

Sudowrite's Story Bible and Novelcrafter's Codex solve the same problem from different angles. Story Core's bet is integration over breadth: fewer fields to maintain, but every field is actually consumed by the AI as you write. (See how the products line up in Muze Writer vs Sudowrite and vs Novelcrafter.)

Story Core vs a static notes folder

Muze WriterNotes folder
Premise, cast, outline in one placeYesScattered across files
Read by the AI as you writeEvery requestNever
Keeps suggestions consistentYesUp to you to remember
Lives inside the editorYesSeparate app

Frequently asked questions

Is Story Core the same as a story bible?

It serves the same purpose — a single home for premise, characters, voice, and outline — but with one key difference: the AI reads it on every request, so your story bible actively shapes suggestions instead of just sitting in a folder.

Do I have to fill all of it in before I can write?

No. Even a one-line premise improves every suggestion. You can flesh out characters and outline as the draft grows; the Muse uses whatever is there.

How is this different from Sudowrite's Story Bible or Novelcrafter's Codex?

All three keep structured story context. Story Core prioritizes tight integration — fewer fields, but every one is fed into generation automatically — over maximal configurability.

Story Core — your premise, characters, voice, and outline in one place · Muze Writer