Home/Platform/Outcome Receipts
The differentiator
The work has an outcome. The record explains how.
A log line tells you what a tool says. Seraph's operation record names the human who authorized the work, the privilege it borrowed, the job that ran, and the machine's own confirmation. Where recovery is supported, its declared path is recorded before execution.
Anatomy
Six answers, on one page, for every operation.
These are the six questions a client, an insurer, or an auditor actually asks. A receipt answers all six or it is not a receipt.
Why it can't be quietly rewritten
Edit one record and the ones after it stop agreeing.
Each receipt carries a fingerprint of the record before it. That is what turns a list of events into evidence: you cannot change history without every later record disagreeing with you.
The comparison that matters
A log line and a receipt are not the same artifact.
| The question your client asks | An RMM log line | A PAM access record | A Seraph receipt |
|---|---|---|---|
| Who told it to do this? | Not recorded | Yes — the request | Yes — the named authorization |
| What privilege did it use? | Standing agent rights | Yes | Leased, scoped, with its expiry |
| What exactly ran? | A summary the tool wrote | Out of scope | The signed job itself |
| Who says it worked? | The tool says so | Out of scope | The target machine answered |
| How do I undo it? | Figure it out | Out of scope | Declared before execution |
| Can it be edited afterwards? | Usually, by an admin | Usually, by an admin | Not without breaking the chain |
Read this as a difference in what the artifact is for, not a scoreboard. A PAM access record is excellent at the thing it was built for. It was simply never built to tell you whether the work succeeded.
What you do with it
The receipt is built to leave the building.
An audit trail nobody outside your team can read is an internal comfort. This one is designed to be forwarded.
The quarterly review
Walk into the QBR with the quarter's operations, each one verified and reversible, under your own branding. "Here is what ran on your environment, under what privilege, proven by your own machines."
Reporting & exports →The insurance questionnaire
The automation section of a cyber-insurance renewal asks what your automated tooling is allowed to do and how you would know if it did something else. Answer it with records instead of prose.
For MSPs →The incident question
When something goes wrong at 2am, the first question is "what changed?". One reference number resolves to the whole operation — command, privilege, job, confirmation, and the undo that is still available.
The operation loop →Does the AI write its own receipt?
Does the AI write the receipt?
No — and this is the whole point. The receipt is assembled by the platform from things that happened, not from the model's account of what it did. The confirmation row can only ever carry what the target machine answered to an independent check. If that check did not run, the row says so rather than going quiet.
What happens when an operation fails?
It still produces a receipt. A failed operation is a real outcome and it gets the same record: what was attempted, what privilege it held, where it stopped, what the machine reported, and whether the declared undo was executed. A receipt that only exists for successes would be advertising, not evidence.
Can we export them?
Yes — PDF for humans, JSON and CSV for systems, per operation or per client per period. Review the published package scope for your operating requirements. We do not charge per receipt, because a platform that meters proof teaches you to ration it.
How long are they kept?
For the life of the workspace, with retention configurable per client. Records live in your tenant's own isolated storage — see Roles & Multi-Tenancy for how the walls between clients are drawn.
Is a receipt the same as session recording?
No. A receipt is the record of an operation — the authorization, the privilege, the job, the confirmation, the undo. Governed remote sessions are a separate surface with their own recording story, and we are deliberately narrow about what that covers today: see Governed Sessions.
Pick a claim and make us show it
Everything on this page can be demonstrated in under a minute.
Bring the hardest question from your last client audit. We will run an operation and open the record it produces.