Use cases / where the receipt earns its place

Use ActProof when a later verifier will not accept "trust our system".

The common pattern is simple: evidence is produced, a package is sealed, a receipt is kept, and a third party verifies later.

The first use case is audit evidence for regulated organisations. The broader applications are regulated submissions, advisor work-product, AI accountability, product-passport claims and supply-chain evidence. The claim stays narrow: the receipt verifies the package, not the whole legal or factual conclusion.

01 / Audit evidence

An organisation seals an evidence package. Months later, a reviewer checks it.

At the time of the event, the organisation packages the evidence, signs a statement and keeps a receipt. Later, the reviewer receives the evidence package and verification bundle. The reviewer recomputes the package root and verifies it without accessing the organisation's servers.

StepProducer actionReviewer result later
Evidence eventEvidence package created from reports, logs, forms and other records.Reviewer sees disclosed package and manifest.
ReceiptPackage root is signed and receipted.Reviewer verifies statement and receipt metadata.
ContextAny relevant form, rule, policy or checklist may be included in the package.Reviewer sees that context was sealed with the evidence.
VerificationProducer exports verification bundle.Verifier reports whether the disclosed package matches the prior commitment.
02 / Other fits

The same package-and-receipt pattern applies beyond audit evidence.

These are credible adjacent uses, but the product should not be diluted. Each use must still involve a later verifier and a meaningful evidence package.

AIAccountability

Action or answer evidence.

An AI or automated process seals the input, output and policy context behind an action record.

Supply chainAudit

Batch evidence.

A shipment, certificate, inspection report or logistics record must later be checked by a buyer, insurer or authority.

AdvisorRecord

Work-product evidence.

A professional preserves the exact package of documents, sources and notes relied on at the time.

03 / Not the target

ActProof is not a regulatory change-management tool.

If a package includes source context, that context is sealed with the evidence. That can be useful later. But the primary value is independent proof of the package, not monitoring whether the source changed after the package was sealed.

The evidence stays with the producer. The proof can be checked outside the producer's system.

That is the use case boundary.