Canon
World facts, tone, entries, rules, and relationships need a source of truth so the world does not contradict itself by accident.
The idea
A garden for coherent worlds
Most worldbuilding tools store notes. Canon Garden is for the next problem: keeping a world coherent as it grows. It treats a world as something with memory, rules, public paths, private roots, and a controlled way to become visible.
The aim is simple: build the framework first, make it beautiful second, and only make it animated or playable when the structure can safely hold it.
What it holds
Canon, boundaries, and paths
Boundaries
Private notes, drafts, spoilers, hidden material, and unfinished ideas must stay private until the framework deliberately allows them out.
Paths
Readers should not be dumped into a folder. They should be guided through a world by safe public routes, clear order, and readable context.
How it works
Nothing becomes public just because it exists
Canon Garden is being built around gates, registries, validators, smoke checks, and publication rules. A file can exist without becoming public. A feature can be planned without being active. A world can be private until the framework is ready to show it properly.
- Source files are checked before they become public output.
- Routes are intentional, not accidental folder exposure.
- Future features stay off until their safety layer exists.
- The public site currently shows the framework story and roadmap only.
Where it goes
From quiet framework to playable worlds
The long-term idea is a place where people can build complete worlds, play inside them, connect compatible worlds through doorways, and later use a completed world to help write stories from its own canon.
That future is deliberately phased. The roadmap tracks what is done, what is in progress, and what is not yet active.