Use this checklist with the current Sandbox API flow.
Do not substitute the iCommerce database path, Sandbox API key, model credential or governed
principal for one another.
1. Provision and retain identity
Choose the admitted runtime/image and resource/lifetime limits. Retain the create request
and its supported idempotency key before dispatch. Verify returned sandbox identity and
readiness; startup consumes its own budget and can consume part of lifetime.
2. Verify the environment
Confirm compatible Node, native module and CLI 1.39.0. Read the explicitly configured store
and one known record. Check durable storage and secret/network scope. A fresh empty SQLite
file is not proof that production data is unavailable or already migrated.
3. Review and execute
Preview the intended typed operation under operator-owned policy/principal/store settings.
Persist original key, payload, versions and approval evidence. Enable apply only through the
configured governed host; a deterministic direct accessor has a different authority contract.
4. Retain and reconcile
Inspect execution outcome, governed receipt, native state, physical stock and provider/ERP
outcomes separately. Export required receipts/artifacts before terminating the worker.
Unknown command outcomes require execution recovery,
not automatic replay. Recover the original commerce request identity after response loss.
5. Stop and verify
Stop in a cleanup/finally path and verify the returned acknowledgment and deployment’s
resource retirement. An accepted stop is not proof of every storage deletion or billing
outcome. Resolve failed cleanup explicitly. See
Sandbox operations. Last modified on October 20, 2026
