Git isolation
Physical isolation rather than a promise to be careful. Each engineer task builds in its own worktree, and a file outside its declared scope fails a gate before anything else runs.
How the isolation works#
- A branch and a worktree per task
- Created under the project working directory, so concurrent tasks cannot see or clobber each other, and your checkout is never the build surface.
- A jailed tool set
- The engineer’s file tools are scope-checked. Reaching outside the task’s declared paths is not a warning; it is refused.
- Scope is a gate, not a guideline
- A file outside the declared scope fails the second gate, before the tree is even compiled.
- Disjoint service directories
- A multi-service plan gets disjoint scopes by construction, so the planner does not have to negotiate them.
Merging is a separate, verified step#
Task branches are assembled into an integration branch by a dedicated role, which probes cross-task contracts, runs every service’s suite and then starts the application.
That is the first moment anything is looked at as a whole — and the last moment before the gate that decides whether it can leave your machine.
Common questions
Can an agent modify files I did not ask it to touch?
Not without failing the scope gate. The tool set is jailed to the task’s declared paths, and the gate re-checks the diff independently.
Does it commit to my current branch?
No. Work happens on its own branch in its own worktree, and reaches your remote only through the ship gate.