evals.intentsolutions.io / gate-result / v1

gate-result/v1NORMATIVE

Predicate URI: https://evals.intentsolutions.io/gate-result/v1

What this predicate asserts

One deterministic or behavioral gate's outcome for one subject: the gate's identity and version, a four-state decision (pass / fail / advisory / error), the reasons, the policy the gate ran under (hash-pinned), and the exact inputs it saw. This is the row every emitter in the platform produces and every verifier re-checks.

Where it is used

Emitted nightly by the j-rig skill roster, by the governed brain's eval suite, and by every platform repo's CI. Consumed by intent-rollout-gate for ship/no-ship decisions and re-verified row-by-row by the labs dashboard before rendering.

Machine-readable definition

The canonical JSON Schema (plus matching Zod and Pydantic validators) is version-pinned in the contracts kernel: schemas/v1/gate-result.schema.json. The kernel package is @intentsolutions/core on npm.

How to verify a statement carrying this predicate

Statements are in-toto v1 Statements, DSSE-signed keyless via sigstore against the public production Rekor transparency log. Given a bundle file and its sigstore bundle:

cosign verify-blob --new-bundle-format --bundle <file>.sigstore.json --certificate-identity <the emitting workflow's identity> --certificate-oidc-issuer https://token.actions.githubusercontent.com <file>

Live, verifiable examples: the results browser re-verifies every row before rendering and links each bundle's evidence.