Handbook

OpenClaw Integration

OpenClaw is a channel gateway workcell.

Updated

Positioning

OpenClaw is a channel gateway workcell.

OpenClaw owns:

  • messaging ingress,
  • session/channel routing,
  • status relay.

OpenClaw does not own:

  • approval authority,
  • execution,
  • canonical ForgeRun state,
  • governance policy.

Governed chat gateway lane

Chat requests enter through OpenClaw while Lenses governs ForgeRun state and relays bounded status back.

  1. Chat/mobile messageA user sends a request through a chat or mobile channel.
  2. OpenClaw creates ChatIntentThe gateway normalizes the inbound message into a bounded ChatIntent.
  3. Lenses creates or updates ForgeRunLenses governs the canonical ForgeRun record from the intent.
  4. OpenClaw relays status/evidence summaryBounded status and evidence summaries return to the user through the gateway.

Rule

Chat can request. Lenses must govern. Fleet executes. Evidence returns.

Matrix channel (implemented)

Operator setup: Agent communication guide — Element at element.forgedc.net, Synapse at matrix.forgedc.net, NATS on Granite, forge-cursor-bridge on the laptop.

Architecture summary: openclaw-matrix-channel.md.