Changelog

Two kinds of change land here, and the distinction matters more than the dates.

• Protocol and surface changes — a new tool, a renamed field, a changed bound, a route that now returns a different status. These change what your integration has to do.
• Documentation changes — a page that was wrong and is now right. These change nothing about the protocol and everything about what you can trust on this site.

Nothing has shipped yet

There is no release history because there has been no release. The contracts are not deployed on Base or on Base Sepolia, the documented hosts do not resolve, and this site is not published. The first entry below is added on the first deploy, not before.

Writing invented version numbers here would defeat the page's only purpose: being the one place a reader can check whether a behaviour described elsewhere on this site is actually live.

How this page is maintained

Hand-written, in the same change as the thing it records. Three rules keep it honest.

One: a deploy to the public host is a changelog entry, in the same commit. Some pages on this site carry a callout saying the feature they describe is merged but not yet on the public host. Removing one of those callouts is what a deploy looks like from here, and the procedure for it — in CONVENTIONS.md, mirrored by a test that inverts the moment an entry is deleted — ends by noting the deploy on this page. A callout cannot be removed without an entry appearing.

Two: a corrected claim is an entry. If a page said something untrue about the protocol and now says something true, that is worth recording, because a reader who integrated against the old sentence has a decision to revisit. Prose improvements that changed no claim are not entries.

Three: newest first, and every entry names what a reader has to do. An entry that records a change without saying whether it breaks anything is not finished.

Not a release feed

Vocs can generate this page from a repository's GitHub releases. That is deliberately not wired up: it fetches at build time, so a repository with no releases produces an empty page, and a private one produces a build that depends on a token the host does not have. The one-line switch is recorded as a comment in vocs.config.ts for whenever tagged releases exist. Until then this page is prose, and its accuracy is a review obligation rather than a build step.

The code itself is the authoritative record in the meantime: the repositories under github.com/OpenSoukAI carry the commit history, and the tickets referenced in it carry the reasoning.

Next steps

• Overview — what the protocol does, if you arrived here first
• Protocol — the guarantees that hold whatever changes here
• The contracts — the deployment state, read from the artifacts rather than claimed