HypervibeDocs
SearchCtrl K Menu

Products

The components that make up Hypervibe, what each one owns and where to read more.

Standing
Planned
Release
No public release yet
Last verified
On this page

Hypervibe is the platform. Lanes, Rocket!, Throttle and Reactor are its components, Fleet is the privileged operations workspace, and the companion carries attention and decisions to your phone. Each component is designed to be useful on its own and to work with the others, and each owns its decisions: no component reaches into another's state.

Each product owns one part of the work #

ProductOwnsStanding
Hypervibe platformIdentity, organizations, devices, configuration, grants and the managed workspacePlanned
Rocket!Agent sessions, tools and exact-effect approval, planning, context and reviewPlanned
LanesThe lane directory, long-running lanes, attention, decisions and messagesPlanned
ThrottleInference routes and admission, the capability catalogue, provider credentials, capacity and usagePlanned
ReactorInstalling Hypervibe; admission and execution of builds and agent tool calls, artifacts, receipts and independent verificationPlanned
FleetOperations on enrolled machines: placement policy, rollout, repair and retirement, under grants and with no store of its ownPlanned
CompanionPairing a phone, attention and decisions away from your computerPlanned

The components share one vocabulary #

The same words mean the same things everywhere. A lane is one addressable work seat, and it outlives the processes behind it. A session is Rocket!'s resumable journal of one piece of agent work, and it resumes as the same session after a kill. A build is what you ask Reactor for, and a job is one admitted execution with its receipt. A grant is the authority an agent or person acts under, and it is checked again where the effect happens. The glossary lists the rest.

Where to go next #

Search the docs