Three agents, one repository.
Two changes integrate cleanly. The third overlaps and comes back as a structured conflict instead of being merged silently. Integration safety means acknowledged changes are not lost; it does not make the combined code semantically correct. Your tests and review still do that.
Fig. 05 — Concurrent integration · step 1 / 9 · Illustrative simulation, not a live backend
Tasks assigned
main
Keyboard: focus the figure, ← → to step, R to reset. Illustrative simulation — not a live backend.
What integration safety means
Every candidate is validated against the authoritative state at publication time. A change either integrates atomically and is acknowledged to its agent, or it overlaps and returns as structured data the agent can inspect — file, region, base and the overlapping revision. Nothing is merged silently.
