Richard Elliot

In development, private testing

StoryGecko

A story bible that keeps up with your manuscript.

The code is private while testing is under way.

The problem

Long fiction outgrows its author's memory. Eye colours drift, a side character's job changes between chapters, a thread opened in chapter three never closes. Writers keep a story bible to hold all of that, and keeping it current is a second job.

What it does

  • Reads an uploaded manuscript and drafts the story bible from it: characters, places, events and open threads.
  • Puts anything uncertain or contradictory into a review queue instead of guessing.
  • Offers “what happens next” suggestions grounded in what the story has already established.
  • A built-in writing editor is in progress, so the manuscript and its bible live in the same place.

The rule it follows

The writer stays the author. The bible changes only when the writer agrees to the change. When a chapter has been edited, StoryGecko asks before updating anything, and never rewrites the record on its own.

How it is built

  • Python and FastAPI on the server, with per-writer accounts and data.
  • Sign-in is built into the app, with no third-party identity service.
  • Developed against my own novella as the test manuscript, now with a first outside tester.