How agents avoid overwriting one another
Nexus decomposes a delivery plan into explicit work slices and gives each active lane a defined scope. Agents work in isolated repository state rather than sharing one mutable working directory.
Ownership is fenced. If a worker fails, times out or is replaced, its old token no longer authorises delivery. That prevents late results from overwriting newer work even when the old worker eventually returns.
- Bounded files and acceptance criteria
- Isolated branches or worktrees
- Lease and fencing-token checks
- Stale-worker rejection
