RVBox v1 design set
This design set turns the initial proposal into an implementation contract. Read the documents in this order:
- Architecture — scope, trust model, state machine, execution, storage, and retention decisions.
- Agent protocol — WSS framing, sessions, replay, ordering, script transfer, heartbeat, and failure containment.
- Control plane —
rvc, Unix-socket gRPC, JSON-RPC, and query/foreground semantics. - Platform and operations — Windows contract, recovery, storage safety, telemetry, and defaults.
- Configuration contract — strict TOML loading, shell resolution, cross-field validation, and annotated server/client examples.
- Go implementation plan — phased build order, package boundaries, storage/session/client details, tests, and release gates.
- Implementation testing — container entry points, run lifecycle, exact cleanup, and coverage inventory.
- Provisioned Windows test VM — exact fixture identity, host/guest access, endpoints, snapshots, credentials contract, reset procedure, and known limitations.
- Interactive VM access — temporary, self-signed HTTPS browser gateway for the rare manual UAC recovery step.
- Linux-server operations runbook — deployment, backup/restore, upgrade, and incident response.
The wire authority is in ../protos/rvbox/v1:
common.proto contains shared data types, agent.proto contains the
client/server WebSocket envelopes, and control.proto defines the local gRPC
service that the HTTP JSON-RPC adapter mirrors.