Skip to content

Perimeter · Open Intent → NVIDIA OpenShell policy

Compile intent into containment policy.

Perimeter (the @intended-inc/perimeter package) compiles Open Intent families and policy into a valid NVIDIA OpenShell containment policy — filesystem, process, per-endpoint network rules, Landlock — applied when the sandbox is provisioned. This is static, ahead-of-time compilation, not per-action runtime interception. Apache 2.0.

02 · How it works

01 · Install

pnpm add @intended-inc/perimeter

One package. Apache 2.0. No account required for the compiler itself.

02 · Compile

Open Intent + policy → NVIDIA OpenShell YAML

Perimeter emits a valid NVIDIA OpenShell containment policy (validated against the launched NVIDIA OpenShell policy schema). Apply it with the NVIDIA OpenShell CLI when you provision the sandbox.

03 · Contain

NVIDIA OpenShell enforces the boundary

Kernel isolation and the resource allow-list enforce what the agent can reach. Containment is resource-level; it does not evaluate semantic intent.

04 · Authorize (roadmap)

Per-action authority at runtime

Asking Intended for an ALLOW/ESCALATE/DENY per action at runtime, from inside the NVIDIA OpenShell path, is on the roadmap — it needs a hook the open runtime does not expose today. We don’t claim it until it ships.

Intended is the authority layer above containment.

Perimeter · Open Intent → NVIDIA OpenShell policy | Intended