
Convergence Mechanisms: Confidence in the Age of Agentic Engineering
A useful agentic change does not end when the diff appears. It ends when the system is coherent again.
I watched this exact loop last month: we asked an agent to tighten signup validation. It updated the form, the server-side validator, even the e2e test. Green across the board. We shipped. Two minutes later realized the password reset was broken.
A software change is not merely code moving. It is a shift in the requirement set.
There's a gap between the physical system (code, tests, schemas, diffs) and the theoretical system (requirements, contracts, constraints). Agents edit the former. We care about the latter.
When those two layers drift apart, an agent can satisfy the explicit task while breaking an implicit requirement nobody named and no automated check protects.
This post is my attempt to reason about that gap, and how to structure an agentic engineering harness around requirements, contracts, and deterministic feedback loops instead of just writing longer instruction files.
If you're interested, give it a read. If not, maybe let me know what I could do better!
Appreciate any feedback, and happy to partake in discussions :)