How do you know why version 27 was accepted?
Not what changed. Why it was trusted.
See the problemA normal pull request, on a normal Tuesday.
Alice tightens a safety threshold in CLAUDE.md. Reviewers approve, checks go green, she merges.
Update CLAUDE.md: tighten eval threshold for prompt safety checks
opened by Alice Chen
- Alice Chen approved1 reviewer • required
- CI passedci / build & test • 2m 41s
- Security scan passedcodeql • 0 findings
- Prompt eval: 0.94 (threshold: 0.90) — passedeval-harness v3.2.0
Fast-forward six months.
Nothing dramatic. Just the ordinary drift of a real system.
- Alice Chen left the companyoffboarded · Aug 2026
- The evaluation model has evolved (v3 → v4)eval-harness release
- A dependency now has a published CVECVE-2026-31840 · high
- The repository has continued to change312 commits since merge
drag the slider →
a3f9e21 — Update CLAUDE.md · merged by Alice Chen · Mar 14, 2026Git tells you what changed.
It doesn't tell you why it was trusted — or whether you still should.
- Which eval model scored this?✕ unknown
- Was 0.94 actually above threshold at the time?✕ unknown
- Who's accountable if this breaks in production?✕ unknown
What if the approval itself was the evidence?
Not a log you go find later. A signed receipt, emitted at the moment of decision.
CLAUDE.md eval threshold change approved
- Approver
- Alice Chened25519:9f4c…a17b
- Timestamp
- 2026-03-14T16:42:18Z
- Attestation hash
- 0x7d3a…f19c8b
- ci_rungh-actions/run/8821447301
- sec_scancodeql/scan/44e2a1
- eval_modeleval-harness v3
- threshold0.90
- eval_score0.94
Signed and notarized at the moment the decision was made.
Anchored on Geeq.
The receipt permanently preserves the conditions and reasoning behind the decision, so it can be verified — byte for byte — at any point in the future.
Six months later…
- · Alice has left the company.
- · The evaluation model has evolved.
- · A dependency now has a published CVE.
- · The repository has continued to change.
Despite all of that, the original approval can still be verified — because the evidence was captured when the decision was made.
- CI rungh-actions/run/8821447301
- Security scancodeql/scan/44e2a1
- Eval modeleval-harness v3
- Threshold0.90
- Eval score0.94
- Approver signatureed25519:9f4c…a17b
The SDK doesn't replace anything you use. It just remembers why.
Your existing tools run as normal
GitHub, CI, eval framework. No new pipeline.
A few lines of SDK emit a signed receipt
When a decision is made, the evidence is bundled and signed.
Anyone verifies it, later
A person, or another agent. No rebuild, no archaeology.
import { receipt } from "@geeq/receipt";
await receipt.attest({
decision: "merge-pr",
subject: "geeq/agent-policies#274",
evidence: { ci, security, eval },
approvedBy: user.id,
});Try it on your own CLAUDE.md.
Geeq IGNITE — bring your own repo, we'll show you the receipt.