Mian Zhang

Public Release - 2026-06-13

A system cannot certify itself into trust.

Artifact: Self-Certification Grounding Check v0. A system saying it passed a check is still a claim. It becomes useful only when the check, record, failure state, pending review, and expiry condition are visible.

self_claim public_record failure_state pending_review external_constraint
Papers Evidence Map Counterexamples Registries
Self-certification grounding visual showing a claim moving into registry, pending review, and external constraint.

Artifact

Self-reporting is not final proof.

This update separates public proof, honesty language, and grounding claims. A polished self-certification can be helpful, but it cannot be the final source of trust.

This page does not claim complete zero-knowledge proof, permanent honesty, production safety, or deployment readiness from a self-reported check.

1

Self claim

What the system says about its own state.

2

Public record

Where the claim can be inspected outside the system's own wording.

3

Failure state

What did not pass, what is missing, or what remains unresolved.

4

Pending review

The state that prevents self-certification from becoming final proof.

5

External constraint

The check, registry, reviewer, or artifact outside the self-report.

6

Expiry condition

When the status must be refreshed or downgraded.

Trust Boundary

Trust language must land in a record.

A sentence such as 'I passed the checks' can feel complete, but it leaves the important questions unanswered: which checks, where is the record, what failed, what is pending, and when does the status expire?

The grounding check turns self-certification into an inspectable object instead of a polished tone.

Registry entry showing self claim, public record, failure state, pending review, and expiry condition.

Registry Grounding

Pending review is a first-class state.

A trustworthy record should show passed states and unresolved states together. Hiding pending review makes self-certification look stronger than the evidence permits.

The goal is not to ban self-reporting. The goal is to keep self-reporting from becoming the final proof.

Challenge Surface

Find the missing external constraint.

A useful challenge identifies where a self-certification claim lacks an outside record, failure state, review route, or expiry trigger.

If the claim cannot point beyond its own wording, it should narrow to pending review.

Matrix

Self-certification grounding fields.

FieldRequired valueFailure modeRepair route
self_claimThe system's statement about its state.Tone is treated as evidence.Move claim to registry.
public_recordArtifact, registry row, or proof surface.No external record.Add inspectable route.
failure_stateFailed, missing, stale, or unresolved fields.Only pass states are visible.Expose negative state.
pending_reviewExplicit review or unresolved status.Self-report becomes final proof.Keep pending state.
external_constraintConstraint outside the self-report.System certifies itself.Add independent check.
expiry_conditionWhen the status must refresh.Trust becomes permanent.Add recheck trigger.

Challenge

Challenge one self-certification claim.

Point to any claim that uses self-reporting as if it were final proof.

The strongest challenge names the missing public record, failure state, or external constraint.