Evidence Map¶
Inspected areas¶
Inspected README.md, pyproject.toml, sandbox_service/main.py, api/routes.py, models.py, runtime/base.py, both runtime implementations, path_guard.py, repositories, cleanup, workspace/artifact/snapshot helpers, frontend API/store/components, justfile, and tests.
| Subsystem | Confidence | Evidence |
|---|---|---|
| API contract | High | Typed Pydantic models and route handlers |
| Session lifecycle | High | Repositories, cleanup service, route transitions |
| Runtime abstraction | High | runtime/base.py, local/microsandbox adapters |
| Filesystem safety | High | path_guard.py and path tests |
| Snapshot behavior | High | snapshot routes, archive helpers, tests |
| Frontend operations | Medium | API client, query hooks, panels |
| Production isolation | Medium | microsandbox integration is dependency/runtime dependent |
Classification¶
- Confirmed: SQLite metadata, scratch workspaces, artifact exports, and optional microVM snapshots.
- Confirmed: local and microsandbox backends share an async protocol.
- Confirmed: bearer auth is optional and disabled by default.
- Inferred: the service is intended as a worker-facing control plane, not a general public shell.
- Unknown: deployment topology, multi-tenant identity model, resource quotas enforced by every backend, and artifact retention policy.