Introduction

Verdikt gates pull requests on evidence, not code diffs. When you label a PR verdikt:rc, Verdikt opens a certification window, collects signals from your eval stack, evaluates them against your thresholds, and returns a gate verdict your CI can enforce.

Quick start

Connect signals (start with API push). Most teams POST eval results after each run — see API push. Alternatives: integration pull (Braintrust, LangSmith, etc.) or CSV upload. Not sure which path? Read the signal sources overview first.
Define signals and thresholds in Settings → Signals & thresholds — mark required metrics before you wire CI.
Install the GitHub App and add the gate workflow so merge is blocked until Verdikt certifies.
Run a cert: label a PR verdikt:rc → post signals → poll gate → merge when action is merge.

Steps 1–2 are about what gets measured. Step 3 is enforcement. You can configure signals before GitHub is wired — both docs follow that order.

How it works

PR labeled verdikt:rc
  → Cert window opens (matched by commit SHA)
  → Signals arrive (pull, push, or CSV)
  → Verdikt evaluates thresholds
  → Gate: CERTIFIED / UNCERTIFIED / COLLECTING
  → Branch protection blocks or allows merge

Questions: hello@useverdikt.com

Getting started

Connecting signals

GitHub integration

Agent setup

Quick start

How it works

​Quick start

​How it works

Quick start

How it works