Public proof explorer · retained evidence

Don’t trust the score.
Inspect the evidence.

Ten fixed product briefs, three canonical viewports, one source-bound artifact identity per case, and a verified semantic correction you can trace from preview to receipt.

Explore the corpus Open the evidence contract
10/10conformant cases
30responsive screenshots
10/10verified corrections
8/8passed gates
0critical issues

Case workspace

Follow one interface through the proof chain.

Select a case, change viewport, then inspect the qualitative review, exact hashes, browser evidence roles, and approved semantic correction.

Loading evidence

Proof case

Loading the retained proof contract.

Browser evidence Open original ↗
Screenshot SHA-256 —
01

Quality scorecard

pass

Every dimension must be at least 3/5, the mean must be at least 4/5, and any critical issue fails the case.

02

Verified semantic correction

receipt applied
Before—
After—

    Assurance boundary

    Successes alone are not a verifier.

    The corpus pairs eight product gates with six negative controls so failure behavior stays as inspectable as the healthy screenshots.

    Eight delivery gates8/8 passed
    Negative controls6 rejected safely

    What this unlocks

    The evidence layer is now a product surface.

    This static, hash-bound contract is the foundation for the next two experiences: direct static/React and breakpoint comparison, then human-approved IntentPatch previews against an isolated hosted compile.

    Next

    Target parity viewer

    Compare static and React at 390, 768, and 1440 pixels with shared anchor evidence.

    Then

    Semantic change preview

    Select a legal patch target, inspect exact before/after intent, approve, and re-prove.

    Later

    Isolated agent workspace

    Compile, verify, repair, and export inside a bounded hosted execution session.

    Run your first proof Inspect the source scorecard