Essay11 min read
Agents Converge the Same Way Models Do
A fleet of agents editing a codebase is a learning system whether you designed it that way or not. Without a declared identity, there is no loss function, and nothing converges.
Insights
Thinking on software identity, agentic development, and the engineering decisions that persist.
Essay11 min read
Same DNA, Native Everywhere: Why Cross-Platform Was the Wrong Abstraction
The industry answered 'two platforms, one product' by sharing code. But the thing that needed sharing was never code — it was identity. When identity is the source of truth and each platform has its own ribosome layer, you get two fully native codebases that honor the same contracts, run independent experiments, and cost tokens instead of headcount.
Essay14 min read
Eight Laws from 1974 That Predicted the Need for Software DNA
In 1974, Meir Lehman formulated laws of software evolution that describe how real-world systems inevitably change, grow complex, and decline. For fifty years, humans were the only mechanism for honoring those laws. Identity engineering is the first architecture that can honor them at the speed they actually demand.
Essay12 min read
The Ribosome Layer: Where Identity Becomes Code
Between what your software should be and the code that runs, there's a translation layer the industry never named. It determines the language, the frameworks, the quality constraints, and the idioms. We call it the Ribosome Layer, because that's what ribosomes do: read instructions and produce functional output given available materials and environmental constraints.
Essay10 min read
Every Developer Has a Different AI. That's the Problem.
Your team uses six different AI setups across five editors with four models and three rules file formats. The same ticket produces wildly different code depending on who picks it up. Standardizing tools won't fix this. An identity layer will.
Essay10 min read
The Brand Moved. The Code Didn't.
Every company eventually repositions. Marketing updates the website in days. Sales starts pitching the new story in weeks. The codebase is still what it was yesterday. Here's how to close the gap between what your company says it is and what the software actually does.
Essay16 min read
The DNA-First Organization
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.
Essay9 min read
Prioritizing the Delta: What to Reconcile First
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.
Essay9 min read
Reconcile, Don't Generate. The Lesson Every Declarative System Had to Learn.
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.
Essay10 min read
Your Software Is Never Done. That's the Point.
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.