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)
| ID | Capability | Status | Notes |
|---|---|---|---|
| ACT-B1 | Playwright context isolation per agent | Planned | Each agent gets an isolated Playwright context; no cross-agent cookie/session leakage |
| ACT-B2 | navigate(), click(), fill(), extract() primitives | Planned | Core browser action surface exposed via ArcActuate SDK |
| ACT-B3 | Screenshot capture and return | Planned | Returns base64 screenshot in result envelope; available to agent for visual analysis |
| ACT-B4 | Domain allowlist enforcement from charter | Planned | Charter defines allowed_domains; navigation outside list raises CharterViolation |
| ACT-B5 | Signed execution receipt | Planned | Every browser session produces a receipt written to audit trail |
M1 — Code Lane (ArcBox)
| ID | Capability | Status | Notes |
|---|---|---|---|
| ACT-C1 | ArcBox (gVisor) container provisioning | Planned | Ephemeral gVisor container per code execution; cleaned up on completion |
| ACT-C2 | Python / JS / shell runtime support | Planned | Three initial runtimes; extensible via runtime registry |
| ACT-C3 | stdout/stderr/exit code result envelope | Planned | Structured output returned to calling agent |
| ACT-C4 | Network egress blocked by default | Planned | Code lane containers have no network by default; charter can grant specific egress rules |
| ACT-C5 | Signed execution receipt | Planned | Receipt includes container ID, runtime, hash of code input, exit code |
M2 — Terminal Lane (ArcBox)
| ID | Capability | Status | Notes |
|---|---|---|---|
| ACT-T1 | Persistent ArcBox container per agent session | Planned | Container persists for session duration; destroyed on session end |
| ACT-T2 | Shell command execution with streaming output | Planned | Long-running commands stream stdout back to the agent in real time |
| ACT-T3 | Scoped mount for file exchange | Planned | Charter-defined directory mounted into container; output accessible via File lane |
| ACT-T4 | Process lifecycle management | Planned | start(), wait(), kill(), status() for long-running process control |
M3 — File Lane
| ID | Capability | Status | Notes |
|---|---|---|---|
| ACT-F1 | read(), write(), move(), delete() on scoped tree | Planned | All operations path-jailed to charter-defined root; no escapes |
| ACT-F2 | Directory listing and glob support | Planned | list() and find() within the scoped tree |
| ACT-F3 | Write permission separate from delete | Planned | Charter fields: can_write, can_delete (default false for both) |
M4 — API Lane
| ID | Capability | Status | Notes |
|---|---|---|---|
| ACT-A1 | Managed credential injection | Planned | Agent specifies credential alias; ArcActuate injects the real key — agent never sees it |
| ACT-A2 | Network egress allowlist per charter | Planned | Charter defines allowed API hosts; calls to unlisted hosts fail at the SDK boundary |
| ACT-A3 | Structured request/response logging | Planned | Full request + response logged to audit trail (body scrubbed of credential headers) |
| ACT-A4 | Retry and timeout configuration | Planned | Per-call retry policy, backoff strategy, and timeout ceiling |