Skip to content
PROOF / CLAIMS MODEL

Verified is
not one thing.

LedgerLayer avoids the single green-checkmark trap. Every result exposes a claims vector so a reader can distinguish transcript integrity, deterministic replay, source admission, participant binding, competition binding, eligibility, authenticity, and publication state.

THE EVIDENCE CHAIN

Result is output.
Evidence is history.

The transcript receives its own stable digest. The verifier replays it. The result is derived separately. The receipt signs the identities and claims needed to interpret both.

MANIFEST→TRANSCRIPT→VERIFIER→RESULT→CLAIMS→RECEIPT
CLAIM DISCIPLINE

Never upgrade
weak evidence.

A historical visual replay can be useful without being equivalent to an authenticated competitive transcript. LedgerLayer preserves that distinction explicitly.

STRONG / AUTHORITATIVE

Replay confirmed.

Transcript, environment, source admission, participant and competition binding can all resolve against authoritative evidence.

WEAKER / HISTORICAL

Display only.

Visual reconstruction can remain valid as a historical artifact while source admission, participant binding, and rank eligibility remain unknown or false.

PUBLICATION

Existence ≠ consent.

Evidence can be private, owner-only, participant-scoped, embargoed, public, or revoked. Storage alone never implies publication.

PORTABILITY

Verify elsewhere.

The evidence bundle is designed so permitted recipients can verify without trusting the presentation layer that originally showed the result.

PUBLIC VERIFICATION

A leaderboard row
should be inspectable.

Explore the scripted homepage concept, then check an actual signed synthetic package. Inspect its named demonstration policy, coverage gaps and gameplay limitations.