BUILD · CHANGELOG
An empty changelog is more useful than an invented one.
What belongs on this page is every change that reached a running system, dated, with the commit that carried it and the person who wrote it. None of that is published yet, and this page is not going to open with three plausible entries so the section looks finished. What it can do is print the two things this build genuinely knows about itself, and say exactly where the rest has to come from.
A changelog that is typed is a marketing artefact. A changelog that is generated is a record.
What this build knows about itself
Two facts, both read from git while this page was being generated rather than written into it. They are the same two the footer of every page on this site carries, and they are enough to answer the only question a changelog page can answer today: which build are you looking at?
- Commit
-
f44fed2 - Generated
2026-08-31T19:58:26Z
What is missing, and what it would take
There is no CHANGELOG.md in this repository for the site to read, no release
feed, and no tag set a build step could walk. Producing this page honestly is therefore
not a writing task — it is a generation task: read the commit range between two releases,
keep the changes that reached a running system, drop the ones that did not, and print
each with its date and its author. Until that runs, an entry on this page would be a
claim with nothing behind it.
Where a change that was wrong actually gets recorded
The discipline this page will eventually carry already exists elsewhere in a stricter form. When a claim is published and later found to be wrong, it is withdrawn in public — what it stood as, what re-checking found, and what is published instead. That ledger is the harder half of a changelog, and it is the half most projects never write.
What is real here.
No part of this page is generated from a change history, because there is no change history for it to read. The commit and timestamp above are measured; everything a reader would actually come here for is absent, and it is absent rather than approximated.
- LIVE Publishes deterministic vectors a third party can recompute offline to check their implementation against ours conformance-vectors
The register holds 17 live · 2 partial · 2 planned · 5 not yet.
1 of the 2 capabilities this page depends on have no row in the register yet, so this page will not print a state for them. They are named rather than dropped, because a slice that silently shortens itself is the same defect as a claim with no receipt.
- generated-contract
The register route serves, but it carries no row for these yet. List what it does carry:
curl -s https://id.orbis.id/api/site/register | jq -r '.entries[].slug'Straight answers
- Is there a changelog I can subscribe to?
- No. There is no feed, no mailing list, and no page of entries — this one included.
- How do I tell which build I am looking at?
- The commit above, and the same identifier in the footer of every page on this site. Both are read from git at build time, never typed.
- Why not list a few notable changes in the meantime?
- Because a hand-picked list is an argument about what mattered, and this section is supposed to be a record. The generated version is worth waiting for.
Do not trust us. Check us.