Skip to content
Docs
ChangelogPricingOpen console

Guides

Evidence pages

An evidence page is an unlisted link to one run's evidence that anyone holding it can open, with no account. Send it to a customer, a manager or a risk team instead of a screenshot.

On a hosted workspace, open the run and find Share an evidence page below it. Only an Owner or an Admin sees it. Choose when the link expires (7, 30, 90 or 365 days, or never) and press Make a link. The link looks like https://oloproof.com/e/ followed by 43 characters. Copy it then: it is shown once, and Oloproof keeps only a digest of it, so nobody can show it to you again.

The same panel lists the run's open links. Revoke ends one at once: the next request for it answers "not found", exactly as a link that never existed. A run can have up to 20 open links. A link also closes by itself when whoever made it leaves the workspace, stops being an Owner or an Admin, or deletes their account; the panel then no longer lists it.

There is no command for this in the CLI. Making a public link is a disclosure, so it stays in the workbench, where the person making it is signed in.

The read-only example project cannot be shared.

What a visitor sees

  • Reported by the developer, at the top. The developer ran the evaluation and pushed it; Oloproof shows the results as the engine recorded them, did not run the system, and nobody outside the workspace has checked the numbers.
  • The release rules in words and in a table, each drawn as the interval it was decided on against its bar (Core concepts).
  • Each metric's estimate, interval, the cases it counted and how far the result reaches.
  • The judge check: each model judge's status, its recorded agreement with people and its bias, and the judge bars the gate applied (Judges).
  • The suite's declared role and, for a release holdout, how many system versions have been run on it.
  • What this cannot tell you (Limits), and a link to check your own scores.

Where a workspace decides the project's releases, the page says that it shows the run's own gate from the terminal, not the workspace's release decision.

What a visitor never sees

Case inputs and outputs, case ids, a judge's verdict or reason on any case, the workspace's or project's name, its members, other runs, comparisons or keys. The page does show the system's name and version and the suite's name, so choose those knowing they travel with the link.

Keeping it private

  • Whoever holds a link can forward it. Treat it as you would the numbers themselves.
  • The page is not indexed: it carries noindex, robots.txt disallows /e/, and it is never cached or sent on as a referrer.
  • Opening pages is rate limited per client. Oloproof counts links made and pages opened as one anonymous total per day, and records nothing about who opened a page.

What the label does not claim

The page is a report, not a seal. It does not say Oloproof checked the system, and it shows no badge. A run whose workspace signs its decision record (Gating) still reads "Reported by the developer" on its page for now. A signed label is built but stays off until the deployment publishes its workspace-statement key: when a link is made, Oloproof checks the run's signed statement once against the published keys, and the page could say the workspace signed it only if that check passed and the key has not been revoked since.

Where to go next