Verified change receipt: a record of what was checked on a change, that anyone can verify later.

01Definition

The verdict, and the evidence behind it, in one record.

A verified change receipt is a small machine-readable record attached to a code change. It names the exact commits that were checked, each check that ran and what it found, the checks that did not run, the policy that turned those results into a verdict, and the verdict itself.

Signed, it becomes tamper-evident: anyone holding it can confirm that nobody altered it after the fact.

• Exact commits
• Checks run, and not run
• Policy and verdict

02Why it matters

Trust that travels with the change.

A green check in one CI system means little to anyone outside it, and nothing at all a month later. A receipt can be read by a maintainer deciding whether to merge, a security team auditing what shipped, or an insurer pricing the risk of AI-written code, without re-running anything or trusting the tool that produced it.

That only works if the format is open, so TraceAxiom plans to publish it, with an offline checker, as open source.

• Readable by anyone
• Checkable later and offline
• An open format

03In Verify

Written and tested; not signed end to end yet.

The rules for what a receipt may trust and publish are built. Signing is written and tested in code but is not yet live end to end: for public repositories it will use GitHub's artifact attestations, and private repositories get an unsigned receipt until TraceAxiom's own signer exists.

Verify is not installable yet.