Forge Platform

Handbook

Product Repo Adoption

Each product repo should add a thin local adoption layer.

Required folder

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

Product boundary template

# Product Boundary

## Owns

## Does not own

## Consumes

## Emits

## MVP responsibilities

## Out of scope

Rule

Do not duplicate canonical schema definitions in product repos. Reference forge-platform/schemas/.

Do not submodule forge-platform

Product repos must not add forge-platform as a git submodule. Use:

  • sibling clone in the workspace,
  • handbook links from forge-platform-website,
  • CI checks that validate emitted JSON against platform schema IDs.

To run workcells locally, submodule autowww/forge-workcells (private) or pip install -e from a sibling checkout — not platform.

See Repository strategy and Ecosystem reference.