Forge Platform

Handbook

L4 — Feature/component

Status: Vision — policy defined; no PoC or Platform-native enforcement today.

Level at a glance
Autonomous unit Capability across modules; may add a component within existing architecture; cross-repo, one platform
What stays fixed Platform, major architecture
Human gate ADR + release gate

Canonical policy: Autonomy levels (Blueprints).

Building blocks at this level (planned)

Building block Planned role at L4 Handbook link
forge-lenses ForgeRun system of record; evidence review before release Workflows and runs
Forge Campaign Multi-repo effort under one frun_*; manifest phases Forge Campaign
forge-lcdl Governed reasoning graphs for complex planning Platform reference architecture §5
forge-fleet Optional container execution for audit/remediate workers Platform reference architecture §6
forge-workcells campaign_orchestrator, fleet_ux_worker, cursor_cli Workcell catalog
blueprints ADR ceremony; Assay Gate at release boundary Assay Gate
forge-platform Schemas, ADRs, ecosystem contracts Platform reference architecture

All L0–L3 blocks remain available for sub-tasks within an L4 campaign; L4 adds cross-module scope and ADR/release gates.

Reference architecture flow (planned)

  [ADR + release intent]
        |
        v
  +------------------+
  | forge-lenses     |  ForgeRun frun_*
  | control plane    |
  +--------+---------+
           |
           v
  +------------------+
  | Forge Campaign   |  multi-repo manifest
  | campaign.yaml    |  phases across modules
  +--------+---------+
           |
     +-----+-----+
     v           v
  [repo A]    [repo B]     topic branches, submodule bumps
     |           |
     +-----+-----+
           |
           v
  +------------------+
  | workcells        |  orchestrator + workers
  | + forge-fleet    |  optional docker_argv jobs
  +--------+---------+
           |
           v
  +------------------+
  | EvidencePacket   |  audit, build, quality gate
  +--------+---------+
           |
           v
  [Human: ADR sign-off + release gate]

Gates and evidence (vision)

Inherits all L0–L3 gates for constituent work, plus:

  • ADR recorded for architectural decisions introduced at this level
  • Release gate (Assay Gate ceremony) before promotion
  • Cross-module acceptance criteria in campaign manifest

No automated L4-specific assay exists in Dark Factory or Platform workcells today.

Implemented vs planned
Implemented Policy table row; Forge Campaign manifest sketch; workcell catalog ids
Not implemented L4 assay enforcement; demonstrated multi-module autonomous delivery
Planned Campaign orchestrator with L4 manifest constraints; ADR linkage in EvidencePacket