Can we prove what happened?
A Trust Receipt is the artifact a CISO or privacy officer hands to an auditor: one governed AI decision, its inputs, its verdict, the reason, who reviewed it, and where it sits in the tamper-evident audit chain. No patient data is ever on a receipt — governance metadata only.
Recent receipts
Four synthetic decisions from one day at Lakeview. Verdicts are computed by the real eligibility evaluator over the synthetic model records.
What every receipt contains
Decision ID
Stable identifier, also the audit object id.
Purpose
Why the request was made, in the words of the workflow.
Data classification
PUBLIC · INTERNAL · PHI · REGULATED — declared, escalation-only.
Model requested → selected
What was asked for, and what actually ran (or nothing).
Governance verdict
ALLOW · REVIEW_REQUIRED · BLOCK, from the deterministic evaluator.
Reason code
Machine-readable and human-explained; the same code every time the same facts occur.
Human review
Not required, approved by a named role, or pending — never implied.
Evidence references
Model card, policy decision, approval record — each hashed.
Audit integrity
Position in the hash chain and whether the chain re-verifies.
Ready to see your own organization?
Everything above is synthetic. Signing in shows your organization's own assessment, risks, policies, recommendations, and Trust Receipts. Access follows a confidential discussion and a signed NDA.
Every record on this page is synthetic and belongs to a fictional hospital. Nothing here is a customer, a patient, or a production measurement. The scoring, eligibility, and audit logic are the real Nexus engines running over the synthetic inputs.