Skip to content
Reloqui Docs

Governance: policies & approvals

Governance is how you turn release truth into a publish decision you can enforce.

Release policy

Section titled “Release policy”

Per project, define a release policy (Delivery → Policies):

  • Minimum confidence — the floor a release must clear.
  • Require approval and required approvals (N-of-M).
  • Orphan / heuristic gates — block if orphans exist or heuristic reliance is too high.
  • Approval confidence floor — the score below which an approved release auto-suspends.
PUT /api/v1/policies/releases
{ "projectId": "proj_…", "name": "Production gate", "minConfidence": 0.7,
  "requireApproval": true, "requiredApprovals": 1, "approvalConfidenceFloor": 0.7 }

When a reconcile fails a gate, the release lands in blocked_by_policy with the failing gate reported on the Release 360.

Policy DSL (preview)

Section titled “Policy DSL (preview)”

The preview API can compile a human-readable expression into policy fields:

POST /api/preview/v1/policies/compile
{ "expression": "confidence >= 0.8 AND orphans == 0 AND approval == required" }

Approvals

Section titled “Approvals”
  1. On a ready/ready_with_exceptions release, Request approval with a note.
  2. It appears in the Approvals inbox (GET /api/v1/approvals?projectId=…).
  3. Reviewers approve or reject with a comment. Self-approval is blocked — the requester can’t approve their own release.
  4. Once the N-of-M quorum is met, the release becomes approved and can publish.

Every decision is recorded with actor, timestamp and comment — a full sign-off history.

G3 — automatic approval suspension

Section titled “G3 — automatic approval suspension”

Reloqui protects against silent drift: if new evidence (e.g. a force-push) collapses the confidence of an already-approved release below the approval floor, it auto-transitions to approval_suspended. It can’t publish until re-reviewed. This is one of the platform’s strongest guardrails.

Freeze windows

Section titled “Freeze windows”

Create a freeze window (Policies → Freeze windows) to block publishing during a period (e.g. Black Friday). An approved sign-off can serve as a waiver during the freeze.

POST /api/v1/freeze-windows
{ "projectId": "proj_…", "name": "Holiday freeze",
  "startsAt": "2026-11-20T00:00:00+00:00", "endsAt": "2026-12-01T00:00:00+00:00" }

Governance-admin role

Section titled “Governance-admin role”

The governance_admin role owns policies, freezes and approvals without needing full project-admin rights — useful for a release-governance function separate from service ownership.

Scorecards

Section titled “Scorecards”

Each service carries a live hygiene scorecard (six weighted checks: repo linked, product set, relationships, a published release, confidence ≥ 0.7, lifecycle) on its Service 360.

Compliance evidence pack

Section titled “Compliance evidence pack”

Publishing freezes a snapshot; the export package (GET /api/v1/export/releases/{id}) bundles approvals, gate results, evidence and notes for auditors.

Section titled “Related”