Proof
Contributor Receipt

Show you read your own pull request.

A receipt is a signed record of the attention you gave your own change: which files you opened, how much of the diff you read in depth, and what you said about it in your own words. Free for contributors, always.

For contributors: get your receipt

If a repository asked you for a receipt, the check on your pull request already carries your link — click "Read your diff and sign the receipt" and it opens your PR, ready to read. Otherwise:

  • Open proof.toremlabs.com/projects?reviewPr=<PR>&repo=<owner/name> with your pull request number and repository.
  • Read your diff in the reading room. Approve or flag each file. What you skip is recorded as skipped — the receipt is honest in both directions.
  • Sign. The record seals with your name, and the check on your PR flips the moment it does.

We do not care what tools wrote the change. Nobody here detects AI or judges your code. The receipt shows one thing: a named human read this and stands behind it.

For maintainers: one line in CONTRIBUTING.md

A pull request now costs you the same attention whether the sender spent three hours on it or ninety seconds, and you cannot tell which from the outside. A receipt moves that cost back to the sender — and someone who clicks through without reading produces a check on their own pull request that says "0 of 12 files read", in the open where anyone triaging can see it. You never have to argue with anyone.

CONTRIBUTING.md paragraph
## Before you open a pull request

If this is your first contribution here, attach a **Proof receipt** with your
PR: a record showing you read your own diff before sending it. Aim for at least
80% read coverage.

We do not care what tools you used to write the change. We care that you have
read it and can explain it if we ask. A receipt is free, takes a couple of
minutes, and it is the fastest way to get a first-time PR looked at properly.

Get one at https://proof.toremlabs.com/receipt — free for contributors, always.
README badge
[![PRs come with a receipt](https://img.shields.io/badge/PRs-come_with_a_receipt-1f6feb)](https://proof.toremlabs.com/receipt)

Pair it with a sign-off policy scoped to external authors: your own team’s flow is untouched, and the proof/accountability check enforces the bar per pull request. A PR without a receipt is marked, so you can filter it out of your triage view — a check cannot reorder your list, and we do not claim it does.

What a receipt does not claim

  • Not that the code is good. It records attention, not correctness.
  • Not that a human wrote it. Attention, not authorship.
  • Not that it is un-gameable. Someone determined can open every file and read none of them. What it does is raise the cost of a pull request from zero back to minutes, and attach a name to the claim. The signed record itself is readable by the workspace it belongs to; the counts ride out in the open, on the check.

Proof does not detect AI or judge code. It proves a named human paid attention and signed.

Free means free

Reviewing and signing your own pull request costs nothing and requires no plan. Maintainers set policies on public repositories for free. Paid plans exist for private teams; the contributor flow is not where the bill is.