Reference · Demos
Demos
Every demo says how real it is. LIVE runs against the service now. REPLAY shows real output recorded earlier. SIMULATED uses synthetic data that describes no real customer.
A receipt, issued now
LIVE One call to the public check endpoint, verified in your browser.
Loading when you press the button.
The transparency log head
LIVE SIMULATED The signed tree head the API publishes, fetched now and verified in your browser against the published key set. The first four leaves are fixed placeholders. After them come the hashes of receipts from recent checks by anyone, appended on a best-effort basis: each data center keeps its own list in its cache for up to six hours, the list stops growing at 64 leaves, and nothing is stored durably. Two fetches can show different heads, and a head does not show that any particular receipt, yours included, is in the log. No route returns an inclusion check for a receipt yet.
Loading when you press the button.
Recorded receipts
REPLAY Four real responses recorded from the live API, verified in your browser against the key set recorded with them.
| Request | Outcome | Rule | Verified here | Evidence grade |
|---|---|---|---|---|
| Verifying in your browser… | ||||
Evidence grade of these receipts
The live receipt and the recorded receipts above are all /v1/check decisions, and each carries this grade. The transparency log head is not a decision, so it has none.
- Covers
- Which rule decided this request and that the record was not changed after signing. Not whether the sender was an AI agent.
- Confidence
- None stated. No calibrated confidence applies to this record.
- Calibration
- Uncalibrated
- Known error rates
- None measured. Silvector publishes no detection error rate yet.
- Basis
- Deterministic decide() rule each rule shown above
- Ed25519 signature over the canonical receipt body, checked against the published JWKS
- Bias risks
- The decision is only as good as the facts it was given. A request with no signature claim is not_identified, which is not a finding that a person or an agent sent it.
- Next step
- To ask who was behind a series of requests, keep the receipts and escalate to rung 3 with at least two independent signal families. How escalation works
- Assigned by
- These docs, from the rung definitions. The grade is not a signed field of the receipt.
The console demo tenant
SIMULATED The console's demo tenant is seeded with synthetic data and labels each panel with its own reality level.
Not here yet
Screen recordings of the console flows are not published on this site yet. They will appear here, labeled REPLAY, with the date and build they were recorded from.