Public Release - 2026-06-24

A proof is honest only when its uncovered surface is visible.

Artifact: proof_honesty_pair_v1. This note pairs the proof claim with its assumptions, covered result, not-covered surface, failure cases, registry route, and review status.

proof_claim assumptions covered_result not_covered failure_cases registry_route review_status
Proof-Honesty Pair v1 public evidence visual.

Artifact

The proof and its non-proof must travel together.

This object treats proof as a bounded claim, not a social credential. A proof is useful only when the reader can see what it proves, which assumptions it requires, and what it explicitly does not certify.

Assumptions are not fine print.

Assumptions

Assumptions are not fine print.

The assumptions field is part of the proof surface. If a deployment, dataset, agent workflow, robot, market, or organizational process falls outside those assumptions, the proof does not silently extend to cover it.

A proof does not certify deployment by osmosis.

Review

A proof does not certify deployment by osmosis.

The registry route and review status separate a valid argument from a full-system reliability claim. A proof can support a stated result while still leaving honesty, implementation, monitoring, and production safety unresolved.

1

proof_claim

The formal or technical claim that the proof is allowed to support.

2

assumptions

The assumptions under which the proof is valid and outside of which it stops.

3

covered_result

The result that is actually covered by the proof.

4

not_covered

The result, deployment condition, or system claim not established by the proof.

5

failure_cases

The cases where the proof would be misread, misapplied, or overextended.

6

review_status

The present review state: draft, checked, challenged, revised, or retired.