Evidence / Reader Guide

Do not start with the strongest claim. Start with the evidence route.

This page helps external readers interpret the public evidence field without confusing daily notes, DOI records, GitHub, HF, and boundaries.

AI evidence map reproducible AI research AI claim verification DOI GitHub Hugging Face evidence counterexample route

Evidence Map Papers Registries Counterexamples

Search Intent

Readers want a practical way to inspect an AI research claim without reading every paper first.

How do I check an AI research claim?
What is the difference between DOI, GitHub, HF, and the main site?
How do I find the boundary of a claim?
Where should I submit a counterexample?

Route

A claim should lead to a record, not a vibe.

The public route is designed to move from claim to evidence, boundary, registry, and counterexample path.

Zenodo is the long-term archive. GitHub holds source, schemas, and issue routes. Hugging Face holds technical mirrors and datasets. The main site explains the public entry points.

Reading Order

Check status before strength.

Before asking whether a claim is impressive, ask what status it has: supported, narrowed, pending, failed, shadow-only, or boundary-only.

A strong public claim should survive that status check and still point to a public attack route.

Evidence Route

Where the claim can be checked.

This page is an entry point. The claim should be evaluated through DOI records, evidence maps, registries, GitHub/HF technical routes, and public counterexamples.

KindAnchorURLRole

Evidence MapPublic claim and evidence maphttps://mianzhang.org/evidence/Start from supported claims and known boundaries.

Paper IndexDOI and paper status maphttps://mianzhang.org/papers/Use paper-specific DOI records for paper claims.

RegistriesMachine-readable public registrieshttps://mianzhang.org/registries/Inspect claim, evidence, action, and counterexample records.

Challenge RouteCounterexample submission pathhttps://mianzhang.org/counterexamples/Attack overbroad claims through public routes.

ArchiveZenodo portfolio indexhttps://zenodo.org/records/20027295Long-term archive index; cite specific DOI records when available.

Boundary

What this page does not prove.

The evidence map does not turn every linked paper into a complete deployment claim.
The Zenodo portfolio index is not a substitute for paper-specific DOI records.
GitHub/HF mirrors are technical routes, not proof that a system is production-ready.

FAQ