Action or answer evidence.
An AI or automated process seals the input, output and policy context behind an action record.
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.
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.
| Step | Producer action | Reviewer result later |
|---|---|---|
| Evidence event | Evidence package created from reports, logs, forms and other records. | Reviewer sees disclosed package and manifest. |
| Receipt | Package root is signed and receipted. | Reviewer verifies statement and receipt metadata. |
| Context | Any relevant form, rule, policy or checklist may be included in the package. | Reviewer sees that context was sealed with the evidence. |
| Verification | Producer exports verification bundle. | Verifier reports whether the disclosed package matches the prior commitment. |
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.
An AI or automated process seals the input, output and policy context behind an action record.
A product-passport field relies on a supplier declaration, certificate or test report that may later need proof.
A shipment, certificate, inspection report or logistics record must later be checked by a buyer, insurer or authority.
A professional preserves the exact package of documents, sources and notes relied on at the time.
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.
That is the use case boundary.