How the charter has changed.
The charter is versioned on its own track, the way it asks the institutions that adopt it to be. This is the public record of what each release changed. From v0.9 the charter also ships as machine-readable data, so any two versions can be compared clause by clause.
The debts paid
Two clauses owed for several rounds are written in. Article 7's commonwealth trust gains the three locks it was missing against EQ–02e: a second key held outside the spending coalition, a named and permanently funded valuation bureau, and the anti-Nauru rule that the trust never lends to the polity that charters it. Article 8 gains the governance-overhead ledger and band, the charter's own price counted in money and member-hours and held inside a published band that fails in both directions, bloat above and starvation below, under the ceiling falsifier F–10 sets. This is also the first version published as machine-readable data.
The ten-article charter
The charter as a fillable, printable document of ten articles, from the inviolable floor and the five commitments through membership and codified exit, decaying standing on the calibrated bands, the four governance modes with the bridge to civilizational scale, the justice of light, automated decisions, the commons and the more-than-human, the vital-signs review, and amendment and forking under the fork protocol. Every bracket editable in the browser, every clause traced to its precedent at the end.
The first adoptable charter
The charter became a real template a group could fill and adopt, brought level with the framework as the instruments caught up. Earlier still, it began as a sketch that traveled alongside the manifesto rather than a document meant to be signed.
From v0.9 the charter ships as a structured file, charter-v0.9.json, one entry per article with its title, text, and fillable slots. Two versions can be compared clause by clause with any diff tool, and a fork can carry its divergence as a change to the data rather than a prose rewrite. This is the fork protocol of Article 9 made concrete: a legitimate fork takes its own name, files a divergence document naming what would re-merge it, keeps the commons interoperable, and strips no one's standing.