HypervibeDocs
SearchCtrl K Menu

Docs

The manual for Hypervibe, the fully managed agentic factory, covering what each component does, how they fit together and how far each part has come.

Start from what you need to do #

Four components share one platform #

You give Hypervibe a goal, the authority to act, a budget and a definition of done. Rocket! does the work, Throttle supplies inference from every provider it supports and holds every credential, Reactor builds and verifies the exact candidate, and Lanes keeps your running work and the decisions that need you in view. Hypervibe itself, the platform, holds identity, configuration and the managed workspace, and Fleet, the privileged operations workspace, looks after the machines underneath. You get a verified candidate, decide whether to accept it, and see one receipt with the full cost.

Every page says how far its subject has come #

StandingWhat it means
QualifiedBacked by a qualification receipt for a named release, target and profile.
PreviewApproved experimental behavior with a named scope and explicit limits.
PlannedAn approved future concept. Not available to install or run.
UnavailableA known missing requirement or an unsupported combination.
UnknownEvidence is missing or insufficient to say more.
DeprecatedReplaced, with a named replacement or removal condition.
SyntheticIllustrative data. It describes origin, not availability.

How standings are decided explains what counts as evidence and what does not.

Each change to the site is recorded #

Every change that reaches hypervibe.app adds an entry to the change log, and Releases will list each public release with its compatibility and evidence.

Search the docs