Local novel infrastructure

BOOKVAULT
YOUR WHOLE BOOK IN CONTEXT

Capture manuscripts, characters, canon decisions, and timelines inside a private operating system that lives on your hardware. Ask questions about your book, surface continuity notes, and keep months of work in one memory that never leaves your machine.

What BookVault holds

Projects

Multiple manuscripts, outlines, and style guides — all locally indexed.

Characters

Roles, relationships, arcs, and reference notes in one searchable layer.

Canon decisions

Every "why" recorded, with rationale you can revisit before you break continuity.

Your manuscript, held whole.

BookVault started as a tool for a novelist who kept losing track of character decisions across drafts. So we built a dedicated, local-first workspace: every decision, every character, every research scrap tied back to the same manuscript. No syncing, no SaaS logins, no risk of an API change destroying your canon.

Canon console

Structured log for decisions, retcons, and world rules. Tag them by act or POV and query them before changing a scene.

Character memory

Keep bios, relationships, emotional beats, and wardrobe notes accessible mid-draft. BookVault keeps it searchable.

Timeline + docs

Scenes, outlines, and manuscripts sit beside a chronological event log so you can reason about continuity at a glance.

Ask about my book

A private console that answers questions about your manuscript using your local model. Nothing leaves the machine.

Your hardware, your model

BookVault ships as a local FastAPI + SQLite application with a slim frontend. We deploy it on the same hardware that runs your Continuity stack so you can maintain it alongside everything else.

Under the hood

  • SQLite for manuscripts, characters, and decision logs.
  • Ollama / local LLM for the Q&A console.
  • Docker + systemd for repeatable deployments.
  • Manual backups or sync to wherever you archive drafts.

Part of a Continuity build

BookVault is available as an add-on to Continuity Systems deployments or as a standalone engagement if all you need is the writing environment. We install it on-site, validate the memory flows, and leave you with scripts to export, reset, or extend it later.

Ready when you are

Tell me about the book you’re working on, the hardware you trust, and what needs to stay consistent. I’ll send back an intake for BookVault or the broader Continuity stack.

Start a conversation See Astrid case study