Skip to main content

Overview

Managed Policies are a different category of governance entity. Their validation logic is built into the Witboost Computational Governance itself — you don't write CUE, natural language, or host a remote service. Instead, you configure a small set of parameters through a guided wizard, and the platform evaluates the policy natively.

Managed Policies exist to cover governance patterns that depend on data or logic that only the platform itself owns (for example, the deployment status of a system across environments). A customer-authored CUE script or remote service has no reliable way to access this kind of information; a Managed Policy does, because it runs inside the Governance Platform.

Where to find Managed Policies​

When you click Create Policy from Governance > Registry, you now land on a Policy Type Selection screen before entering any creation flow. This screen presents a grid of cards:

  • One card per available Managed Policy type (e.g., "Environment Promotion").
  • One "Custom" card, which opens the policy creation flow described in Creating a Policy — unchanged from before.

Currently, one Managed Policy type is available:

More Managed Policy types will be added over time. Each type defines its own configuration wizard, its own restricted operations, and its own evaluation logic, but all of them share the concepts described on this page.

Restricted operations​

Each Managed Policy type declares which of the standard governance entity operations are not available for it. This is a property of the policy type, not a platform-wide rule — different Managed Policy types may restrict different operations, typically because versioning, cloning, or deprecation of that type's configuration only make sense if handled internally by the platform. Check the documentation page of the specific Managed Policy type you are using for its concrete restricted operations set.

Regardless of type, you can always Edit, Enable/Disable, and Delete a Managed Policy.