Releases
Release standing, compatibility and what each public release contains, starting with the first.
On this page
The first release needs two records #
The first version exists only when both records exist:
| Record | What it shows | Standing |
|---|---|---|
| Single-person record, for Just me | One person on one Linux x86-64 machine installs Hypervibe, connects Claude with an API key, commissions a change, recovers it after an interruption, verifies it, decides on it and sees one cost receipt. The installed GraphLake engine then explains the same run and its cost from the evidence it projected. The run is repeated on a second clean machine. | Planned |
| Team record | A team server with sign-in, invitations, enrolled machines, a shared inference pool, revocation and a restore onto a fresh server, repeated from the restored server, with the team's GraphLake engine explaining the team's runs. | Planned |
The first release is planned to include every model provider Throttle supports. Each provider other than the one the single-person record runs on is planned to qualify by its own conformance tests and one recorded live call, not by a whole run.
macOS and Windows are Unavailable: they are not part of the first release. A hosted server is Planned as a later packaging profile, and the phone app comes after the first release. Each gets its own entry here when its evidence exists.
Each release will get its own page #
A release page will list the version, the supported platforms and profiles, what changed, what was deprecated or removed, migrations, and the evidence behind each claim. Older supported releases keep their pages, and links into them keep working.
Changes to this site are logged #
Every change that reaches hypervibe.app is recorded in the change log, whether or not it is a product release.
Where to go next #
- Standings explains what counts as release evidence.
- Choose a profile shows which record each profile waits for.
- Install explains what setup is designed to change once a release exists.