Back to Waclaude docs

Governance

Approval gates, rollout policies, and rollback automation

Codify how fixes move to production and how Waclaude responds if something goes wrong. Policies keep humans in control while letting the platform handle the heavy lifting.

Reviewer routing

Map directories or vulnerability classes to reviewers and approvers. Waclaude auto-assigns CODEOWNERS, security leads, and compliance approvers based on policy.

Change tickets

Sync PRs with Jira, ServiceNow, or Linear. Ticket status updates gate merges and record compliance evidence automatically.

Rollout & rollback

Attach rollout strategies (canary, feature flag, blue/green) and rollback hooks. Waclaude executes runbooks if health checks fail.

Sample policy fragment

approvals:
  default:
    reviewers:
      - team-security
      - platform-leads
    required: 2
  critical_systems:
    paths:
      - services/payments/**
      - services/auth/**
    reviewers:
      - ciso
    required: 3
change_tickets:
  provider: jira
  project_key: SEC
  auto_close_on_merge: true
rollout:
  strategy: canary
  percentage: 20
  rollback_hook: scripts/rollback.sh

See also