Versioning and publishing
ACP treats important resources as versioned assets. Every resource starts with a first saved version, edits can be saved to the current version or a new version, and publishing selects the immutable version that production execution should use.
Save, publish, restore, and compare versions for agents, computers, web apps, functions, Metronomes, guardrails, and evaluations.
Version model
Versioning separates draft editing from production behavior. Saving captures a snapshot, publishing chooses the production snapshot, restoring copies a previous snapshot back into the editable resource, and comparing returns file-style diffs for review workflows.
Use version methods
Each versioned manager exposes the same method names. Product managers such as webApps and functions inherit the same server-resource versioning operations.
Versioned resource map
Use the resource-specific manager when one exists. Use server-resource managers for deployable resources such as web apps and functions.