All originals
Creator toolsShipped 20255-week sprint

LoreSync

A story bible that stays true across every chapter.

Scroll for the technical layer
Layer 01 — The world

An unfolding blueprint of an invented world, ink lines catching a single violet light.

Worldbuilding infrastructure for writers and game masters: characters, places and canon that refuse to contradict each other.

Interface01
Motion02
System03
Layer 02 — The build

X-ray the interface. See the engineering.

The challenge

Creators keep canon in five documents and their head. Contradictions surface in chapter nine, and the fix costs a weekend of rereading.

Architecture decisions

  • 01Entity-first canon model: characters, places, factions and events with typed relations.
  • 02Every prose reference resolves to a canon entity, so contradictions are detected at write time.
  • 03Version history per entity with branchable drafts for alternate timelines.

Build process

Week 1Audited three novelists' real canon documents.
Week 2Prototype: one entity page, linked everywhere.
Week 3Contradiction detector and history.
Week 4Draft branching and export.
Week 5Ship to 60 writers, publish the canon format.

Stack

Client
React · web-first
Model
Typed canon graph
Editor
Rich text with entity linking
Sync
CRDT drafts, per-entity history

From the codebase

// Prose resolves against canon, so contradictions surface at write time
link(writing, canon.character("Mira")) // → conflict: eye colour

Measured results

0

canon contradictions undetected

5wk

idea to public beta

3.4×

faster continuity checks

The technical layer holds the challenge, the architecture decisions, the week-by-week build and the numbers. Open it when you want to judge the engineering, not the screenshots.