OpenRoots

Lifecycle

A published version is never edited.

That single promise makes errata a publishing problem rather than an editing one, and it is why every correction below names the version it applies to instead of quietly changing it. The published digest lets an adopter prove the bytes they hold are the bytes that were published.

The promise

Clause 16.2, word for word.

A published version of this Licence is never edited. A correction is issued as a new version, and every earlier version remains reachable at its canonical address permanently.
An adopter can hash the text they hold and compare it against the published digest. If the two match, they are holding exactly what was published, and no later decision by anyone here can change that.

Verify a copy you hold

curl -s https://openroots.org/licenses/orl/1.0/legalcode.txt | shasum -a 256

Every version

Status, conversion, and the digest of the canonical text.

Superseded never means withdrawn. A superseded version keeps resolving and keeps governing every work released under it.

InstrumentVersionStatusReleasedConversionMonthsSHA-256
ORL2.2Published2026-08-27none-41fbf21b90d7d7188886dcd7d245848f
ORL2.1Superseded2026-08-27none-not current
ORL2.0Superseded2026-08-26none-not current
ORL1.1Superseded2026-08-24none-not current
ORL1.0Superseded2026-08-24Apache-2.036monot current
ORD2.2Published2026-08-27none-ce06000460909da058c2d296bbb07f4a
ORD2.1Superseded2026-08-27none-not current
ORD2.0Superseded2026-08-26none-not current
ORD1.1Superseded2026-08-24none-not current
ORD1.0Superseded2026-08-24CC-BY-4.036monot current
ORM2.2Published2026-08-27none-71d68b5fe08820f88990a7f8c15fcbea
ORM2.1Superseded2026-08-27none-not current
ORM2.0Superseded2026-08-26none-not current
ORM1.1Superseded2026-08-24none-not current
ORM1.0Superseded2026-08-24Apache-2.036monot current
ORA2.2Published2026-08-27none-856afd5e95d1591630d5d569be4584a2
ORA2.1Superseded2026-08-27none-not current
ORA2.0Superseded2026-08-26none-not current
ORA1.1Superseded2026-08-24none-not current
ORA1.0Superseded2026-08-24Apache-2.036monot current

Policy

How a version number is allowed to move.

Rule three is the load-bearing one. Publishing a new major version moves nobody.

  1. 01

    A version number is major.minor and never a patch.

    There is no patch level, because a patch implies an in-place fix and there are none. A correction of any size produces a new minor version.

  2. 02

    A substantive change should receive a major version.

    A change to eligibility, payment, fallback status, or the competing-offering boundary is substantive. Version 1.1 predates this rule and made substantive changes under a minor number; that published identifier is retained, recorded below as a governance defect, and must not become a precedent.

  3. 03

    A major version is opt-in and never retroactive.

    A work released under 1.0 remains governed by its frozen 1.0 text, including that version's historical conversion provision. Publishing 1.1, 2.0 or 2.1 moves nobody, and no or-later clause exists in any instrument.

  4. 04

    A superseded version stays reachable and stays valid.

    Superseded means a newer version exists and is recommended for new work. It never means the old one stopped working, and the canonical URL keeps resolving.

  5. 05

    Deprecation is dated, announced and never silent.

    A deprecated identifier is marked with the date it was deprecated and the identifier that replaces it, following the shape Creative Commons uses for its own retired units.

Errata

1 errata on the record.

An erratum is a defect found in a version that has already been published. Because the text is never edited, the erratum stands on the record against that version until a correcting version exists.

  1. 01Anyone may raise an erratum against any published version, on the public tracker or privately to info@openroots.org.
  2. 02The committee records the finding here with a severity and a disposition, including findings that are declined, and states why.
  3. 03A typographical or clarifying erratum is corrected in the next minor version. A substantive one requires a major version, because it changes what is owed.
  4. 04Until the correcting version is published, the erratum stands on the record against the affected version. The affected text is never edited.

Deprecation

Nothing is deprecated.

A deprecated identifier is marked with the date it was deprecated and the identifier that replaces it. Deprecated never means unusable.

No identifier has been deprecated. When one is, it appears here with its date and its replacement and stays on this page permanently, following the shape Creative Commons uses for its own retired units rather than removing them from the record.