Core concepts
A bundle is a container that holds materials or work items (e.g., models, files) you want to govern as a group, and allow the application of policies to that material. To govern anything, it must be in a Bundle.

Anatomy of a Policy
-
Stages represent the phases you expect work to go through (e.g., Use Case Definition, Data Selection, Deployment, Ongoing Monitoring).
- Stages contain evidence. Your policy defines what evidence is required in each stage. Evidence can be collected as a variety of input types, including static responses, attachments, or calculated/computed results.
- Approvals specify who must sign off on the provided evidence before a stage will be considered completed. It can also control transitions between stages. If a reviewer identifies an issue, they can create a finding to document and track it.
- Gates let you enforce that certain actions (e.g., deploying a model or an App) cannot be performed until certain Approvals are completed.
Next steps
- Work with bundles: connect assets to policies and start the governance workflow
- Define policies: create and configure policies (for Governance administrators)
- Roles and security: understand permissions and role assignment for Governance
- Audit Trail: review a log of user and system actions across the platform