Skip to content

Commit 86d340b

Browse files
committed
docs(rfc): RFC 0012 Isolation Backend interface
Specify the Isolation Backend that RFC 0001 declared but left unspecified: the contract by which a pluggable backend establishes an agent's isolation boundary and the supervisor operates it, instead of the supervisor building the boundary inline with logic hardcoded for one environment. Why now: OpenShell is already building boundary placements other than in-pod (a microVM driver on main, open work for a node enforcer and an outer gVisor sandbox). Without a shared contract each one wires its own privileged setup and supervisor mode into the codebase. The interface makes them backends behind one contract instead of supervisor forks, and keeps open the path to a placement that runs the supervisor outside the agent's kernel without rewriting the supervisor. Contents: - Two-faces model: a provisioning contract the driver realizes on the control plane and a runtime contract the supervisor drives on the data plane, handing off through the provisioned environment. - An 8-call runtime contract with ordering as a security property; five calls stable, three (exec, port_forward, identity) provisional, validated only where the supervisor shares the agent's kernel. - A Scope-and-status section stating what is stable vs in flight, which placements share the kernel, that Phase 1 ships a consistency check rather than cryptographic verification, and a falsifiability clause. - Trust defined as a contract (four MUSTs); the cryptographic mechanism deferred to a Phase 2 trust RFC. Capability-gated identity with an assurance ladder. - A kernel-sharing 2x2 with the forbidden cell (one pod plus a kernel-separated supervisor is not expressible on stock Kubernetes), grounded in the CRI shape. - An in-pod-first, behavior-preserving implementation plan; the nft fail-open fix is a hard prerequisite for Phase 1. - Security disclosures (shared-kernel residual risk, init-container exposure) and explicit non-goals (control-plane authorization, the trust mechanism, one-to-N supervisors). Supporting files: topology-matrix.md (placement catalog + selection matrix), codebase-grounding.md (file:line verification against main). Refs NVIDIA#1737, NVIDIA#899, NVIDIA#981, NVIDIA#1511, NVIDIA#1650, NVIDIA#1680.
1 parent 4ee27d9 commit 86d340b

3 files changed

Lines changed: 476 additions & 0 deletions

File tree

0 commit comments

Comments
 (0)