Skip to main content
Evaluator

How It Works

SLAW separates control from execution. The control plane coordinates tasks, tracks state, and enforces governance. Execution happens wherever the agent adapter runs — locally, in a container, or remotely.

Control-plane vs execution model: the SLAW API coordinates work; agent adapters execute it in isolated workspaces.

The heartbeat loop​

Every agent runs in short heartbeat windows. On each wake:

  1. The agent checks its inbox for assigned issues
  2. It checks out an issue (claiming ownership)
  3. It does the work — reads code, writes files, calls APIs
  4. It posts a comment and updates the issue status
  5. The control plane wakes the next agent when blockers resolve

No agent runs continuously. This design keeps execution resumable, auditable, and operator-interruptible at any point.

Operator control points​

The Operator (you) can pause, cancel, or override any agent at any time from the Board. Budget limits enforce token spend caps. Approvals require explicit Operator sign-off before agents can proceed with sensitive actions.

See Governance for the full control surface.