Hypervibe platform
What the Hypervibe platform will keep for the other components, from identity and settings to grants, the capability registry and the workspace inventory.
On this page
Hypervibe is the fully managed agentic factory, and its platform is the system of record under the other components. Other pages call that system of record the Hypervibe service. It will hold who you are, how your work is configured, what each person and agent may do, and what exists in each workspace, and it runs no work itself. This page covers what the platform keeps, how one person and a team differ, and what the first release includes. All of it is Planned.
The platform keeps the record, and other components act on it #
| Concern | The platform keeps | Owned elsewhere |
|---|---|---|
| Identity | People, devices, machines and agents, each acting in one organization | Credential values: Throttle |
| Configuration | Every setting, with its scope, layer and revision | What a setting means: the component that owns it |
| Secrets | A secret's type, scope, owner, rotation and grants, never its value | The value: Throttle; only the key to the platform's own store stays with the service |
| Work | Commissions and their work records, changed only through shared Work, the one owner of tasks and runs | Doing the work: Rocket!; running tools and verifying the candidate: Reactor |
| Machines | Inventory records | Acting on machines: Fleet, under grants |
| Spending | Budgets, as settings | Admission, usage and settlement: Throttle |
Identity starts with one person and grows into a team #
The Just me profile is one person on one machine, with no sign-up and no sign-in. Hypervibe sets up one local owner, your operating-system user, in a personal organization. A request from another user on that machine is refused, and agents cannot reach the owner's keys.
For a team, an organization holds teams, a team is people, and a member belongs to an organization and its teams. Organization roles are owner, admin and member. You join by invitation and sign in with Google, with no password and no emailed link. A machine without a browser signs in with a device code instead. GitHub sign-in is planned for a later release.
A device is a signed-in client with its own key, such as a laptop, a phone or a browser. A team's owners and administrators can pause, resume or revoke a device, remove a member, or revoke an enrolled machine. The first release's team record requires anything paused or revoked to be refused within 60 seconds; that figure is a requirement, not a measurement. One organization never sees another's records.
Every setting shows the layer that won and its revision #
No configuration file is meant to be edited by hand. A value is either a registered setting or a file Hypervibe writes for a tool that can only read a file. Each value comes from one layer, in this order: the default, your organization, your team, you and this device. The later, more specific layer wins, but a preference never widens a policy. Every value shows the layer that set it and its revision. Most settings refuse a save that started from an older revision, so no change is silently lost.
On Just me, the first release shows settings read-only. In the team record, a team's owners and administrators can change shared team settings, such as the team's model and daily budget, and the change applies from the next revision. Editing every layer comes in a later release.
A grant is the only thing that authorizes #
A grant gives one capability, at one scope, to one subject: a person, an agent, a device or a machine, or a whole team or workspace. Grants are checked when something is searched for, when a reference is resolved and on every use, and the component where the effect happens checks again before it acts. "Not found" and "not visible" are the same answer, so a search never reveals what you cannot see. Installing a package, binding it to a workspace or writing instructions grants nothing.
The registry and the inventory describe what exists #
- The capability registry lists skills, tools, hooks, connectors, workflows, agent teams and the extension packages that bundle them. Installed, enabled and authorized are three separate facts, and a capability that is declared but not yet qualified is never offered. The registry comes in a later release.
- The inventory lists workspaces, repositories, worktrees and installed products. Machines report what they observe, and a person or a grant holder sets what should be. The first release keeps a local inventory, and team clients poll the team server for changes.
- Managed files each have one mode: canonical (written by people), projection (generated from a source you edit) or observed (listed, not yet adopted). A difference from the expected content, called drift, is shown with both versions and never silently overwritten. Drift handling comes in a later release.
One person and a team run the platform differently #
| Question | Just me | A team |
|---|---|---|
| Where it runs | Your machine. Hypervibe's records need no database server, and the planned GraphLake engine runs there as a managed part of the install | A team server your organization hosts itself |
| Store | An encrypted database embedded on your machine | PostgreSQL on the team server |
| Sign-in | None | Google after an invitation, or a device code |
| What the server holds | There is no server | Team records, such as settings, membership and devices |
| What stays on your machine | Everything the platform keeps | Your personal records and Rocket! transcripts |
A hosted server run for you is not part of the first release; it is Planned as a later packaging profile. A shared multi-replica service is deferred.
The Platform web area comes in a later release #
The web app is designed with two areas, switched by Lanes · Platform. The Platform is where identity and configuration live, in seven sections: Profiles, Workspaces, People & teams, Skills & tools, Instructions, Managed files and Connectors. In the first release, team administration uses the planned hyper commands, an invitation page, a device-code approval page and interim team views, which the Platform's People & teams section replaces later.
Where to go next #
- Choose a profile compares Just me with the team profiles.
- Throttle holds every credential value.
- Fleet acts on machines under grants.
- Managed workspaces covers recipes and managed files.
- Deploy and operate covers team servers and enrollment.
- Standings explains what Planned means.