# Counterexample Challenge Template

Use this template for public technical counterexamples, reproduction failures, and claim-boundary corrections.

Before submitting, read the public examples:
https://mmjbds-mianzhang-org.static.hf.space/counterexamples/examples.html

## Target

- Target page, paper, or claim:
- Claim ID, DOI, or URL:
- Current wording of the claim:

## Counterexample Type

Choose one:

- Over-broad claim
- Data leakage or provenance error
- Stronger baseline
- Reproduction failure
- Gap between evidence and action
- False no-go or overly conservative gate
- Credit contamination
- Other:

## Public Evidence

- Minimal public input:
- Public data or synthetic example:
- Reproduction command, if available:
- Expected result:
- Observed result:

## Why It Matters

Explain how this minimal counterexample weakens the claim, evidence tier, scope, or action boundary. Keep the report specific and isolate the smallest failure point.

## Suggested Repair

- Narrow the claim
- Add a missing baseline
- Add a missing receipt
- Add a missing falsifier, null arm, or stop rule
- Add a reproduction command or artifact-manifest row
- Correct a formula or variable definition
- Mark the result as negative
- Add a no-authority or no-credit test
- Other:

## Public Boundary

Reports should use only public, reviewable, non-sensitive material. Do not include credentials, customer data, protected logs, protected operational traces, harmful real-world action steps, or protected system details.