Forge Platform

Handbook

Workcell catalog

Maintained table of workcell ids. Update this page when adding runners; mirror key rows in ecosystem reference sample samples/ecosystem_reference.v1.json when appropriate.

Workcell id Role Runner host Typical mode Primary contract Handbook
hermes operator Hermes operator / proposal workcell_request / workcell_result Hermes integration
factory implementation_worker Factory Droid sandboxed_implementation workcell envelopes Factory integration
openclaw channel_gateway OpenClaw readonly / proposal workcell envelopes OpenClaw integration
local_runner operator forge-platform operator local_runner_action / local_runner_result Self-Host local runner
local_llm_worker reviewer forge-workcells proposal workcell envelopes + micro-pack Forge micro-agent
campaign_orchestrator operator operator host / CI operator workcell + campaign manifest Forge Campaign
fleet_ux_worker implementation_worker Fleet container sandboxed_implementation workcell + Fleet workspace bridge Forge Campaign
cursor_cli implementation_worker operator / container sandboxed_implementation workcell envelopes Forge Campaign

Role types

From Workcell model:

  • operator — orchestration and coordination
  • implementation_worker — code, patches, container work
  • reviewer — second-pass or judgment-only
  • channel_gateway — chat/mobile ingress
  • versona_runner — discipline-lens review
  • evidence_summarizer — evidence packaging

Adding a workcell

  1. Choose a stable id (snake_case).
  2. Add schemas/samples if new fields are required (schemas/workcell_request.v1.schema.json).
  3. Implement the Forge runner in forge-workcells or document product-repo exception.
  4. Update this catalog and Forge Agent table.
  5. Register in ecosystem reference sample when the repo joins the topology.