Feature Matrix

ArcActuate Feature Matrix

Five execution lanes, milestone plan M0 through M4. Each milestone ships one lane from charter design through ArcBox integration to production readiness. All milestones are currently planned.

5 lanesM0–M4All Planned

ArcActuate ships in five milestones, one per execution lane. Each milestone adds one full lane to the agent action surface. All lanes build on the charter permission model — no lane is usable without an explicit charter grant. Browser and Code lanes are highest priority as they unblock the most factories.

M0 — Browser Lane (Playwright)
IDCapabilityStatusNotes
ACT-B1Playwright context isolation per agentPlannedEach agent gets an isolated Playwright context; no cross-agent cookie/session leakage
ACT-B2navigate(), click(), fill(), extract() primitivesPlannedCore browser action surface exposed via ArcActuate SDK
ACT-B3Screenshot capture and returnPlannedReturns base64 screenshot in result envelope; available to agent for visual analysis
ACT-B4Domain allowlist enforcement from charterPlannedCharter defines allowed_domains; navigation outside list raises CharterViolation
ACT-B5Signed execution receiptPlannedEvery browser session produces a receipt written to audit trail
M1 — Code Lane (ArcBox)
IDCapabilityStatusNotes
ACT-C1ArcBox (gVisor) container provisioningPlannedEphemeral gVisor container per code execution; cleaned up on completion
ACT-C2Python / JS / shell runtime supportPlannedThree initial runtimes; extensible via runtime registry
ACT-C3stdout/stderr/exit code result envelopePlannedStructured output returned to calling agent
ACT-C4Network egress blocked by defaultPlannedCode lane containers have no network by default; charter can grant specific egress rules
ACT-C5Signed execution receiptPlannedReceipt includes container ID, runtime, hash of code input, exit code
M2 — Terminal Lane (ArcBox)
IDCapabilityStatusNotes
ACT-T1Persistent ArcBox container per agent sessionPlannedContainer persists for session duration; destroyed on session end
ACT-T2Shell command execution with streaming outputPlannedLong-running commands stream stdout back to the agent in real time
ACT-T3Scoped mount for file exchangePlannedCharter-defined directory mounted into container; output accessible via File lane
ACT-T4Process lifecycle managementPlannedstart(), wait(), kill(), status() for long-running process control
M3 — File Lane
IDCapabilityStatusNotes
ACT-F1read(), write(), move(), delete() on scoped treePlannedAll operations path-jailed to charter-defined root; no escapes
ACT-F2Directory listing and glob supportPlannedlist() and find() within the scoped tree
ACT-F3Write permission separate from deletePlannedCharter fields: can_write, can_delete (default false for both)
M4 — API Lane
IDCapabilityStatusNotes
ACT-A1Managed credential injectionPlannedAgent specifies credential alias; ArcActuate injects the real key — agent never sees it
ACT-A2Network egress allowlist per charterPlannedCharter defines allowed API hosts; calls to unlisted hosts fail at the SDK boundary
ACT-A3Structured request/response loggingPlannedFull request + response logged to audit trail (body scrubbed of credential headers)
ACT-A4Retry and timeout configurationPlannedPer-call retry policy, backoff strategy, and timeout ceiling