Skip to content

Reviewer Path (One Page)

This page is for first-time readers, journalists, program reviewers and external operators who need a fast honest picture of the public repository. It is not an endorsement, legal opinion or private application document.

The question ClaimBound answers

Where is the evidence?

A public claim becomes a small evidence card: frozen protocol, source boundary, exact result status, sanitized hashes, claim boundary and reproduction level. No card means the statement is still only a claim.

Five-minute inspection (no coding depth required)

  1. Read ClaimBound in 30 seconds.
  2. Skim three flagship cards in the README:
  3. green source audit (Anthropic or EEA),
  4. green gate with yellow reproduction chip (NASA POWER D-103),
  5. red honest negative (NOAA CO-OPS D-131).
  6. Run the portable baseline (Windows, macOS or Linux):
git clone https://github.com/ClaimBound/claimbound-evidence.git
cd claimbound-evidence
uv sync --extra dev
uv run claimbound doctor
uv run claimbound validate-all

Expected: ready=yes, valid_cards=48, exit code 0.

  1. Read Planned work not shipped — SourceProbe v1, static registry HTML views, PyPI and WCAG are not claimed as completed.

What is already strong

Signal Where to look
Honest mixed outcomes Green, red, amber blocked and yellow drift cards in registry
European open-data angle European Dimension and five EU-related examples
Cross-platform operator CLI doctor, inspect, rerun, drift, verify — platform support
Scope discipline Reviewer summary — not OSF, not OpenML, not certification
Artifact honesty Artifacts catalog — NYC TLC / CDC are artifact-only, not registry cards

The main credibility gap (stated openly)

All 48 registry cards currently use SINGLE_OPERATOR or SINGLE_OPERATOR_RERUN. There is no INDEPENDENT_RERUN or MULTI_OPERATOR card yet.

Maintainer bootstrap runs closed VERIFY mirrors #88–#92 for repository hygiene. Independent external closure of #85, #86 or #87 is the acceptance signal. See External verification packs: first setup ~15 min; each open issue closes with one claimbound verify … command (~2 min) after baseline. Minimum credible signal: #85 + one of #86/#87 from an operator who is not the maintainer.

What is planned but not shipped

See Public roadmap 2026 and Planned work not shipped. Acceptance-criteria documents are specifications until implementation lands on main.

Role Next page
Non-developer Start without coding
External operator External operator starter pack
Deeper comparison Reviewer summary
EU public-interest framing European Dimension
Common mistakes Common misreadings
End-to-end EU example EEA source audit case study