Mian Zhang

Public Release - 2026-05-30

A weekly map for public evidence.

This week did not just add three notes. It made the evidence field easier to enter: evidence needs shape, counterexamples need reproduction, and valid counterexamples need boundary updates.

claim evidence counter ledger
Weekly Evidence Counterexample Challenge Evidence Map Public Boundaries
Weekly evidence digest map linking claims, evidence, counterexamples, boundaries, and ledger records.

Digest

Not more noise. A clearer operating surface.

A public evidence field should not ask readers to chase a scattered feed. It should leave a weekly trail: what was claimed, which evidence objects were added, which counterexamples are useful, and which boundaries changed.

The weekly digest is therefore a memory layer. It does not replace original artifacts. It helps readers find the claim, inspect the evidence, aim a bounded counterexample, and see how the boundary should update.

This Week

Three notes became one evidence route.

DatePublic noteWhat it addedRoute
2026-05-27Evidence Has a ShapeEvidence should be an inspectable object, not only narrative support.Open 2026-05-28Counterexample ChallengeUseful attacks need exact claims, minimum failing cases, observed behavior, and missing receipts.Open 2026-05-29Claim BoundariesValid counterexamples should narrow, split, raise evidence, withdraw, or be rejected with reason.Open 2026-05-30Weekly Evidence DigestThe weekly memory layer for claims, evidence, counterexamples, and boundaries.Open
Three-card evidence route for 05-27 evidence shape, 05-28 counterexample route, and 05-29 claim boundaries.
Public evidence field map from claim to evidence, counterexample, boundary update, revised claim, and ledger.

Lifecycle

The weekly chain is now explicit.

Claim -> Evidence -> Counterexample -> Boundary Update -> Revised Claim -> Ledger

This is the public discipline we want for high-risk AI claims. A claim should point to evidence. Evidence should admit counterexamples. Valid counterexamples should change the claim boundary. The change should remain visible.

1

Over-broad claim

Find a public statement that says more than the public evidence can support.

2

Missing evidence

Name the missing artifact, replay path, receipt, baseline, seed, or provenance object.

3

Stronger baseline

Show a simpler or standard baseline that beats the result under the same protocol.

4

Broken replay

Identify the exact command, dependency, data pointer, or assumption that prevents reproduction.

5

Boundary update

State how the claim should narrow, split, raise evidence requirements, or withdraw.

6

Public record

Leave the change in a ledger so the next reader can see what happened.

Next Week

The best feedback is a bounded attack.

Next week attack queue: over-broad claim, missing evidence, stronger baseline, broken replay, and boundary update.
QuestionUseful answerNot usefulWhere to aim
Which claim is too broad?Point to the exact public claim."The whole project is wrong."Claim table
Which evidence is missing?Name the absent receipt, replay, baseline, or artifact.General doubt.Evidence map
Which replay breaks?Give the smallest failing command, case, or dependency.Screenshot-only critique.Counterexamples
Which boundary should change?Suggest the narrower claim or evidence requirement.Demanding private logs.Boundaries

Boundary

Open claims, not private systems.

The weekly digest invites attacks on public claims. It is not a request for exploit instructions, private runtime logs, customer data, real execution records, or private orchestration details.

A mature public route protects private systems while still making public claims inspectable, reproducible, and correctable.

Weekly boundary ledger with date, claim, evidence route, counterexample route, boundary status, and next attack.

Ledger

The weekly record should stay readable.

The point is not to make the archive bigger. The point is to keep the evidence memory navigable: dates, claims, evidence routes, counterexample routes, boundary status, and next attacks.

Chinese Entry

The Chinese route now has a weekly memory layer.

Chinese entry map from official account to evidence field, attack route, private route, and weekly evidence summary.
RouteUseBoundaryLink
Weekly EvidenceNew reader weekly memory layer.Summary, not replacement for artifacts.Open Counterexample ChallengeSubmit bounded attacks on public claims.No private logs or customer data.Open Evidence MapInspect public evidence surfaces.Public artifacts only.Open Public BoundariesRead what is and is not claimed.Boundary discipline.Open