Proof receipts

A signed record of the work.

A proof receipt is how Riley proves what it did: what was found, what you approved, what got done, and what was verified, with before and after evidence where capture is available.

found  ·  approved  ·  done  ·  verified

Verify a receipt

Receipts show what Riley recorded and signed. Before and after evidence appears where capture is available.

What a receipt records

Every line, start to finish

01

Found

Riley detected the issue or the work to do.

02

Approved

You approved anything that writes outside your workspace.

03

Done

Riley completed the action.

04

Verified

Riley checked the result, and where capture exists, kept the evidence.

Signing, in plain English

It cannot be quietly edited

Each receipt is signed and chained to the one before it. In plain terms: the receipt carries a cryptographic signature, and if a single character changes, the signature no longer matches. Because each receipt also references the one before it, you cannot slip an edited receipt into the middle without breaking the chain. That is what lets anyone holding the link check that a receipt is real and intact, without an account and without trusting our word for it.

Receipt types

The shapes proof can take

Each type is marked with its honest status. A type marked coming soon is not available yet, and we say so.

Weekly proof receipt

Live
  • ·Every action Riley completed this week, line by line
  • ·Which of those actions you approved before they went out
  • ·A signature and a public link anyone can use to verify it

Workflow run record

Live
  • ·Which workflow ran, when, and what it did
  • ·The approval that let it write anything external
  • ·The result Riley verified after the run

Client update

Coming soon
  • ·A client-ready summary built from recorded work, not memory
  • ·What changed since the last update and why it mattered
  • ·Links back to the underlying receipts

AI usage proof

Coming soon
  • ·Which AI surfaces asked Riley to do work
  • ·What each request produced and whether it was approved
  • ·A usage picture you can hand to a client or a manager

Website QA report

Coming soon
  • ·Pages checked and the problems found
  • ·Which issues became fix cards and what happened to them
  • ·Verification that fixed issues stayed fixed

Ecommerce growth report

Coming soon
  • ·Store checks Riley ran and what they found
  • ·Drafts and fixes you approved for the store
  • ·Recorded results, never projected ones

Implementation proof

Coming soon
  • ·What was set up, connected, and configured
  • ·Each step recorded as it completed
  • ·A handover record a client can verify

Support summary

Coming soon
  • ·Support threads summarized with outcomes
  • ·Escalations flagged and where they went
  • ·Reply drafts and who approved them

Lead rescue record

Coming soon
  • ·Leads that were going quiet and what Riley did about it
  • ·Follow-up drafts and the approvals behind them
  • ·Which leads came back

Security audit record

Coming soon
  • ·Permission scopes and access checks Riley reviewed
  • ·Findings and the fixes proposed
  • ·A record you can share with whoever owns security

Custom receipt

Custom setup
  • ·A receipt shaped around your own workflow
  • ·The fields and evidence you and the Riley team agree on
FAQ

Common questions

What is a proof receipt?

A proof receipt is a signed record of work Riley completed: what it found, what you approved, what it did, and what it verified, with before and after evidence where capture is available. Every line comes from the outcome ledger, which only holds actions Riley actually completed.

Can a receipt be edited after the fact?

No, not quietly. Each receipt is cryptographically signed and chained to the one before it, so any change breaks the signature and the chain. Anyone holding the link can check that the receipt is intact.

Do receipts guarantee an outcome?

No. A receipt is an honest record of work that completed, not a promise of a result. It shows what happened, and where evidence was captured, it links to it.

Prove the work. Keep the client.

Put your work on one loop and watch the first signed receipt land. Start free, no card to begin.