Work with governed Assets
Find an authorized Asset, verify its exact release, and use the action defined for its type.
Use this guide when you know the outcome you need and want to find, inspect, and use a governed Asset. If this is your first time in Organizational AI Memory, start with Your first governed journey for the end-to-end product model.
You must be signed in, have access to the relevant Asset, and have at least one usable release. No repository access or deployment setup is required.
Find an Asset
Open Assets in the product navigation. Search by the task or outcome, then narrow the results by Asset type or change the sort order.
The catalog is actor-specific: it returns the latest non-withdrawn exact release that the current identity may use. A missing item is not evidence that the Asset exists; the catalog does not disclose denied candidates.
Verify the exact release
Open a result and check the title, Asset type, summary, and availability. Use the Version selector when your workflow requires a specific release. Expand Version and provenance and verify:
- Coordinate identifies the Asset namespace and slug;
- Released identifies when this immutable release was published;
- Digest identifies the exact release content.
A newer release does not rewrite an older one or change an existing Capability Pack pin. Confirm the selected version again before an action that matters to your workflow.
Use the action for the Asset type
| Asset type | Primary action | Verify before completion |
|---|---|---|
| Prompt Template | Supply validated variables, prepare the prompt, and explicitly confirm any external model run. | Grounding uses only authorized Knowledge, and the receipt identifies the release digest and model route. |
| Work Instruction | Follow the ordered guidance and acknowledge the exact release. | Required checks, expected results, and escalation guidance are complete. |
| Capability Pack | Open the Pack, work through accessible pinned items, and record actor-scoped progress. | The outcome, prerequisites, item versions, and access-gap state are understood. |
| Skill | Inspect the package before installing it through the authenticated CLI. | Compatibility, manifest, file digests, and exact install command match your environment. |
External model calls and state-changing actions require explicit confirmation. Merely opening an Asset does not run a model, install a Skill, or complete a Pack item.
Handle an unavailable release
- If an Asset is absent from the catalog, check your search and filters, then ask an administrator or Asset owner to verify access without assuming the Asset exists.
- If the detail page has no usable release, ask the owner to complete the review and release process.
- If a release is Deprecated, prefer a current release unless a controlled workflow requires the older exact version.
- A Withdrawn release cannot start new consumption. Historical evidence and existing pins remain identifiable, but they do not make the release usable again.
- If access changes while you are working, refresh or use the available recheck action. A Capability Pack reports denied components as one opaque access gap without exposing their titles, types, or count.
Record the outcome
Use Yes or Report issue on the Asset detail page. Feedback is attached to the exact release you used and does not modify that immutable release. For a Capability Pack, mark an item complete only after performing its required work; progress belongs to your current actor.
Continue
- Understand the governed Asset lifecycle.
- Learn how authorization protects secure retrieval and GraphRAG.
Last updated on