Thinking on software identity, agentic development, and the engineering decisions that persist.
MDA tried to generate code from declarations and failed. Identity engineering reconciles code against declarations — a structurally different pattern with a proven track record in infrastructure.
Burndown charts assume a fixed destination. But software identity is a moving target. The metric that matters isn't whether you hit zero — it's the rate at which your system converges toward what it's supposed to be right now.
The strongest objection to identity engineering is that a wrong identity faithfully enforced is worse than no identity at all. The objection is correct. That's why the humans defining it carry the hardest job.
Specs drifted. Docs rotted. Tribal knowledge walked out the door. The code became the source of truth by default -- not because it's good at the job, but because everything else died first.
Spec-driven development produces documents that drift. Identity engineering produces a living layer that agents reconcile against continuously. The shift isn't technological — it's organizational. Here's what the operating model actually looks like.
February 2025: vibe coding. February 2026: agentic engineering. The fastest paradigm shift in modern software, month by month.
Terraform proved infrastructure should be declared. The same transformation is coming to application software. The specification becomes the source of truth.
Everyone's talking about AI code quality. The actual problem is cognitive debt, verification debt, and architectural debt, and your linter can't catch any of them.
Bill Eisenhauer proposed that specifications are the durable artifact and code is a regenerable rendering. The natural next question: what does the infrastructure look like that makes that work at enterprise scale?
If you were hiring today knowing AI writes 41% of the code, would you build the same org? The roles, the teams, the governance -- it all changes.
We use cookies to understand how you use ribo.dev and improve your experience.
Learn more in our Cookie Policy