Forge Platform

Handbook

L1 — Function

Status: Demonstrated — PoC runs with machine evidence (Blueprints Examples 1–2).

Level at a glance
Autonomous unit One method/function to a given signature/contract
What stays fixed Architecture, API, tests
Human gate Approve branch/merge

Canonical policy: Autonomy levels (Blueprints).

Building blocks at this level

Building block Role at L1 Handbook link
Forge Dark Factory (PoC) Reference unattended loop: classify → route → plan → draft → apply → verify Bounded execution examples
forge-lcdl Patch units, verify, repair, proof Platform reference architecture §5
forge-workcells Optional local_llm_worker in worker ladder Forge micro-agent
blueprints Assay gate ceremony; forge.config.yaml core evidence Assay Gate
forgesdlc-kitchensink Harness rules, deterministic scaffolds Platform reference architecture §8

Platform ForgeRun / workcells are not required for the PoC path today; L1 is demonstrated in Dark Factory outside the Platform submodule tree.

Reference architecture flow

  [Campaign item declares L1]
        |
        v
  +------------------+
  | Dark Factory PoC |
  | classify + route |
  +--------+---------+
           |
           v
  +------------------+     +------------------+
  | forge-lcdl       |<--->| forge-workcells  |
  | patch unit plan  |     | local_llm_worker |
  | verify / repair  |     | (optional)       |
  +--------+---------+     +------------------+
           |
           v
  +------------------+
  | apply + verify   |  --> 1 file typical
  +--------+---------+
           |
           v
  +------------------+
  | assay gate       |  tests_pass, acceptance_criteria_met,
  | (forge.config)   |  risks_reviewed
  +--------+---------+
           |
           v
  +------------------+
  | dual-wiki trace  |  machine/ + human/report.md
  +--------+---------+
           |
           v
  [Human: approve branch/merge]

Gates and evidence

Core evidence from forge/forge.config.yaml:

  • tests_pass
  • acceptance_criteria_met
  • risks_reviewed

At L1, one patch unit and typically one changed file suffice. The Assay gate does not require multi-file proof (that is L2).

PoC evidence: poc-sandbox-offline (deterministic, 0 tokens) and L1-a-broken-link (lenses-production campaign) — see Bounded execution examples.

Implemented vs planned
Implemented Dark Factory loop; LCDL patch units; assay gate in assay_gate.py; worker ladder (local → cursor → deterministic → fake); dual-wiki trace
Not implemented Platform-native L1 enforcement on ForgeRun/workcells; unsupervised push/deploy
Planned Wire PoC patterns into governed Campaign workcells under Lenses ForgeRun