Check the evidence
before you ship.
Ship-Check verifies evaluation files and requires a signed approval from the RunLog gate. Run it in your own GitHub workflow after your evaluator has measured the change.
Open setup guide on GitHub ↗ Create an API key
What you need
- A RunLog API key, stored in your repository's protected secrets.
- Your evaluated suite, workflow definition, measured report with a real tool-execution trace, and an evidence file binding those files and commits.
- A trusted issuer public key supplied independently of the pull request. Contact support if you need help obtaining and verifying the gate key.
- A reviewed Ship-Check action release pinned in your GitHub workflow.
The action guide documents exact inputs, evidence fields, and verification steps.
Understand the result
The action fails when evidence is invalid, hashes or commits do not match, the signature cannot be verified, the decision is too old, or the verdict is not approved. Configure your repository rules to require the check before merging.
The legacy recorded-trace mode checks caller-provided records only. It does not establish measured benchmark quality. Ship-Check does not automatically post pull-request comments.
After release
Add Loop-Guard around your runtime calls. Use what you learn to refine the next prompt and compare it in Benchmark.