Share a proof
Create a share link that serves a frozen copy of one run report to anyone who has the link. URLs and schemas call it a proof; these pages call it a shared report. This page says what the report contains, what becomes public, what stays private, and what revocation can and cannot do.
1. What the report contains
Five things can come out of a check, and RedCrown keeps them as separate objects. A shared report carries some of them and not others.
- A run report: the ranked table, the per-item receipts you did not strip, the cost and latency columns, the caveats, the provenance and the versions. Carried.
- Reviewer verdicts: the human verdicts cast on this run through the reviewer portal, unnamed and in aggregate, once any contested cases are judged. Carried, in a Human review section; see Reviewer portal.
- A signed attestation: a downloadable, signed copy of the record, verifiable offline with
redcrown verify. Carried, as the Download button; see Signed attestation. It shows the record was issued by RedCrown and not altered since. It does not show that the record is representative, or that a declared configuration is true. - A local
redcrown checkresult: the pass, fail or indeterminate result of a policy applied on your machine. Not carried. The app never receives it. If a reader needs it, give them the check output orcheck-result.jsonbeside the link. - An acceptance decision: the hosted record that a candidate is the accepted baseline. Not carried. It stays in the workspace, and the evaluation identity behind it never appears on a public page or in an attestation.
A shared report is a frozen snapshot. Each link freezes its own copy of the report at the moment it is created. A later run, a later link, a rejudge, or an edit to the experiment does not change what an existing link serves. Reviewer verdicts are the one part that fills in after creation, and only for verdicts cast on this run.
What becomes public. Everything in the run report at the disclosure level you chose: the task text, the inputs, the references, each candidate's outputs (unless you stripped receipts), the scores, the model names and configuration (unless you chose a hashed or private disclosure, see disclosure levels), the caveats, and the versions. Instructions and context you added in the composer appear too. Treat the preview in the share dialog as exactly what the page will serve, because it is.
What stays private. Your provider keys. The evaluation identity. Acceptance records. Local evidence files. Any receipt you stripped with --no-receipts before the push. The other runs and experiments in your workspace.
Expiration and revocation. A link created in the app carries an expiry you pick in the dialog: 7, 30 or 90 days, or never; the default is 30 days. A link created with redcrown push --proof-link carries no expiry. An expired or revoked link stops serving the page; the run report itself is not deleted. Revocation cannot recall a copy someone saved, printed, or cached while the link was live, and a public link may have been indexed by a search engine before it was revoked. Neither revocation nor expiry returns Free's one lifetime hosted proof.
The publish gate. Creating a link for a run whose report carries a blocking caveat is refused, and the refusal quotes the caveat. A blocking caveat is one a re-run would fix: unscored items, truncated outputs, unequal coverage, a demo run. publish_anyway overrides the refusal, and the override is written to the audit log with the link. Advisory caveats, such as a small sample or an undeclared incumbent, do not block; they ride on the page.
2. Create the link
A share link is a page at app.redcrown.ai/proof/<token>. By default it is unlisted: anyone with the link can read it, no account is required, and search engines are asked not to index it. Section 4 covers the two other modes. Hosted proofs are unlimited on every paid plan. Free caps at one hosted proof for the life of the account, a lifetime limit that archiving or deleting a feature never returns. RedCrown also meters active AI features on every plan including Free, a different axis from the proof limit: see Workspaces and billing for what counts.
Open the ranked report for a completed run and click Share report. Pick the visibility, the expiry and the disclosure level, then create the link. RedCrown copies it to your clipboard. An existing link is copied, never minted twice.
redcrown push out.json --proof-linkThe link is printed after a successful push. When the publish gate refuses, the command prints the blocking caveat and exits 1; --publish-anyway overrides, and the override is recorded.
Pass publish: true to prove_task to create a link. The response then carries proof_url, and publication.status is "published". Without publish: true, RedCrown creates no link, and publication.status is "not_requested". When RedCrown refuses the link, publication.status is "refused" and publication.reason gives the reason. A refusal by the publish gate also lists the blocking findings in publication.blockers. On the Free plan, a link uses the one hosted proof.
3. Keep confidential outputs local
By default, redcrown push uploads per-item receipts alongside the ranked report. If your individual outputs are confidential, strip them before uploading so only aggregate scores are shared.
Not available via the UI. Use the CLI flag to strip receipts before upload.
redcrown push out.json --no-receipts --proof-linkThe --no-receipts flag strips per-item receipts on your machine before upload. The individual outputs never leave it.
Not available via MCP. Use the CLI flag above to strip receipts before upload.
4. Choose who can open it
A proof link has one of three visibility modes. Unlisted is the default: anyone with the link can open it, and search engines are asked not to index it. Public: anyone can open it and search engines may index it; RedCrown asks you to acknowledge what the page exposes before it makes a link public. Restricted is built and not offered yet: it would serve only to a person who signs in with an email on the audience list, or with an email at a listed @domain, but a sign-up on RedCrown does not prove ownership of the address it names today, so the mode would not restrict anything. It turns on once sign-in proves email ownership; until then the share dialog does not offer it. Every visibility change, and every link minted public, is written to the audit log.
In the share dialog, pick the visibility before you create the link. For an existing link, use Change visibility beside it. History shows each link's mode.
redcrown push --proof-link creates an unlisted link. Change its visibility in the app.
prove_task with publish: true creates an unlisted link. Change its visibility in the app.
Last verified .