Skip to main content
Geval is built for audit trails: decisions record which contract, policies, and signals were used.

​
Contract

  • name — Stable identifier for the gate (e.g. ai-release-quality-gate).
  • version — Bump when you add/remove policy paths or materially change what “passing this gate” means.

​
Policy

Each policy file may carry its own name and version. Bump the policy version when rules change. Decision artifacts record per-policy identity and hash when available.

​
Signals

Optional top-level name and version on the signals JSON identify the evidence set. Bump version when your pipeline output shape or semantics change. Example: 
{
  "name": "ci-signals",
  "version": "1.2.0",
  "signals": [
    { "metric": "accuracy", "value": 0.94 }
  ]
}

​
Decision artifacts

Each geval check can write a JSON artifact under .geval/decisions/ including contract hashes, policy hashes, and signals hash — see Decision artifacts.

​
Next

Contract and policies · troubleshooting