Use casesEvidence for the questions your systems will be asked.
What did the agent do, and in what order? Which notice did a person get before talking to an AI? Start from the need. Each page explains where the question comes from, how Trustvice 360 records the answer, and exactly what that record can and cannot show.
Two needs, one kind of evidence
Every solution ends in the same kind of artefact: a signed, tamper-evident record that someone other than you can check against Trustvice's published keys. What changes is the fact being recorded.
Who usually asks.
The same receipt answers different people. These groupings are a starting point, not a rule: most needs touch more than one team.
Engineering
You build the agent, the pipeline or the integration, and you will be the one asked to show what it did. You want evidence that is produced by the code path itself, with no extra system to run.
Security
You need to notice when an agent acts outside the rules you declared, and to show afterwards what it did and when.
Compliance and legal
You need records that hold up when someone else checks them: a regulator, an auditor, a customer’s counsel. You also need to know precisely where that evidence stops.
Where the record matters most.
Three categories where Trustvice's artifact is the difference between an explainable AI deployment and one that breaks down under regulatory or customer scrutiny.
Customer support
Agents handling user queries in regulated industries. Witness records every reply; Council records user-rule evaluation.
Hiring & AEDT
Automated employment decision tools under NYC Local Law 144 and EU AI Act high-risk classification. Per-decision record, dissent log, audit-firm read-only access.
Multi-agent SDR fleet
Sales fleets where intake → enrich → route → book agents hand off to each other. v2.spot's Ensemble, Quorum, and Chronicle produce the cross-agent record.
What every receipt gives you.
Whatever the need, a signed receipt has the same four properties. They are narrow on purpose.
Integrity
Change one character of any field and the Ed25519 signature stops verifying.
Time
The receipt existed no later than its issuedAt. It is an upper bound on when the fact was recorded, never a lower one.
Origin
It was signed by a Trustvice key published at https://trustvice.com/.well-known/receipt-keys.json, so a verifier needs no relationship with you or with us.
Content binding
Receipts carry hashes. Anyone holding the original bytes can recompute the hash and match it; the hash does not reveal the content.
What no receipt does
- It does not make a reported fact true. Where you supply the facts, the signature makes your statement tamper-evident, not correct.
- It does not show that nothing is missing. A missing receipt is invisible unless something else says it should exist.
- It does not make anyone compliant with a law, and it is not a notarisation or a qualified timestamp.
Not sure which need is yours?
Tell us what you have to prove and to whom. We will say plainly whether Trustvice fits, and when it does not.
Every suite is part of Trustvice 360.
Every workspace can reach every suite; plans differ by capacity. Read the docs, or talk to us about what you need to prove.
