Storybook Prototype

Preamble

Prototype keeps Storybook small enough to test. Use an authoring surface for world facts, rejected attempts, scene prompts, and evaluation before inventing a dedicated app.

---

The Surface Should Stay Humble

Storybook starts with a working vault, templates, links, and prompts. A dedicated app can wait until the writing workflow proves it deserves one.

world facts -> scene drafts -> author refusals -> evaluator notes -> revised context

That loop lets the author navigate the world and lets the model assemble context without pretending the interface has solved the writing.

Refusals Need A Shelf

The prototype should store more than accepted lore. It should keep discarded scenes, rejected tones, abandoned openings, cut characters, and notes on why each one failed.

Those records give the model access to authorial taste through elimination. The next draft can learn from what the writer refused and what the writer kept.

The First Proof Is Friction

The prototype should make the writing loop sharper: easier retrieval, clearer continuity checks, better context packs, and more visible refusals. A beautiful archive that delays the story has failed.