Skip to main content
You need the definition’s authoring and publication authority. Forge authoring is separate from Admin status. Most definition kinds also require Vantage.

​
Publish an inspected draft

  1. Open the definition and inspect its draft and dependencies.
  2. Check intended scope: Private, Workspace, Deployment or platform-managed System.
  3. Complete the required evaluation for the kind and visibility.
  4. Publish and retain the new version number.
  5. Inspect the version and a representative authorised consumer.
A draft save does not publish. A stale save is refused rather than replacing another revision. An unchanged publication is also refused. Publishing fixes content and dependencies. Display metadata can change separately, but material supplied to a model or approved output belongs to versioned content.

​
Adopt an upgrade in its consumer

Inspect changed schemas, tools, effects, runtime requirements and access before adoption. Recheck app instance parameters against the new workflow.

​
Publish and move a domain-schema pin

Author layers, types, relationship endpoints, attributes and units in the schema definition. Publish a permitted version. As workspace Owner, open the World Model schema controls. Inspect the current pin and select the new version. The workspace can use System, Deployment or its own Workspace schema. Confirm how Other entries and existing types resolve. Publishing a schema alone changes no workspace pin.

​
Narrow, revoke or restore

Narrow visibility when the definition should have a smaller audience. Existing holders keep their recorded pins, but current dependency checks can block later use. Revoke an unsafe published version through its version controls. Authored implementations retain exact bundle bytes and digest; missing or revoked pins block execution. A job following latest has no fixed pin. After revocation it selects the newest non-revoked bundle version. A watch destination behaves differently: a revoked newest destination stops delivery without fallback. To restore earlier behaviour, promote the earlier version into the draft, inspect it and publish a higher version. Earlier version numbers are never reused. Deletion is refused while retained work depends on a definition. Duplication creates an independent draft with its own files and provenance; it does not follow later source changes. Agent deployment-wide sharing and authored-tool deployment scope are refused under V2’s evaluation limits. See Configure a reusable agent definition.