Reference

3 min read

Sharing a gate result

Every gate run has a shareable link. You can send it to stakeholders, drop it in Slack, or attach it to a PR review — no StateAnchor account required to view.

Creating a share link

Open the run detail view in your project cockpit (/project/{projectId}/runs/{runId}) and click Share. A share token is minted for the run and a Copy link button appears with the public URL:

https://stateanchor.dev/share/{token}

Click Copy link to copy the URL to your clipboard. You can also use the export buttons in the same toolbar to save a PDF of the verdict for archival.

What the share page shows

The public share page includes:

• Gate verdict — the lane badge (PASS / WARN / ERR) and the decision reason.
• Syndrome breakdown — per-syndrome findings for the parent, merge-base, LKG, and deployed diffs (see Gate Engine).
• Per-change classifications — every finding with its lane, endpoint, field, and plain-language evidence string (see Gate classification).
• Drift pressure — the DPI score and band at the moment of the run.
• Corpus citation — the 847-pair corpus attribution for the classification rules that produced the verdict.
• Merkle proof link — anchors the verdict to the public append-only log (RFC 6962 CT model).
• Run metadata — timestamp, commit SHA, and sync-run UUID.

The share page deliberately does not expose your spec, environment, secrets, or project settings. Only the classified findings and evidence for this specific run are public.

Permanence

Share links are permanent. They point to an immutable gate result captured at the moment the sync ran. Re-running the gate on a new commit creates a new run with a new share link — the old link continues to render the original verdict.

Gate decisions are also anchored in the public Merkle log (stateanchor-merkle-log), so the share page can be independently verified even if you lose access to your StateAnchor account.

No account required

The /share/{token}route is a public page — it does not sit behind Clerk auth. Anyone with the link can read the verdict. That makes share links a good substitute for screenshots in PR reviews and post-incident write-ups.

If you need to restrict access, do not share the link publicly — the token is effectively a bearer credential for that specific verdict. Revocation lands with the dashboard exception-audit work; today the only way to retire a link is to avoid distributing it.