It's been a long time since i posted here.

We have moved to the agentic era, a new shitstorm of bad software is coming online.

Software that is sloppy, brittle and unrefined.

The main culprit of fragility at this current period is the agentic part. 

Your agent has one version number and four things that decide what it actually does.

> Ship a change to the orchestration code, tag it, done. That covers one of the four.

>> The instructions and policy block is the second. Also yours, also the one everyone treats as the whole system, right up until the third and fourth parts move without telling you.

>> The model runtime is the third. A vendor's pinned snapshot, sitting in Active, Legacy, Deprecated, or Retired, on that vendor's own lifecycle, with a minimum notice period before it goes away. Anthropic's is 60 days. That is one company's policy. It binds nobody else's model, and it does not ask what your regression suite thinks.

>>> The fourth is the protocol and tools your agent calls out through. MCP now stamps a dated version string on every single request, which is more discipline than most teams manage on their own code. The tool schemas sitting behind that protocol still version on their own schedule, with no such stamp, and no one upstream is watching your integration tests when they change.

Most teams have a git log for the first two and nothing for the last two, then act surprised when the agent that passed every eval last month answers differently this month with no local commit to blame.

I put the rest of it in the attached deck: the release pipeline for a system that cannot be tested to certainty, what decides whether a rollback is even possible, and the four OWASP agentic-risk entries that are this problem read as a containment question.

 

Presentation here: https://drive.google.com/file/d/1rAghJ-Wcp57gFey1caBpA8xKWenz28eB/view?usp=drive_link