Public Release - 2026-06-04

Each paper should register what it does not claim.

A dense upload matrix needs negative boundaries before louder claims. The Per-paper Boundary Update Ledger records how each accepted challenge should shrink, split, downgrade, withdraw, or request more public evidence.

does_not_claim downgrade_trigger withdraw_condition public_note

Public Boundaries Evidence Map Counterexamples Registries

Boundary ledger visual showing a paper matrix surrounded by does_not_claim boundary controls.

Upload Matrix

The ledger is a repair surface, not a defense wall.

The current public record is tied to a 16-paper upload matrix: W0, P23, P28, P29, P30, P31, P32-P40, and F1/P8. The point is not paper-count promotion. The point is to make each paper's claim, evidence, boundary, freshness status, and attack route inspectable.

Yesterday's queue described how to attack a paper claim. Today's ledger describes what happens after a useful attack is accepted. A valid public counterexample should leave a visible boundary change: narrower wording, a split claim, a lower evidence tier, a withdrawal condition, or a next evidence requirement.

old_boundary

The current claim envelope before a challenge is accepted.

trigger

The public counterexample, replay gap, stronger baseline, or authority leak that changes the claim.

delta

The evidence requirement that changed: proof, replay, manifest, checksum, DOI, or baseline support.

new_boundary

The narrower claim after the update, written in public language.

status

Accepted, downgraded, split, withdrawn, needs evidence, or rejected with public reasons.

public_note

The record a reader can cite without needing private runtime or submitter context.

Ledger Map

Boundary fields for the paper matrix.

Paper groupdoes_not_claimdowngrade triggerwithdraw condition

W0No universal metrology proof for all AI behavior.Public theorem or interoperability gap.Core definitions fail under stated assumptions.

P23No live self-modifying deployment claim.Dry-run replay cannot support the stated boundary.Public artifact no longer reproduces bounded replay.

P28 / P29No customer monitoring, sensitive group inference, or real-world drift authority.Heldout drift or minority relabel gap under public fixtures.Value-boundary or drift bridge collapses in public replay.

P30 / P31No complete ZK system or permanent honesty guarantee.Proof transcript, honesty bound, or verifier mismatch.Protocol claim cannot be supported by public transcript.

P32-P40No production handoff, legal authority, governance authority, or deployment proof.Measurement gate, succession gate, ethics gate, or authority leak.Public protocol implies authority it cannot warrant.

F1/P8No alpha, no trading advice, no account state, no executable strategy.No-trade refusal or no-alpha boundary is contradicted.Negative-result framing cannot be maintained.

Block diagram separating public claim updates from private submitter context and internal data flow.

Public / Private Filter

Update the public claim without exposing private context.

Boundary updates operate on public claims, public artifacts, public evidence deltas, and public notes. They do not publish a submitter's sensitive context, private material, internal validation logs, customer data, account state, credentials, private prompts, or execution chains.

If a challenge can only be evaluated by disclosing protected material, the public outcome is usually a boundary downgrade, a no-go note, or an evidence requirement, not a demand for private disclosure.

Template

Minimum fields for a boundary update.

FieldPurposePublic-safe ruleLedger effect

paper_idNames the paper or group.Use the public matrix identifier.Routes the update.

old_boundaryRecords the previous claim scope.Quote public wording only.Makes the change inspectable.

triggerNames the accepted counterexample or evidence gap.Use public artifacts or redacted-safe summaries.Explains why the claim changed.

evidence_deltaStates what public evidence is now required.No private runtime as the required proof.Creates the next work order.

new_boundaryWrites the narrower claim.No hidden expansion or marketing upgrade.Prevents overclaim.

public_noteCreates a citeable update record.Do not include sensitive submitter context.Lets readers audit the repair.

Challenge

Show when a claim should shrink, split, or be withdrawn.

The most useful critique is not the loudest objection. It is the smallest public-safe case that forces a visible boundary update for one paper claim.

The standard remains: public credibility, not public control authority.