Release history
Every push to dev is a release: CI validates the site, verifies the version bump, tags the commit v{release}.{major}.{minor}, and deploys to GitHub Pages. How it works.
| Version | Date | What shipped |
|---|---|---|
| v0.2.0 | 23 Aug 2026 | The real brief pack arrived, and this release replaces v0.1.0's content in full.
v0.1.0 shipped without a brief pack, under the working assumption that this site would report on the The build order from the brief, followed in full for the first five steps: the front page, /corrections/ (hub plus all five specified subpages — the 10,000-hours case, the 242-paper citation network, how a graph answers it, the self-critique on agenda, and the AI Act staleness case), /provenance/ (hub plus the £8.40 worked story, the decision graph, show-your-work and articles-as-vaults), /library/ (all ten core articles and three adjacent pieces, chronological, each carrying the provenance contract), and /economics/ (hub plus paying-the-fact-creator, trust-as-a-service, the payment rails, and the republished 2025 micropayments piece paired deliberately with the 2026 rail). Three sections shipped as single comprehensive hub pages rather than the full multi-page trees the brief specifies: /rights/, /newsroom/ and /thesis/. That is a real, stated de-scoping — tracked as task T1 — made to get the whole architecture live and gated in one release rather than shipping half of it silently complete. The provenance contract is now enforced by the gate, not just documented. A new validate.js check requires every block marked Two honest limits, stated rather than smoothed over. The brief's own N1 request — roughly 15,000 words of likely origin material sitting in an external repository not yet retrieved — means the library's chronology may still be incomplete at the start. And several republished |
| v0.1.0 | 22 Aug 2026 | The site, first release — pipeline first, shipped without a brief pack.
No brief pack had reached this site at the time of this release. Rather than block, v0.1.0 shipped the validate → tag → deploy pipeline, carried in from the sibling |