TECH Signal 471
ProofRun binds test results to a cryptographic fingerprint of the code state
ProofRun runs a command, binds its exit code to a hash of the current git state, and marks the result as stale if any byte changes.
AI coding agents often claim tests pass without actually running them against the latest code. ProofRun provides a local, offline receipt that proves a check ran against an exact code fingerprint, flipping to a stale status on any subsequent edit. This gives engineers a verifiable signal instead of trusting the agent's word.
Written by elseif from the cluster below · every claim links back to a sourceThe three things worth knowing
ProofRun runs a real subprocess and binds its exit code and duration to a fingerprint of the current git HEAD plus uncommitted changes.
Any code change after a run automatically flips the check status to STALE, requiring a re-run to confirm a pass.
The tool makes no LLM calls, operates fully offline, and compares command arguments as arrays rather than shell strings.
THE CLUSTER