Forge Platform

Handbook

Repository Strategy

Keep forge-platform as a sibling repo in the same Cursor workspace as product repos. Blueprints is embedded in forge-platform as a submodule at forge-platform/blueprints/ (pin updates from the standalone…

Keep forge-platform as a sibling repo in the same Cursor workspace as product repos. Blueprints is embedded in forge-platform as a submodule at forge-platform/blueprints/ (pin updates from the standalone autowww/blueprints repo). Other product repos may still mount blueprints separately when needed.

workspace/
  forge-platform/        # sibling governance (schemas, ADRs) — never submodule of products
    blueprints/          # submodule → autowww/blueprints
    forge/               # Forge SDLC config + Charge paths
  forge-workcells/       # private — workcell runners (local_llm_worker, …)
  forge-lenses/
  forge-lcdl/
  forge-fleet/
  forgesdlc-kitchensink/
  forge-platform-website/  # handbook only; submodules forge-platform for build
  forgesdlc-site/
  lenses-site/
  lcdl-site/
  fleet-site/

Platform is never a product submodule

forge-platform must not appear as a git submodule inside product repos (Lenses, Fleet, Kitchen Sink, certificators, etc.). Products consume platform truth via:

  • published handbook URLs (forge-platform-website),
  • schema identifiers and samples referenced in docs/CI,
  • sibling clone in the same Cursor workspace.

Exception: forge-platform-website alone submodules forge-platform to run generator/build-site.py.

forge-workcells is a separate private repo for runnable workcells. Consumers (KS, later Lenses) submodule workcells, not platform.

Split of responsibility

forge-platform owns canonical cross-product truth:

  • architecture,
  • product boundaries,
  • schemas,
  • sample objects,
  • roadmap,
  • prompts,
  • ADRs,
  • milestone/sprint structure.

Each product repo owns only its local implementation slice:

product-repo/
  docs/forge/
    product-boundary.md
    contracts-consumed.md
    contracts-emitted.md
    roadmap-slice.md
    prompts/
    evidence/

Current recommendation

Keep schemas and contracts authoritative in forge-platform. The blueprints submodule provides canonical methodology, Versonas, policy, and setup scripts (forge-init, Cursor rule sync). Initialize it with git submodule update --init --recursive after clone.