Skip to main content
On Dome, an operator owns the shared substrate: workspaces, tool and model connections, Gateways, grants, and the live signals that show the platform is healthy. You make backends reachable under Dome, group them behind named endpoints, grant the right agents access at the edge, and watch traffic. Developers integrate agents into that substrate. Security tightens what those agents may do once they are on it.

Hand this to an AI agent. It provisions an operator sandbox, attaches demo-hr, and proves the substrate with one smoke call.

Open in Cursor
In this tutorial, you will provision a sandbox, attach demo-hr to Default, grant a throwaway agent at the edge, and prove the substrate with one allowed call — then see it in audit. To do this, you will:
1

Provision a sandbox

Create the disposable workspace you will operate in.
2

Attach a tool to Default

Make demo-hr a governed target on the Gateway.
3

Grant a smoke-test agent

Admit a throwaway agent so you can prove the edge path.
4

Deploy a minimal allow

Permit discovery and one directory tool so the smoke call succeeds.
5

Smoke-test the substrate

Call once with curl or Python, then check audit.

Prerequisites

For this tutorial, you will need:
  • The Dome CLI installed and authenticated
  • A role that can provision a sandbox and attach tools (admin, operator, or equivalent — refer to Permissions concept)
This tutorial runs entirely in a sandbox. The throwaway agent and tiny Cedar rule exist only so you can prove backends and grants work — not to replace the Developer or Security tutorials.

Provision a sandbox

Confirm the workspace reads sandbox-role-operator.

Attach a tool to Default

A tool is unreachable until it belongs to a Gateway. Register the public demo HR server on Default:
Confirm Default lists the connection:

Grant a smoke-test agent

Without an agent grant, nothing can call through the edge — even with a healthy backend. Register a disposable agent and admit it:
Save the token to a gitignored .env. Treat this agent as scaffolding for the smoke test, not a production workload identity.

Deploy a minimal allow

Gateway grants admit the agent; Cedar still decides each call. Deploy the smallest permit that lets one directory tool succeed:
role-ops-agent.cedar

Smoke-test the substrate

One allowed call proves backend membership, the grant, and Cedar together.
Expect demo employees in result.
Confirm the call landed in audit. Tail live events in a second terminal if you want the operator view:

Clean up

Next steps

You learned how to attach tools to a Gateway, grant access at the edge, and prove the substrate with a smoke call. Continue with: