Handbook
L6 — Product increment
Status: Vision (grade a) — policy defined; no PoC or Platform-native enforcement today. L6 stays flat — no sub-levels are defined for vision-stage levels.
Updated
Level at a glance
| Autonomous unit | Multi-repo, multi-service on a single cloud/platform |
| What stays fixed | Cloud/platform choice |
| Human gate | Go/no-go |
Canonical policy: Autonomy levels (Blueprints).
Building blocks at this level (planned)
| Building block | Planned role at L6 | Handbook link |
|---|---|---|
| forge-lenses | Product Spark / milestone tracking via ForgeRun | Workflows and runs |
| Forge Campaign | Multi-repo stack with pr_stack_order, CI wait |
Forge Campaign |
| forge-fleet | Container execution for build, audit, deploy-adjacent jobs | Platform reference architecture §6 |
| forge-workcells | fleet_ux_worker, campaign_orchestrator |
Workcell catalog |
| blueprints | Product Spark; Assay Gate; go/no-go ceremony | Planning flow |
| forge-platform | Ecosystem reference; multi-service topology | Ecosystem reference |
Reference architecture flow (planned)
L6 product increment flow
How Product Spark intent becomes a governed multi-service increment with coordinated PRs before human go/no-go.
- [Product Spark / go-no-go intent]Product Spark defines increment scope and acceptance criteria before execution.
- forge-lensesForgeRun tracks the Product Spark as the system of record.
- Forge CampaignCampaign manifest coordinates repos and Fleet profile across services.
- forge-fleetFleet runs containerized build and audit jobs with workspace upload.
- [service A]First service receives coordinated changes in the PR stack.
- [service B]Second service receives coordinated changes in parallel.
- CI + AssayCampaign waits for multi-repo CI green before Assay evidence review.
- [Human: go/no-go]Human decides whether the product increment ships.
[Product Spark / go-no-go intent]
|
v
+------------------+
| forge-lenses | ForgeRun per Product Spark
+--------+---------+
|
v
+------------------+
| Forge Campaign | repos[] + fleet profile
| multi-service |
+--------+---------+
|
v
+------------------+
| forge-fleet | docker_argv jobs
| build / audit | workspace upload
+--------+---------+
|
+-----+-----+
v v
[service A] [service B] coordinated PR stack
| |
+-----+-----+
|
v
+------------------+
| CI + Assay | wait_for_ci: true
+--------+---------+
|
v
[Human: go/no-go]Gates and evidence (vision)
Inherits L5 gates, plus:
- Go/no-go decision before increment ships
- Multi-repo CI green across campaign
repos[] - Product Spark acceptance criteria met
Implemented vs planned
| Implemented | Policy table row; Campaign manifest fields (fleet, integration); Fleet job API |
| Not implemented | L6 autonomous product increments; end-to-end demonstrated runs |
| Planned | Campaign templates for Product Spark scope; Fleet-backed verify phases |