Snapshots and sharing
Share a time-bound visual receipt without detaching it from the canonical Page.
Snapshots are shareable representations of a Page at a point in time. They should include the subject identity, Page type, Trust and Confidence values, verification state and the timestamp needed to understand freshness.
Safe sharing rules
- Link back to the canonical Page whenever possible.
- Never imply that a snapshot stays current after its creation timestamp.
- Preserve unavailable scores as unavailable.
- Do not let a presentation field overwrite a system fact.
The Console Share proof action should use the same Page record shown by View Page, so a share cannot drift from the source card.
Snapshot contents
A useful snapshot records:
- the canonical Page identifier and public URL;
- Page type, display identity and source;
- Trust and Confidence exactly as stored at creation time;
- score state and last-scored timestamp;
- verification state and method where public;
- snapshot creation time and immutable snapshot identifier.
The snapshot route is /snapshot/{id}. It is a historical receipt, not a live alias. The canonical Page remains the destination for current evidence.
Create and share
Open the owned Page
Use the Pages card or canonical public Page. Confirm the score state before creating a share.
Create the snapshot
The server resolves the Page and records the current authoritative facts. Client-submitted score values never override the stored score facts for an owned canonical Page.
Copy or publish the link
The shared surface names the creation time and links back to the current Page. The interface confirms when a link is copied or explains why creation failed.
Consumer guidance
When receiving a snapshot, first check its creation and score timestamps. Then open the canonical Page for current state before a high-impact action. A valid snapshot can support an audit trail even after the current score changes, but it should never be presented as continuously current.
Privacy and revocation
Only public Page facts belong in a public snapshot. Provider tokens, private email addresses, API-key identifiers, billing state and internal evidence payloads must not appear. If deletion or revocation is supported, retain the minimum audit metadata required by policy and return a clear unavailable state at the old URL.