Mian Zhang

Public Release - 2026-06-07

Without schema, paper evidence drifts.

Artifact: Upload Matrix Registry Validator v0. If the 16-paper upload matrix has no registry schema, PDF, manifest, supplement, claim boundary, hash, and DOI/status records slowly drift across versions.

paper_id claim_id evidence_id boundary_id hash_status
Registries Schema Notes Evidence Map Challenge Route
Schema validator visual showing PDF, manifest, hash, metadata, schema, and timestamp entering a validation gateway.

Validator

The matrix needs records that can fail.

The current public record is tied to W0, P23, P28, P29, P30, P31, P32-P40, and F1/P8. A validator does not make those papers stronger. It makes the public upload matrix less ambiguous by checking whether each public row has the identifiers, routes, boundaries, freshness fields, and failure status needed for review.

Today defines a public validation shape for paper, claim, evidence, counterexample, boundary, freshness, DOI/status, and hash records. It validates public registries and upload-package fields only. It does not read private logs, customer data, account state, or internal execution systems.

1

Required fields

paper_id, file_id, claim_id, evidence_id, boundary_id, public_route, hash_status, doi_status, and last_verified.

2

Failure modes

orphan paper_id, missing public_route, broken evidence link, hash mismatch, missing boundary, stale status, or ambiguous claim.

3

Validator report

Each row should say pass, fail, warn, needs_human_review, and the exact public field that caused the result.

4

Boundary check

The validator checks public fields; it does not demand private runtime, customer logs, account state, or internal execution traces.

5

Attack route

Challenge a registry field if it causes ambiguity between paper, evidence, boundary, DOI/hash, freshness, or claim status.

6

Repair action

A valid failure should produce a public repair: add a route, downgrade a claim, mark stale, update a boundary, or request evidence.

Schema

Minimum validation fields.

RecordRequired fieldsFailure conditionBoundary
paperpaper_id, title, group, public_file, status.Missing public PDF, manifest, or stable identifier.No anonymous submission identity.
claimclaim_id, paper_id, text, scope, evidence_tier.Claim has no paper link, no scope, or unsupported wording.No hidden deployment or performance claim.
evidenceevidence_id, public_route, artifact_type, hash_status, reproduction_route.Broken link, missing route, stale hash, or unclassified artifact.No private path or raw log.
boundaryboundary_id, does_not_claim, downgrade_trigger, withdraw_condition.Claim lacks a negative boundary or repair condition.No marketing expansion.
counterexamplepaper_id, target_claim, evidence_gap, attack_class, status.Attack route lacks a target or boundary effect.Public materials only.
freshnesslast_verified, doi_status, hash_status, route_health, stale_reason.Status is pending, stale, replaced, or unverifiable without notice.No reviewer-only or private account status.
Mechanical schema diagram linking paper_id and claim_id to PDF, manifest, hash, and boundary records across time.

Drift Prevention

Identifiers hold versions together.

The validator is not a trust badge. It is a way to stop version drift: a PDF changes but the manifest does not, a claim boundary moves but the claim_id stays vague, a hash is replaced but freshness is not updated, or a DOI/status field becomes ambiguous.

A passing row should mean only this: the public registry has enough structure for a reader, reviewer, or tool to trace the public claim to public evidence and a public attack route.

Validator Report

The output should be inspectable.

StatusMeaningExample repairPublic note
passRequired public fields exist and route health is current.No action.Still not proof of the claim.
warnField exists but status is pending, stale, or needs human review.Add freshness note or review date.Do not hide uncertainty.
failRequired public route, boundary, identifier, hash, or claim link is missing.Add route, downgrade claim, or mark not yet public.Failure is repair work.
needs_human_reviewThe schema cannot decide whether wording overclaims or leaks authority.Route to boundary review.Prefer downgrade over ambiguity.

Challenge

Attack one registry field.

The useful critique for this artifact is small and sharp: name a registry field that makes a paper, evidence object, boundary, DOI/hash status, freshness state, or attack route ambiguous.

Do not ask for private material. The validator must stay public-first: schemas, manifests, registries, demos, boundaries, issue routes, and negative results.

Boundary filter visual sending public registry and upload package fields through validation while private logs and customer data stay isolated.

Public / Private Boundary

Validate public records, not private systems.

This validator must not become a back door into protected material. It excludes private runtime, customer data, account state, private execution logs, internal prompts, private orchestration, commercial schedulers, financial execution details, alpha hints, and trading advice.