Book a demo
Topics · GOVERNANCE-AGENTS

Asset management AI agent registry Version Control | Moring

Version control in an asset management AI agent registry records every material change to an agent, model upgrades, tool changes, permission changes, and configuration edits, as a distinct version with an owner and approval state. This makes the estate's change history auditable and gives rollback a reliable foundation.

On this page
  1. Short answer
  2. How it works
  3. FAQs
  4. Related reading
  5. Sources

Short answer

Version control in an asset management AI agent registry records every material change to an agent, model upgrades, tool changes, permission changes, and configuration edits, as a distinct version with an owner and approval state. This makes the estate's change history auditable and gives rollback a reliable foundation.

How it works

Agents change constantly: models are upgraded, tools are added, prompts and configurations are tuned. MuleSoft's account of agent asset management describes governing agents, models, MCP servers, and tools across a structured lifecycle, and version control is the lifecycle mechanism that keeps those changes visible rather than silent. In an asset management registry, every material change to a registered agent should produce a new version in its record, with the previous configuration retained.

What counts as material should be defined narrowly enough to catch risk-relevant changes: a model version change, a new tool grant, an expanded permission scope, a change of owner, or a change to control configuration such as rate limits or approval requirements. Cosmetic changes, like descriptions, can be edited in place. The distinction matters because version control is a control surface, not a documentation habit: each version is what reviewers approve, what runtime enforces, and what rollback restores.

The approval linkage is what elevates version control above a change log. When a new version is proposed, the registry routes it through the same review that governed the original registration: does the changed scope remain justified, does the new model version carry validation, does the owner confirm accountability. This mirrors SR 11-7 change management for models, where material changes trigger revalidation, and it keeps agents inside the firm's existing model risk framework rather than beside it.

Version control also answers the question audits ask after an incident: what changed, when, and who approved it. Because each version carries its owner and approval state, the registry provides that answer directly. Microsoft's governance of agents across the organization, described in its Cloud Adoption Framework guidance, emphasizes that agents are software systems accessing data and taking actions across business systems, so knowing which version acted at which moment is a prerequisite for accountability.

Rollback depends on version integrity. A rollback path is only as reliable as the version history behind it: if configurations were not captured, the last approved version cannot be restored. Retaining full configuration per version, model, tools, permissions, controls, makes rollback a procedure rather than an archaeology project, which matters when reporting or trade support workflows need rapid restoration.

Finally, version control should drive the review cadence. Versions that changed risk-relevant properties trigger review promptly; all versions are re-examined at the quarterly cycle. This keeps the registry synchronized with the live estate, so the record an auditor sees is the system that actually ran.

Frequently asked questions

What changes to a registered agent should create a new version in the registry?

Material changes should create a new version: model version upgrades, new or removed tool grants, expanded permission scopes, owner changes, and modifications to controls such as rate limits or approval requirements. Cosmetic edits can update in place. Defining materiality narrowly ensures every risk-relevant change is reviewed and enforceable. This mirrors SR 11-7 change management, where material model changes trigger revalidation, and keeps agent changes inside the firm's existing model risk framework rather than alongside the registry.

How does version control support accountability for agent actions?

Version control supports accountability by recording which configuration of an agent existed at any moment, with the owner and approval state attached to each version. When an incident occurs in a research, reporting, or trade support workflow, the registry answers what changed, when, and who approved it directly from the record. Microsoft's Cloud Adoption Framework guidance emphasizes that agents access data and act across business systems, so knowing which version acted is a prerequisite for attributing responsibility.

What is the relationship between version control and rollback?

Rollback depends on version integrity: restoring a prior state requires that its full configuration, models, tools, permissions, and controls, was captured when it was approved. Registry version control retains that configuration per version, so rollback becomes a procedure executed from the record rather than an archaeology project during an incident. In asset management, where client reporting and trade support workflows have limited downtime tolerance, complete version history is what makes rapid, provable recovery possible.

How should version control interact with the review cycle?

Versions that change risk-relevant properties should trigger prompt review, while every version is re-examined at the quarterly registry cycle. Approval of a new version should route through the same reviewers who governed the original registration, confirming that changed scope remains justified and that new model versions carry validation. This linkage keeps the registry synchronized with the live estate, so the record auditors and EU AI Act reviews see reflects the system that actually ran in production.

Sources

  1. - federalreserve.gov
  2. - federalreserve.gov
  3. - artificialintelligenceact.eu