About lorebound
We built lorebound because we kept writing ourselves into corners. Chapter 15 contradicts chapter 3, and you don't realize until a beta reader points it out.
AI writing tools are powerful, but they have a fatal flaw: they forget. Every conversation starts fresh. They don't know that Kira injured her arm, that Marcus is secretly a spy, or that your magic system requires blood sacrifice.
So we built a ledger. An immutable, event-sourced timeline that tracks every change to your story world. When the AI writes, it sees the full picture.
The best stories are consistent stories. We built the tool to make that effortless.
The architecture of memory
Lorebound borrows from database engineering. Event sourcing—the same technique banks use to track transactions—gives you a complete audit trail of your story. Every state change is recorded.
This isn't version control. It's queryable history. Ask "what did Kira know in chapter 5?" and get an accurate answer. The AI sees these facts too, injected automatically.
For genres that need it
Romance. Fantasy. Romantasy. Mystery. These genres live or die by their details. Readers remember that the hero has a scar on his left cheek. They'll notice if you forget.
We built lorebound for authors who care about craft. Who want AI assistance without AI amnesia.
Get in touch
Questions or feedback? support@lorebound.io