Mian Zhang

Public Release - 2026-05-31

From public pages to an evidence console.

Public entry points now exist. The next task is to turn them into controls: a place to inspect claims, evidence, counterexamples, boundaries, and daily engineering work.

claim evidence queue ledger
Open Registries Evidence Map Counterexamples Boundaries
Public evidence field map linking claims, evidence, counterexamples, boundary updates, revised claims, and ledgers.

Console

A public route is not enough.

The public evidence field now has a start page, an evidence map, a counterexample challenge, public boundaries, and a weekly memory layer. That is useful, but still too page-shaped.

Today turns the route into a console specification. A reader should be able to ask: where is the claim, what evidence supports it, what would break it, and what boundary changes if the attack works?

1

Claim Ledger

Each public claim should have a state, a scope, evidence links, attack routes, and downgrade conditions.

2

Evidence Registry

Each evidence object should say what it supports, what it does not prove, and where it can be inspected.

3

Counterexample Queue

Useful criticism should enter a queue with target claim, minimum case, observed gap, and boundary effect.

4

Boundary Update Ledger

Accepted attacks should narrow, split, raise evidence requirements, withdraw, or reject with a reproducible reason.

5

Daily Engineering Ledger

Daily public work should leave one named artifact, one boundary, one attack route, and one next action.

6

Private Boundary

The console inspects public claims. It does not expose private runtime, customer data, internal prompts, or commercial orchestration.

Route Map

Every entry point should map to a control surface.

Public routeConsole roleNext engineering actionLink
Start HereReader orientationMap each promise to a bounded claim.Open Evidence MapEvidence registryAttach support, limits, and inspection status.Open Counterexample ChallengeAttack queueRoute each useful attack to a claim and expected boundary effect.Open Public BoundariesBoundary ledgerMake claim narrowing, withdrawals, and evidence upgrades visible.Open Weekly EvidenceMemory layerSummarize what changed and which gaps remain open.Open Open SourcePublic artifact routeKeep schema, demos, manifests, and issue routes public-safe.Open Bounded BriefingPrivate inquiry routeRequire public boundary clarity before scoped private discussion.Open RegistriesMachine-readable indexAlign claim, evidence, counterexample, and action records.Open
Three-card evidence route for evidence shape, counterexample route, and claim boundaries.

Alignment

The console begins with registry alignment.

The next build step is not to add more slogans. It is to align canonical records: claim identifiers, evidence identifiers, counterexample classes, boundary states, and public routes. 

public route -> registry record -> evidence link -> attack route -> boundary state

If any public entry point cannot be mapped to a claim, evidence object, or challenge route, that is the useful bug.

Boundary

This is not the private system.

Evidence Console v0 is a public inspection interface. It is not a complete commercial system, and it does not disclose private runtimes, customer data, real execution strategies, internal prompts, production logs, or commercial schedulers.

The point is to make public claims inspectable without turning public accountability into exposure of protected execution systems.

Attack Prompt

The best 05-31 critique is a missing mapping.

Please point to any public entrance that still cannot find its corresponding claim, evidence object, counterexample route, or boundary state. That is the shortest path from public feedback to engineering work.