Forge Platform

Handbook

Platform sibling layout and forge-workcells

Accepted for Micro Agent MVP.

Status

Accepted for Micro Agent MVP.

Context

Forge Platform holds cross-product schemas and governance. Runnable workcell code was growing in platform scripts (selfhost_runner.py) and in Kitchen Sink UX harness glue. Product repos were at risk of submoduling platform for convenience.

Decision

  1. forge-platform remains a sibling repo in the workspace. Product repos must not submodule platform. The only exception is forge-platform-website, which submodules platform to build the private handbook.
  2. forge-workcells is a private implementation repo (autowww/forge-workcells) for workcell runners (local_llm_worker, future workcells). Platform owns contracts and glossary; workcells owns execution code.
  3. Domain micro-packs (e.g. UX AI rule prompts) stay in forgesdlc-kitchensink under tools/forge-micro-agent/packs/. KS may submodule forge-workcells via SSH; it must not submodule forge-platform.
  4. Blueprints continues to submodule into platform at forge-platform/blueprints/ only.

Consequences

  • Clear split: governance (platform) vs runners (workcells) vs packs (KS).
  • CI and clones that use KS --llm need read access to private forge-workcells.
  • Lenses will orchestrate workcells post-MVP by submoduling forge-workcells, not platform.
  • ecosystem_reference.v1 documents topology for handbook readers and tooling.