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.

vH.1.19phase: ChronosThe H.1.x benchmark/scoring rehaul arc

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
Coordinate: Release C · Era 1 · Name #20
Era: Chronos
Legacy token: v.H.1.19
CharonShipped
Coordinate: Release C · Era 1 · Name #19
Era: Chronos
Legacy token: v.H.1.18
CharonShipped
Coordinate: Release C · Era 1 · Name #18
Era: Chronos
Legacy token: v.H.1.17
CharonShipped
Coordinate: Release C · Era 1 · Name #17
Era: Chronos
Legacy token: v.H.1.16
CharonShipped
Coordinate: Release C · Era 1 · Name #16
Era: Chronos
Legacy token: v.H.1.15
CharonShipped
Coordinate: Release C · Era 1 · Name #15
Era: Chronos
Legacy token: v.H.1.14
CharonShipped
Coordinate: Release C · Era 1 · Name #14
Era: Chronos
Legacy token: v.H.1.13
CharonShipped
Coordinate: Release C · Era 1 · Name #13
Era: Chronos
Legacy token: v.H.1.12
CharonShipped
Coordinate: Release C · Era 1 · Name #12
Era: Chronos
Legacy token: v.H.1.11
CharonShipped
Coordinate: Release C · Era 1 · Name #11
Era: Chronos
Legacy token: v.H.1.10
CharonShipped
Coordinate: Release C · Era 1 · Name #10
Era: Chronos
Legacy token: v.H.1.9
CadmusShipped
Coordinate: Release C · Era 1 · Name #9
Era: Chronos
Legacy token: v.H.1.8
CadmusShipped
Coordinate: Release C · Era 1 · Name #8
Era: Chronos
Legacy token: v.H.1.7
PerseusShipped
Coordinate: Release C · Era 1 · Name #7
Era: Chronos
Legacy token: v.H.1.6
NemesisShipped
Coordinate: Release C · Era 1 · Name #6
Era: Chronos
Legacy token: v.H.1.5
TriptolemusShipped
Coordinate: Release C · Era 1 · Name #5
Era: Chronos
Legacy token: v.H.1.4
DaedalusShipped
Coordinate: Release C · Era 1 · Name #4
Era: Chronos
Legacy token: v.H.1.3
Re-drawn from the minor pool: this coordinate’s historical Name collided with a reserved Release-tier deity, so it is re-drawn to the canonical Name Daedalus shown above. The version history for v.H.1.3 still resolves through this node.
ArgusShipped
Coordinate: Release C · Era 1 · Name #3
Era: Chronos
Legacy token: v.H.1.2
PheidippidesShipped
Coordinate: Release C · Era 1 · Name #2
Era: Chronos
Legacy token: v.H.1.1
CharonShipped
Coordinate: Release C · Era 1 · Name #1
Era: Chronos
Legacy token: v.H.1.0

Release B · Boreas (“Genesis”)

6 nodes at their canonical coordinates, newest first.

CerberusShipped
Coordinate: Release B · Era 1 · Name #6
Era: Boreas (“Genesis”)
Legacy token: v.G.1.1a
AsclepiusShipped
Coordinate: Release B · Era 1 · Name #5
Era: Boreas (“Genesis”)
Legacy token: v.G.1.x
IrisShipped
Coordinate: Release B · Era 1 · Name #4
Era: Boreas (“Genesis”)
Legacy token: v.G.1.4
AntikytheraShipped
Coordinate: Release B · Era 1 · Name #3
Era: Boreas (“Genesis”)
Legacy token: v.G.1.3
CerberusShipped
Coordinate: Release B · Era 1 · Name #2
Era: Boreas (“Genesis”)
Legacy token: v.G.1.1
GenesisIn flight
Coordinate: Release B · Era 1 · Name #1
Era: Boreas (“Genesis”)
Legacy token: v.G.1.0

Release A · Aether (“Foundation”)

6 nodes at their canonical coordinates, newest first.

HydraShipped
Coordinate: Release A · Era 1 · Name #7
Era: Aether (“Foundation”)
Legacy token: v0.7.12l.x
MedusaShipped
Coordinate: Release A · Era 1 · Name #6
Era: Aether (“Foundation”)
Legacy token: v0.7.12.x
PrometheusShipped
Coordinate: Release A · Era 1 · Name #4
Era: Aether (“Foundation”)
Legacy token: v0.7.10.x
CassandraShipped
Coordinate: Release A · Era 1 · Name #3
Era: Aether (“Foundation”)
Legacy token: v0.7.9.x
PapyrusShipped
Coordinate: Release A · Era 1 · Name #2
Era: Aether (“Foundation”)
Legacy token: v0.7.8.x
AntikytheraShipped
Coordinate: Release A · Era 1 · Name #1
Era: Aether (“Foundation”)
Legacy token: v0.7.7.x