Forge Platform

Handbook

Forge Platform

This repository is the platform spine for the Forge ecosystem.

It defines the shared operating model, product boundaries, cross-product contracts, schemas, roadmap, ADRs, prompts, and sprint structure for a governed agentic delivery platform.

Core thesis

Forge is not an agent orchestration product. Forge is a governed delivery control plane with pluggable agent workcells.

The platform makes agentic delivery governable:

  • ForgeSDLC defines the methodology and vocabulary.
  • Blueprints define canonical policy, discipline recipes, Versonas, and evidence expectations.
  • Lenses is the local control plane and human review surface.
  • LCDL owns governed LLM reasoning, verification, repair, and trace summaries.
  • Fleet owns controlled execution, templates, logs, and telemetry.
  • Hermes, Factory Droid, OpenClaw, and future agents are workcells that operate inside the Forge envelope.

Start here

Read these in order:

  1. docs/platform-charter.md
  2. docs/product-boundaries.md
  3. docs/intersection-map.md
  4. docs/roadmap.md
  5. docs/sprint-structure.md
  6. schemas/forge_run.v1.schema.json
  7. schemas/evidence_packet.v1.schema.json

Blueprints and Forge SDLC

This repository vendors the canonical Blueprints framework as a git submodule at blueprints/ (autowww/blueprints). Edit policy and discipline content in the standalone blueprints repo, then bump the submodule pointer here.

Forge operating-model assets for Cursor and daily practice live under:

  • forge/forge.config.yaml — team scale, ceremony weight, and which Versona discipline capabilities are active (product, engineering, governance, security, compliance, and sub-disciplines).
  • forge/, ember-logs/, forge-logs/ — Charge, journal, evidence, and Versona session tracking per Blueprints conventions.

After updating the blueprints submodule, or after toggling Versonas in forge/forge.config.yaml, re-align Cursor rules:

git submodule update --init --recursive
bash blueprints/sdlc/methodologies/forge/setup/sync-forge-cursor-rules.sh status --preset recommended
bash blueprints/sdlc/methodologies/forge/setup/sync-forge-cursor-rules.sh sync --preset recommended
bash blueprints/sdlc/methodologies/forge/setup/sync-forge-cursor-rules.sh sync
bash blueprints/sdlc/methodologies/forge/setup/sync-forge-cursor-rules.sh check

Use sync --preset recommended for the standard bundle, then sync (no preset) so any extra disciplines enabled in forge.config.yaml (for example compliance) get their matching .mdc files.

Validation

python3 scripts/check_foundation.py

The check script uses only Python standard library. It verifies required files exist, parses JSON schemas and samples, and checks that sample schema fields match expected schema identifiers.

Non-goals

This repo should not become:

  • a UI runtime,
  • a job runner,
  • an LLM task runner,
  • an autonomous agent,
  • a product-specific implementation repo.

It should stay the shared platform spine.