Policy Enforcement
Use drift monitoring, rules, and policy signals to keep repositories aligned with the team decision record.
DecisionOps gives you three related but different governance views: constraints, rules, and monitoring.
Constraints shape what a valid decision should account for. Rules define governance posture that can synchronize policy behavior across repositories. Monitoring shows what is happening now: alerts, coverage, and timeline activity. Drift data adds another signal by showing where actual behavior is moving away from the posture you expect.
Rules
Open /rules to manage validation and approval rules. This is where admins decide whether the organization is operating in advisory or blocking mode, which repositories are in scope, and what rule types should apply.
Monitoring
Open /monitoring to review alerts, repository coverage, and timeline activity. This page answers questions like which repositories are fully covered, which alerts need attention, and whether the current policy posture is creating problems that need follow-up.
Drift
Open /integrations/drift when you need to see whether drift telemetry is available and how strong those signals are. Drift views are especially helpful when teams want to understand whether policy conflicts and overrides are trending upward over time.