geval check

Synopsis

geval check --contract <path> [--contract <path> ...] --signals <path> [options]

Required

--contract / -c — Contract YAML. Repeat for multiple contracts in one run (e.g. multiple teams’ gates on one PR).
--signals / -s — Signals JSON file shared across those contracts.

Option	Description
`--signals` / `-s`	Path to signals JSON.
`--contract` / `-c`	Contract path; repeat for each contract.
`--combine-contracts`	How to merge outcomes across contracts (`worst_case` default).
`--env` / `-e`	Optional environment label (e.g. `prod`); forwarded where reports use it.
`--json`	Print structured JSON to stdout instead of a human report.

Single contract

./geval check --contract .geval/contract.yaml --signals .geval/signals.json

Multiple contracts

./geval check \
  -c team-a/contract.yaml \
  -c team-b/contract.yaml \
  --signals signals.json

JSON for automation

./geval check -c contract.yaml --signals signals.json --json

Non-zero process exit from Geval on parse/load errors follows normal shell conventions (see Exit codes).

Successful runs write a decision artifact under .geval/decisions/ — see Decision artifacts.