Skip to main content

M9 - OpenClaw as Orchestration Runtime

Status: delivered.

M9 introduced OpenClaw as an optional orchestration runtime pilot while keeping Bloom's built-in runtime as the default and rollback path.

Result​

  • Bloom now has an OrchestrationRuntime seam above the workflow engine.
  • BuiltInOrchestrationRuntime preserves the previous default behavior.
  • RuntimeCorrelationStore records OpenClaw runtime reservations, success, failure, and cached results for idempotent node execution.
  • OpenClawPilotRuntime can route allowlisted low-risk nodes through an OpenClaw execution adapter.
  • The current pilot allowlist is track_progress, a read-only progress refresh path.
  • /health exposes the configured runtime, active runtime, pilot nodes, failure mode, and correlation-store health without leaking gateway URLs, API keys, prompts, or responses.
  • Deployment docs include local validation, staged rollout, production enablement, and emergency rollback.

Current Support Level​

OpenClaw orchestration is available only when explicitly enabled:

BLOOM_ORCHESTRATION_RUNTIME=openclaw_pilot
BLOOM_OPENCLAW_ORCHESTRATION_PILOT_NODES=track_progress
BLOOM_OPENCLAW_ORCHESTRATION_FAILURE_MODE=fallback

The production default remains:

BLOOM_ORCHESTRATION_RUNTIME=builtin

OpenClaw as an LLM provider remains separate:

BLOOM_LLM_PROVIDER=openclaw

Enabling one does not enable the other.

Retained In Bloom​

Bloom still owns:

  • product state and persisted RunState,
  • workflow graph traversal and reducers,
  • GitHub coordination semantics,
  • account/session state,
  • Telegram and GitHub webhook routing,
  • durable job enqueue and event dedupe,
  • GitHub and Telegram side effects,
  • Product Owner review and merge gates,
  • milestone closure.

Out Of Scope​

M9 does not:

  • remove the built-in runtime,
  • route all workflow nodes through OpenClaw,
  • move webhook routing into OpenClaw,
  • move account or product state storage into OpenClaw,
  • route GitHub mutations, Telegram sends, PR review publication, merge decisions, or milestone closure through OpenClaw.

Any removal of the built-in runtime must be planned as a later, explicitly-approved milestone.