How it works
- Declare the gate. Requirements are data, not prose: which evidence must exist, from which sources, before a claim may proceed.
- The agent does its work and makes its claim. Tests added, citation found, task complete. Claims are cheap; agents are stochastic.
- Evidence decides. The gate resolves each requirement against observed data. Proven claims proceed. Unproven claims are blocked, fail-closed, with the evidence preserved for audit.
Where it runs
- Agent task verification: completion claims are checked against gates before the workflow advances.
- CI/CD quality gates: releases hold until tests, coverage, and approvals are proven, not asserted.
- Approval workflows: human sign-off is evidence like any other, and missing sign-off holds the gate.
Keep going
Start with Basics to trace a claim from assertion to accepted record. Applications shows where that same boundary belongs in real workflows. The Docs contain the complete reference.