Thinking on software identity, agentic development, and the engineering decisions that persist.
The traditional org was designed around code production. An identity-first org is designed around trust production. Here's what changes for product, engineering, compliance, marketing, support, and ops when the identity layer becomes the center.
You can see the gap between what your software declares and what it actually does. Now you need a system for deciding what to fix first. Here is one.
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.
The sharpest objection to identity engineering is that you can't formally verify code against natural-language constraints. That's true. It's also irrelevant. Every quality mechanism in software is probabilistic. Reconciliation just needs to be better than nothing.
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.
Amazon's fix was more review gates. That doesn't scale. The real lesson: AI agents need something to reconcile against before they touch production.
February 2025: vibe coding. February 2026: agentic engineering. The fastest paradigm shift in modern software, month by month.
We use cookies to understand how you use ribo.dev and improve your experience.
Learn more in our Cookie Policy