Forge Platform

Handbook

Workflows and runs

How ForgeRun, AgentRuns, Fleet jobs, campaigns, and harness runs relate. For conditional rules (approval, DecisionPack, campaign phases) see Governed workflows and rules.

ForgeRun spine (production)

Human intent
  -> Lenses opens ForgeRun (frun_*)
  -> BlueprintContextPack (optional)
  -> WorkcellRequest -> Forge runner -> WorkcellResult
  -> LCDLTraceSummary / FleetJobSummary (optional)
  -> EvidencePacket
  -> Lenses review / ForgeRun decision

On-disk alpha layout: Self-Host run store.

Parallel paths under one ForgeRun

                    ForgeRun (frun_*)
                           |
         +-----------------+------------------+
         |                 |                  |
         v                 v                  v
   [B] Campaign      [C] LCDL graph      single workcell
   orchestrator      DecisionPack        (one AgentRun)
   + Fleet job        + trace summary     e.g. local_runner
         |                 |                  |
         +-----------------+------------------+
                           v
                  EvidencePacket + decision
  • [B] — Forge Campaign: manifest-driven phases, not DecisionPack.
  • [C] — Governed workflows and rules: LCDL DAG attached via trace/evidence (R3 visibility on Lenses).
  • Single workcell — one runner invocation per AgentRun (typical Self-Host Alpha).

Forge Campaign flow

Operator -> frun_* + campaign.yaml
         -> campaign_orchestrator: branches, pack, POST Fleet
         -> fleet_ux_worker (container): audit/remediate
         -> orchestrator: integrate, PR stack, verify
         -> EvidencePacket + Lenses decision

See Forge Campaign for manifest and lifecycle states.

Fleet-only execution

Approved FleetTemplate
  -> POST /v1/jobs (+ workspace upload)
  -> poll terminal state
  -> FleetJobSummary -> EvidencePacket path -> Lenses

No campaign required when a single template job satisfies the intent.

Harness / auditor (development)

KS fixture + ruleset
  -> analyze / assemble context
  -> optional --llm -> local_llm_worker OR Cursor CLI
  -> parse findings -> detection gate

ForgeRun is optional in harness mode; contracts still align when recording an AgentRun for integration tests.

Separate agents as workcell ids

Hermes, Factory Droid, OpenClaw, Cursor CLI, and future agents appear as workcell ids on AgentRuns — not as alternate run models. See Workcell catalog.