Proof runs

The terminal blocks on /verify/ are run every day and compared with what proof-claims.json says they should print. The expected output lives in that file, not in the page — so a badge on /verify/ cannot say “verified” about a run that disagreed with it.

Skipped is not passed and is not failed. A rate limit or a DNS failure is not a disagreement about what the surface does; it is recorded with its reason and leaves the previous badge alone.

• Proof run 2026-09-23

  10 verified, 0 stale, 0 skipped

  website commit

  5bc2f692b837

  app server

  CodeRifts API Governance 1.0.3

  app commit

  not recorded — the app exposes no commit on any public surface — /health and MCP initialize both return a version string and no SHA. surface_source_ref_commit is the coderifts/api-governance commit that pins the published tools[], not the server build.

  surface commit

  d68d5c9d87d3

  runner

  darwin-x64, node v24.12.0, Python 3.9.6

What a proof run does and does not prove is in every artifact’s own does_not_prove block. The wider honesty table is What each proof proves.