Sequential and Parallel Delivery
Release dependency-ready work through task gates and active write scopes
Harness implementation uses a dependency graph, task gates, and active write scopes. The route keeps its old URL for compatibility. The parent coordinates and validates; scoped workers implement plan tasks.
Worker Waves
create-plan records task dependencies, owned paths, validation, and shared
integration points. implement-spec launches every currently unblocked task whose
write scope is disjoint. When a task passes its Task Gate, the parent reconciles its
result and immediately releases newly eligible dependents; unrelated work does not
wait for the rest of a wave.
When two tasks would edit the same file or contract, the dependency graph orders them or transfers the active write scope to one explicit owner.
Ownership
- The parent owns the plan graph, wave construction, shared artifacts, integration, and final judgment.
- Each worker owns one bounded task and its declared paths.
- Workers preserve changes outside their scope and report evidence, blockers, and touched files.
- Shared files have one explicit owner in a wave.
Required Plan Shape
Before implementation starts, the plan must provide:
- task dependencies and the first unblocked wave;
- owned and forbidden paths for each task;
- required skills and read-first sources;
- validation for each task and the combined change;
- the owner of shared integration work.
Failure Handling
A failed worker or validation gate blocks its dependent tasks. Independent tasks may continue if their premises remain valid. The parent records the failure, repairs the plan or scope, and rebuilds the next unblocked wave from current evidence.
Done Signal
Delivery closes after every required task is validated, shared artifacts are reconciled, the combined change passes its acceptance audit, and the final report names remaining blockers honestly.