Skip to main content
reticle gate is what makes verification unavoidable. It computes the affected flows, looks for a passing artifact for each, and fails the command if any is missing. An agent that edits a covered file cannot call itself finished without re-verifying.

Arguments and flags

What blocks and what does not

What it prints

One reticle_gate line. Real capture from this repository, with the flow lists trimmed for length:
downgraded and deletedCoverage appear only when they are non-empty.

Exit codes

Measured on this repository, npx @reticlehq/server gate --since HEAD~1 exited 1 with the output above.

Worked example

Wiring this into CI

Where the gate sits relative to build, verify, and merge.
Last modified on August 15, 2026