Counterexample / Public Challenge

The best challenge names the claim, the missing evidence, and the boundary error.

This page turns criticism into a public repair route: not vague attack, but claim, evidence, counterexample, boundary, and requested correction.

challenge AI research claim AI counterexample reproducible AI research stronger baseline claim boundary

Evidence Map Papers Registries Counterexamples

Search Intent

Readers want to know how to challenge AI claims without guessing what evidence is missing.

How do I submit a counterexample?
What makes a challenge useful instead of vague?
How do I report a stronger baseline?
How should a claim be narrowed after a challenge?

Format

A useful challenge is specific.

Name the public claim, quote or link the relevant page, state the evidence gap, and identify the failure class: stronger baseline, reproduction failure, leakage, overbroad boundary, stale evidence, or authority leak.

The purpose is not to win an argument. The purpose is to make the public record narrower, stronger, or visibly unresolved.

Repair

A valid challenge should change the record.

If the challenge is valid, the page should update status, boundary, evidence route, or next review. If it is invalid, the rejection reason should still be explainable.

That is the difference between community criticism and evidence production.

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.

Do not request private credentials, customer data, private logs, or restricted submission material.
Do not treat harassment, private-system probing, or credential requests as public validation.
A counterexample should attack a public claim through public evidence routes.

FAQ