Compute

Compute is the app surface for the execution machinery behind interactive work and judged runs.

Use it when the question is “what is actually running, what compute exists behind it, and which object should I control?”

Note

In the product model, the runtime is the durable control point and the sandbox is the replaceable compute backing.

Two-layer model

Layer	What it does	What it does not do
Runtime	holds durable interactive identity, sessions, capability bindings, and project grouping	it is not the provider instance
Sandbox	tracks the provider-backed compute allocation, lifecycle, and billing	it is not the durable interactive identity

When to use which page

• use Runtimes when you need to start, pause, resume, reset, or reason about interactive context
• use Sandboxes when you need to understand the compute ledger shared by runtimes, evaluations, tasks, and worlds workloads

The practical split is:

• runtime questions are usually about control and continuity
• sandbox questions are usually about provider state, expiry, logs, and billing

Workflow

1. start from the runtime when the problem begins with a project, conversation, or interactive tool flow
2. drop to the sandbox layer when you need provider IDs, logs, or low-level compute audit
3. move to Agents when the question broadens from one instance to a workspace pattern and you need Charts, Data, or Notebook

What agents should assume

• runtime controls are the right surface for interactive lifecycle operations
• sandbox records persist for billing, telemetry, and audit even after termination
• project is grouping metadata while workspace remains the main scope boundary
• evaluations can create additional sandboxes without taking over the interactive runtime slot