Skip to main content
Large organizations often attach more than one contract to a pull request — for example platform security, product quality, and infra SLOs — each maintained in its own repo.

​
Single signals file

geval check accepts one --signals path and multiple --contract paths: 
geval check \
  --contract platform/contract.yaml \
  --contract product/contract.yaml \
  --signals signals.json

​
Combining across contracts

Use --combine-contracts (default worst_case) to control how per-contract outcomes merge into the overall result. See check.

​
Operational tips

  • Keep each contract versioned independently.
  • Run geval validate-contract on each contract in CI before spending time on signal generation.

​
See also

How Geval works · Decision artifacts