Universe Author — .chronverse

Define a universe for your timeline — fictional, historical, or scientific. Set its temporal anchoring, default calendar, canon scopes, and related universes, then export a portable .chronverse file.

schemas.openchronology.org/v0.3/universe
Import .chronverse prefill form
📂
Drop a .chronverse file to edit it
or click to browse · .chronverse or .json
01 Universe Identity required
Stable key used in .chron references. Lowercase, hyphens only.
Where this file will live permanently. Enables cross-site referencing.
02 Universe Type required
Load preset →
Absolute Universe

This universe has its own independent time axis — it does not map to any other universe's timeline. Use this for fully original worlds, fantasy settings, and distant sci-fi galaxies. Events reference this universe directly, with no real-world date equivalent unless you choose to add one in the Epoch field of your calendar.

Temporal Anchor — required for relative universes
The universe this one is anchored to. Use real for the actual world.
ISO 8601 datetime in the target universe that corresponds to this universe's year zero.
03 Defaults optional

Default values inherited by any .chron event that references this universe and omits these fields. Saves authors from repeating boilerplate in every event file.

Machine ID of the calendar events in this universe use by default.
URL to the .chroncal file for the default calendar.
Default celestial body for events in this universe (e.g. arda, coruscant).
04 Canon Scopes optional
What are canon scopes? They define the official tiers of continuity in your universe — the answer to "which version counts?" A Star Wars file might declare two scopes: Disney Canon (post-2014 official stories) and Legends (the pre-2014 Expanded Universe). Events in .chron files can then declare which scope they belong to, and tools can filter by scope. The supersedes relationship lets you record when one canon formally replaced another.
.chronverse untitled-universe.chronverse