Replaces the v1.1 'world_id is a string' model with a graph-of-planes. Driven by Kay's Q2 ('worlds are planes') and the v1.2 design review.
- 17-planes.md (NEW): the plane taxonomy, the four relation types, Cypher patterns, migration from world_id, open questions
- 01-ontology.md: Plane and Setting as first-class nodes; the 6 plane-relation edge types
- 02-time-model.md: plane-aware time (entity_planes_at_time as the 6th time-aware primitive)
- 08-architecture.md: data flow for plane questions (the 'can I get from X to Y' pattern)
- 11-extensibility.md: how to add custom planes and plane-relations without code
- 12-storage-strategy.md: planes are pure graph (no Postgres/Redis/Qdrant/S3 changes)
- 14-examples.md: example 5 — full Setting + planes + Roland + Asmodeus + LLM tool calls
- README.md: v1.2 entry + doc 17 in the table of contents
The POC rebuild (T10) is the next step: migrate the existing 4 world_id values to Setting/Plane nodes and update the plugin queries to use EXISTS_IN/LOCATED_IN.
Researched 9 systems in the KG-RAG + LLM-reasoning space, with actual
abstracts, GitHub stars, and arXiv citations:
- Microsoft GraphRAG (33,779 stars, arXiv 2404.16130) — global summarization
- Cognee (17,843 stars, arXiv 2505.24478) — agent memory, cognitive ontology
- LightRAG (36,622 stars, arXiv 2410.05779) — graph-based text indexing
- Stanford Generative Agents (arXiv 2304.03442) — memory stream + reflection
- IVIE (arXiv 2606.13348) — neuro-symbolic interactive-fiction generator
- WikiChat (arXiv 2305.14292) — Wikipedia-grounded, 97.3% factual
- TKG methods (TLogic, Chain of History, TGL-LLM) — temporal forecasting
- Chain-of-Knowledge (arXiv 2306.06427) — in-prompt structured reasoning
- Long Story Generation (arXiv 2508.03137) — KG for long-form narrative
Critical findings:
- The Lore Engine's 'closed-world fictional ontology' niche is not crowded.
No system does time-aware, contradiction-checking, source-attributed
reasoning over a fictional world. That's the opening.
- BUT: GraphRAG/Cognee/LightRAG are 18-37k-star production systems.
The Lore Engine is a design. Maturity gap is the single biggest weakness.
- The right move might be: build Lore Engine on top of Cognee, not
GraphMCP-Example. Cognee is MIT, production, has paying users, and
closes 80% of the substrate gap in 2 weeks of integration work.
- The most leveraged next move: 1-week spike to validate the core
idea before committing to the 43-day build.
16-comparison.md is the honest assessment. Where the Lore Engine is
Worse is a direct list of 10 weaknesses; where it's Better is a
direct list of 10 strengths. Six debatable design decisions called
out for Kay to push back on.
