Compute orchestrationInfrastructure
Box sandboxes
Dispatch explicitly selected CPU sandbox work without sending it through the GPU startup-agent scheduler.
Box sandboxes — contract and behavior
- Box is provider-pinned and explicitly selected; it is not a fallback when no GPU is available.
- The dispatcher creates the sandbox, sends the task, collects output, and tears down through the provider contract.
- CPU sandbox lifecycle remains visible under the same job/result identity where the integration supports it.
- GPU resource estimates and cloud-agent startup templates do not apply to Box jobs.