Handbook
Workcells terminology
Deep glossary for the workcells hub. For platform-wide terms see Glossary.
Run vs job vs workflow
| Term | Meaning | Common mistake |
|---|---|---|
| ForgeRun | Governed container; Lenses SoR | Calling a Fleet job a “run” |
| Fleet job | One container execution | Treating job id as frun_* |
| AgentRun | One agent session under a ForgeRun | Confusing with Cursor chat outside ForgeRun |
| Harness run | KS auditor/ruleset output dir | Assuming every harness has frun_* |
| Governed workflow | LCDL graph or operator chain | Same as Blueprint Versona playbook |
| Campaign phase | Orchestrator status from manifest | Same as DecisionPack node |
Workcell vs runner vs agent
| Term | Meaning |
|---|---|
| Forge Agent | Pattern name for a governable session |
| Workcell | Role contract (WorkcellRequest / WorkcellResult) |
| Workcell id | Stable string in manifests and CLI |
| Forge runner | Process or library that implements the workcell |
| Hermes | Optional adaptive operator workcell (not required for governance) |
Rule: Say local_llm_worker or campaign_orchestrator in specs; reserve “Forge Agent” for the pattern doc.
Conditional rules (three models)
Do not conflate these — detail in Governed workflows and rules:
| Model | Mechanism | Owner |
|---|---|---|
| A — Approval gate | ApprovalRequest + workcell mode |
Lenses + platform |
| B — Campaign procedural | campaign.yaml statuses, Fleet poll |
Orchestrator workcell |
| C — LCDL graph | DecisionPack, llm_boolean_gate, operators |
forge-lcdl |
DecisionPack and operators
| Term | Meaning |
|---|---|
| DecisionPack | Versioned DAG (nodes, depends_on, gate tasks) |
| LCDL operator | seq, fallback_chain, until_ok — composition helpers |
| Hermes operator | Adaptive tool/MCP choice under policy — not a DecisionPack |
Micro-agent and harness
| Term | Meaning |
|---|---|
| Micro-pack | Fixed prompt + manifest in KS tools/forge-micro-agent/packs/ |
| Micro-agent | One bounded LLM judgment via local_llm_worker |
| AI.* / DET.* | KS UX ruleset rule ids — quality harness, not platform workflow engine |
Anti-patterns
- Using “forge-agent” when a specific workcell id exists.
- Storing canonical campaign state only in Fleet or Hermes (Lenses + ForgeRun own the spine).
- Implementing multi-step DAG orchestration inside forge-workcells without an explicit workcell design.
- Equating Forge Campaign with a marketing campaign or
charge/*Git branch.