Ship a project
Several outcomes that share decisions or have to integrate, split across workers in their own worktrees and judged as one candidate.
Several outcomes that need shared decisions or have to integrate. That is the whole test — not headcount, not how many files change, and not whether the ticket says "project".
Ask for it
Forge deliver collaborative editing: presence, live cursors,
conflict resolution, and an offline queue that reconciles on
reconnect. Take it through Acceptance, stop before Ship.How the work splits
One Engineer owns the whole thing and never stops owning it. Workers get bounded outcomes underneath:
| Role | Owns |
|---|---|
| PM | Product scope and what "accepted" means |
| Architect | Contracts, data ownership, trust boundaries, migration |
| Engineer | Strategy, dependencies, worker assignment, integration, repair |
| Workers | One bounded outcome each, with their own writes |
| Reviewer | The verdict on the integrated candidate |
| Judges | One review dimension each, read-only, clean context |
| QA | Acceptance of the combined result, in a separate context |
Each worker gets an outcome boundary, the shared contracts, the files it owns and the proof it is responsible for. Work that does not overlap runs at the same time; work that shares a file is serialized so one writer owns the hot seam.
A worker finishing is not a verdict
Worker returns add no gates. Only the integrated candidate gets judged, by one Reviewer who did not build it.
Approve the shape before the work
At Full depth the spec gate comes with real artifacts — a short PRD, a design doc when experience decisions matter, a technical doc when contracts do. You approve those before anyone builds, which is the cheapest moment to change your mind.
Acceptance is of the whole, not the parts
Every outcome passing individually is not enough when the combined experience is missing or contradicts itself. QA exercises the outcomes, the seams between them, and the existing behavior they touched.
Checking in partway
Forge checkpoint the editing project.You get review and acceptance over the scope that is actually done, and a plain list of what is not. It will not call the project complete to make the checkpoint look better.