Handbook

L4 — Feature/component

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

Updated 2026-07-26

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).

Sub-levels

Sub-level	Autonomous unit	Status	Page
L4.1	New component, single repo	Defined (vision gates)	L4.1
L4.2	Cross-repo change-set with submodule bump	Defined (vision gates)	L4.2
L4.3	Capability with agent-drafted, human-signed ADR	Defined (vision gates)	L4.3

L4.2 has wider span than L4.1 but lower architectural risk — sub-levels within a level are peer variants ordered by typical adoption, not strictly increasing risk.

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)

L4 feature component flow

How ADR-backed release intent becomes a governed multi-repo campaign with evidence review before human sign-off.

[ADR + release intent]Human records architectural decisions and release goal before work starts.
forge-lensesForgeRun control plane holds the campaign as system of record.
Forge Campaigncampaign.yaml declares multi-repo phases across modules.
[repo A]First repository executes its campaign phase with bounded changes.
[repo B]Second repository executes its campaign phase in parallel.
workcellsOrchestrator and workers run campaign tasks; Fleet may execute docker_argv jobs.
EvidencePacketCollects audit, build, and quality-gate proof from all phases.
[Human: ADR sign-off + release gate]Operator signs ADR and passes Assay Gate before promotion.

    [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

Forge Platform