Concurrency

A PR at PhoenixDX passed review clean — no errors, no crash, no merge conflict — and it was still wrong, because two agents had quietly overwritten each other's memory of the codebase and nothing in the system was built to notice.

A Lamport clock will always tell you which event came first — even when that's a lie — and the fix for it, vector clocks, turns out to be exactly what your multi-agent pipeline needs before a merge quietly erases someone's work.