Releases
Release centre
Nothing has been released. Not software, not a module, not a dataset, not a finding.
What a release will carry
| Every release records | Why |
|---|---|
| Immutable version identity | Changed bytes or changed meaning require a new version. A published version's bytes never change. |
| SHA-256 digest | So you can confirm you received what was published. |
| Explicit licence | Ambiguous ownership is non-releasable, and the build enforces it. |
| Provenance | Where it came from, with sanitised steps marked as such. |
| Release state | Current, superseded, deprecated or withdrawn — and superseded releases stay addressable. |
| Verification recipe | How to check it yourself, and what that check does not establish. |
What has changed so far
Scientific state changes — including the ones that weaken a claim — are recorded separately from API contract changes, because mixing them trains readers to ignore both.
- Scientific changes — currently empty; Atom feed
- API contract changes — one entry, the initial contract
- The demonstration claim's history — semantic diffs across three versions