Documentation / Releases / Canonical forest
Documentation · Pillar
The canonical versioning forest
Every shipped and in-flight node in the versioning model, grouped by Release and rendered newest-first, at its canonical (Release, Era, Name, fix?) coordinate. Where a historical Name collided with a reserved Release-tier deity the canonical re-drawn Name is shown here, with its provenance inline.
The four-designator scheme, in brief
Every coordinate on this page is a single key with four designators:
v.<Release>.<Era>.<Name>-<fix>
- Release— a major-tier deity; its leading letter is the release ordinal (A = 1, B = 2, …).
- Era— an integer counting the major arcs within a Release.
- Name— a minor figure drawn within an Era; the day-to-day identity.
- fix— an optional lowercase-letter patch suffix; an absent fix sorts strictly before that Name’s
-a.
The retroactive-fix rule
Touching shipped work under a historical Name does not open a new head node — it mints a retroactive fix under that Name at its historical coordinate: the next-unused fix letter. The first retroactive touch of a Name that shipped with no fix mints -a ; the next mints -b, and so on ([] → a, {a} → b).
Codename uniqueness & Release reservation
Every major-tier deity that occupies a Release slot is permanently reserved: a reserved Release-tier name may never appear at the Name layer, and no codename bound to a shipped coordinate is ever reused or used twice. A historical Name that collides with a reserved slot is re-drawn from the unused pool deterministically.
Concrete de-dup: the shipped Genesis Iris node keeps its historical Name at its preserved coordinate, while the later plannedrelease that reused “Iris” is re-drawn to Icarus — so the scheme is de-duplicated and the codename stays unique.
This page is a complement to the full grammar reference, not a substitute. For the complete explainer — the A–Z deity Release roster, the legacy-track historical note, and the model-authority section — read the Versioning chapter.
Release C · Chronos
20 nodes at their canonical coordinates, newest first.
CaduceusShipped
Release C · Era 1 · Name #20v.H.1.19CharonShipped
Release C · Era 1 · Name #19v.H.1.18CharonShipped
Release C · Era 1 · Name #18v.H.1.17CharonShipped
Release C · Era 1 · Name #17v.H.1.16CharonShipped
Release C · Era 1 · Name #16v.H.1.15CharonShipped
Release C · Era 1 · Name #15v.H.1.14CharonShipped
Release C · Era 1 · Name #14v.H.1.13CharonShipped
Release C · Era 1 · Name #13v.H.1.12CharonShipped
Release C · Era 1 · Name #12v.H.1.11CharonShipped
Release C · Era 1 · Name #11v.H.1.10CharonShipped
Release C · Era 1 · Name #10v.H.1.9CadmusShipped
Release C · Era 1 · Name #9v.H.1.8CadmusShipped
Release C · Era 1 · Name #8v.H.1.7PerseusShipped
Release C · Era 1 · Name #7v.H.1.6NemesisShipped
Release C · Era 1 · Name #6v.H.1.5TriptolemusShipped
Release C · Era 1 · Name #5v.H.1.4DaedalusShipped
Release C · Era 1 · Name #4v.H.1.3v.H.1.3 still resolves through this node.ArgusShipped
Release C · Era 1 · Name #3v.H.1.2PheidippidesShipped
Release C · Era 1 · Name #2v.H.1.1CharonShipped
Release C · Era 1 · Name #1v.H.1.0Release B · Boreas (“Genesis”)
6 nodes at their canonical coordinates, newest first.
CerberusShipped
Release B · Era 1 · Name #6v.G.1.1aAsclepiusShipped
Release B · Era 1 · Name #5v.G.1.xIrisShipped
Release B · Era 1 · Name #4v.G.1.4AntikytheraShipped
Release B · Era 1 · Name #3v.G.1.3CerberusShipped
Release B · Era 1 · Name #2v.G.1.1GenesisIn flight
Release B · Era 1 · Name #1v.G.1.0Release A · Aether (“Foundation”)
6 nodes at their canonical coordinates, newest first.
HydraShipped
Release A · Era 1 · Name #7v0.7.12l.xMedusaShipped
Release A · Era 1 · Name #6v0.7.12.xPrometheusShipped
Release A · Era 1 · Name #4v0.7.10.xCassandraShipped
Release A · Era 1 · Name #3v0.7.9.xPapyrusShipped
Release A · Era 1 · Name #2v0.7.8.xAntikytheraShipped
Release A · Era 1 · Name #1v0.7.7.x