ArcBox — Agent Execution Environment

ArcBox Capability Matrix

Ephemeral, isolated, full-stack execution environment primitive. One box per task, never shared. Declarative arcbox.yaml spec. Network deny-by-default with egress allowlist. Credentials scoped and revoked at teardown. Phase 0 ready to start. Source: GRID-HANDOFF-ARCBOX-001 Rev A.

6
Phases
P0
Ready
8
Open Decisions
Phase Scope Status Exit criteria
Phase 0
Spec schema and provisioner
ArcBox spec schema on ArcHelm; one project (ArcGrid Surface) with arcbox.yaml; manual invocation only
ready to start A box provisions, runs the test suite, and tears down reproducibly
Phase 1
Cache layer
Base image build pipeline, volume cache, setup-time instrumentation
planned Setup time below 20% of box wall-clock on pilot project
Phase 2
Egress enforcement
Egress policy via ArcGate, Vault credential issuance, denial telemetry
planned Zero unpinned dependencies; all denials logged and visible
Phase 3
Attach and debug hold
Hold on failure, SSH/shell attach path, session capture into task records
planned A human can attach to a failed run and land a spec fix
Phase 4
ARC runner integration
Actions Runner Controller on ArcHelm backed by ArcBox provisioner; CI moves onto ArcBox for one repo
planned Green builds on Grid runners; one-line workflow change
Phase 5
AUTOBUILD integration
Wire into AUTOBUILD-001 loop; extend to portfolio cohort
planned Loop runs three concurrent projects within cost target
Box properties (arcbox.yaml)
Isolation unitOne box per task, never shared across tasks
ContentsOS, toolchain, pinned deps, repo working copy, service dependencies (DB, cache, queue), test fixtures
NetworkDeny by default, allowlist per spec. Denials logged as security events.
LifetimeTask duration + 60 min debug hold on failure
IdentityScoped credential set from Vault, issued at provision, revoked at teardown
MutabilityBox may be modified; spec that created it may not be modified by its own occupant
Open Decisions (8)
  • Isolation technology: Firecracker/Cloud Hypervisor (VM) vs hardened containers. VM is correct if client tenancy is in scope.
  • Where cache volumes physically live and failure behavior when that node is down.
  • Whether debug hold window is billable time against the per-project cost meter.
  • Whether client CI runs on Grid compute at all in year one, given the support surface it creates.
  • Ownership of arcbox.yaml per project: platform team or project agent with human review.
  • Base image cadence and accountability when nightly rebuild breaks a project.
  • Whether ArcBox is an internal primitive only, or eventually a Grid Pack offered to clients.
  • Hardware procurement trigger and budget ceiling for the Phase 0 sizing pass.