sand-boxer/registry/capabilities/execution.sandbox-provision.md

---
id: capability.execution.sandbox-provision
name: Sandbox establishment and lifecycle
summary: Profiles, extensions, provision, checkpoints, TTL teardown and telemetry.
owner: sand-boxer
status: draft
domain: infotech
tags:
- sandbox
- isolation
- provision
- e2e
- agentic
- execution
- profile
- security
- netkingdom
- framework-reuse
maturity:
  discovery:
    current: D5
    target: D6
    confidence: high
    rationale: 'Charter (INTENT.md), meta-framework spec, extension SDK, integration
      docs, and research synthesis. Capability indexed in registry/.

      '
  availability:
    current: A5
    target: A5
    confidence: high
    rationale: 'Source interface assessed 2026-10-14: Profiles, extensions, provision,
      checkpoints, TTL teardown and telemetry. Availability describes the delivery
      form, not production acceptance. Backend-specific guarantees; a created sandbox
      alone proves no credential isolation.'
external_evidence:
  completeness:
    level: C5
    name: Mature
    confidence: high
    basis: scope_vs_intent_and_consumer_expectations
    satisfied_expectations:
    - profile-based create/destroy/snapshot/restore via CLI
    - TTL extend and expire/reap (SAND-WP-0009)
    - E2B and Modal cloud adapters with BYOK (SAND-WP-0010)
    - State Hub lifecycle events on transitions
    - wise-validator and the-custodian migration arc complete
    - extension SDK with compose-ssh, vm-packer attach, saas-stub, e2b, modal
    broken_expectations:
    - sandboxer01 dedicated host not live (CoulombCore interim)
    out_of_scope_expectations:
    - agent harness and tool orchestration (glas-harness)
    - e2e test semantics (wise-validator)
  reliability:
    level: R0
    confidence: low
    basis: No longitudinal reliability assessment available.
discovery:
  intent: Profiles, extensions, provision, checkpoints, TTL teardown and telemetry
  includes:
  - Profiles, extensions, provision, checkpoints, TTL teardown and telemetry
  excludes:
  - Backend-specific guarantees; a created sandbox alone proves no credential isolation
  use_cases:
  - 'U11: Agent executes an attributable bounded task and supplies supervision evidence'
  - 'U14: Framework adopter validates and reuses selected contracts, tools and reference
    compositions'
availability:
  current_level: A5
  target_level: A5
  current_artifacts:
  - SCOPE.md
  - README.md
  consumption_modes:
  - containerized service
  - CLI
relations:
  related_to:
  - capability.security.iam-tooling-suite
evidence:
  documentation:
  - SCOPE.md
  - README.md
consumer_guidance:
  recommended_for:
  - Agent executes an attributable bounded task and supplies supervision evidence
  - Framework adopter validates and reuses selected contracts, tools and reference
    compositions
  not_recommended_for:
  - Backend-specific guarantees; a created sandbox alone proves no credential isolation
  known_limitations:
  - Backend-specific guarantees; a created sandbox alone proves no credential isolation
  - 2026-10-14 architecture review estimates operational maturity separately; a registry
    entry does not authorize execution or establish deployment.
---

# Sandbox establishment and lifecycle

Profiles, extensions, provision, checkpoints, TTL teardown and telemetry.

## Reuse boundary

Backend-specific guarantees; a created sandbox alone proves no credential isolation.

## Supported use cases

- U11: Agent executes an attributable bounded task and supplies supervision evidence
- U14: Framework adopter validates and reuses selected contracts, tools and reference compositions

## Evidence and integration

- [SCOPE.md](../../SCOPE.md)
- [README.md](../../README.md)

Assessment: CUST-WP-0081, 2026-10-14. Relations identify interfaces to compose; they do not certify native integration. Existing external evidence levels are retained where present. New entries use conservative C1/R0 until consumer assessment exists.