6 · The release discipline
The same as every other site in this estate: validate → tag → deploy, in that order, with a failure at any stage stopping the release. One file owns the version, the release commit's subject repeats it, and CI refuses to tag if the two disagree. Every push to the release branch is a minor.
That is not ceremony. It is what makes "as of v0.2.1, this claim was verified" a statement somebody can check a year later.
PAGE /disclosures/ — Disclosures
title: Disclosures description: "Every commercial relationship between this estate and any provider written about across this family, in one place. There are none. Created before any exists." lead: "Every commercial relationship between this estate and any provider written about across this family, in one place — created before any relationship exists, so that the existence of a page about a vendor is not read as evidence of a relationship with them." order: 90 provenance: commit: 7d1916aca5f3 date: 8 September 2026
| Provider | Relationship | Since | Checked |
|---|---|---|---|
| ElevenLabs | None. A self-paid key, and one free-tier key supplied by the project lead for a single render on 8 September 2026. No credits, no programme, no agreement | — | 8 September 2026 |
| OpenRouter | None. Pay-as-you-go on a self-minted key, list price | — | 8 September 2026 |