Diffusion of responsibility occurs when accountability is spread across people or agents until no individual owns the outcome. In AI-assisted development, “the model wrote it” and “someone will check it” can combine to leave generated code unverified. section 1.4
The dump-and-review handoff
A developer generates a large change, opens a pull request without reading the diff, and feeds reviewer comments back to the agent until it merges. Verification has not disappeared: it has moved to a reviewer with less context and time. A quick approval and passing tests do not establish that important invariants hold. section 1.4
Unverified code creates trust debt: someone must eventually understand it, potentially under pressure. Late handoffs also encourage shallow review and overreliance on green tests. section 1.4
Counter the diffusion with explicit ownership: someone must stand behind the change and understand its assumptions, failure modes, effects, and where to investigate when it breaks. The team should be able to explain why the system behaves as it does and notice when it stops. section 1.5
