Thinking on software identity, agentic development, and the engineering decisions that persist.
Every turn an agent spends rediscovering what a function is, who owns it, and what it promises is a tax on your latency, your token bill, and your error rate. The fix is not more context. It is identity upstream of discovery.
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.
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.
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.
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.
Terraform proved infrastructure should be declared. The same transformation is coming to application software. The specification becomes the source of truth.
You wrote a spec. Your AI agent ignored it. Here is why, and how to write specifications that agents actually respect.
Specs drift because they describe states. Deltas survive because they describe decisions. Stop writing better documents. Start declaring better deltas.
Context changes per request. Identity persists across sessions, tools, and team members. Context engineering without identity engineering is a database query without a schema.
More context isn't the answer. The right context is. Your agent needs a schema to query, not a haystack to search.
We use cookies to understand how you use ribo.dev and improve your experience.
Learn more in our Cookie Policy