Audience 01
Enterprise platform teams
Adopts it to replace a patchwork of tools with one reviewable surface.
Knowledge & context · Concept
Where the work actually changes.
GraphHypervisor is aimed at Enterprise platform teams, data architects, multi-tenant software companies.
01
Who it is for
Three audiences, one boundary model.
Audience 02
data architects
Needs the same permission model for people and agents.
Audience 03
multi-tenant software companies
Needs the same permission model for people and agents.
02
Use cases
Each row maps a capability to the operational change it is meant to produce.
| Capability | Operational change | Status |
|---|---|---|
| Graph namespaces and virtualization | Makes an existing action reviewable. | Specified |
| Cross-graph federation | Turns a manual control into an explicit contract. | Specified |
| Graph-scoped permissions | Makes an existing action reviewable. | Specified |
| Query and execution mediation | Removes an ad hoc step from the workflow. | Specified |
| Provenance, monitoring and replay | Removes an ad hoc step from the workflow. | Specified |
03
Migration
How a team would move from the status quo without a big-bang cutover.
Step 01
Map the current path
Name the tools, owners and handoffs that the product replaces. Nothing is removed yet.
Step 02
Run one capability
Pick a single scoped capability and run it alongside the old path, with evidence compared side by side.
Step 03
Retire the old path
Remove the previous tool only when the new record is complete enough to audit.