Integrations
OpenClaw
Archetype: EventBus — @loop-engine/adapter-openclaw forwards selected loop events to OpenClaw's gateway; governed transitions go through loopSystem.engine.transition(...).
What it does
Loop Engine provides the decision governance layer for OpenClaw workflows. OpenClaw handles agentic reasoning and tool orchestration; Loop Engine governs which actions are authorized, by whom, under what policy, and records full attribution for each transition.
This is the Sense → Decide → Govern pattern in practice:
- OpenClaw retrieves context and reasons over it (
Decide) - Loop Engine evaluates policy and transition guards (
Govern) - Action executes only after the loop permits it (
Execute)
Quick setup
-
Install
1npm install @loop-engine/adapter-openclaw @loop-engine/sdk -
Wire Loop Engine into an OpenClaw workflow
1"cmt">// @no-typecheck2import { createLoopSystem } from "@loop-engine/sdk";3import { OpenClawAdapter } from "@loop-engine/adapter-openclaw";45const loopSystem = await createLoopSystem({6 loops: [procurementLoop]7});8"cmt">// loopSystem is { engine: LoopEngine, signals?: SignalEngine, eventBus: InMemoryEventBus }910const openclaw = new OpenClawAdapter({ engine: loopSystem.engine }); -
Define the governed decision point
1"cmt">// @no-typecheck2const proposal = await openclaw.proposeAction({3 workflowId: "procurement-workflow",4 action: "submit_purchase_order",5 input: { vendor: "Acme Medical Devices", amount: 9200 }6});78await loopSystem.engine.transition({9 aggregateId: proposal.aggregateId,10 transitionId: proposal.transitionId,11 actor: proposal.actor,12 evidence: proposal.evidence13});
How it works
- OpenClaw agent proposes an action
- Adapter maps proposal to a Loop Engine transition
- Runtime evaluates guards and policies
- Human approval gate pauses when required
- Approved transition executes and is fully audited