ActProof wraps regulated evidence into a verifiable bundle.
A future auditor, reviewer or counterparty should not have to rely only on internal timestamps, screenshots, filenames or archived emails. ActProof turns the package into something that can be checked locally.
This is narrower than compliance management. ActProof proves package integrity, receipt continuity and included context. It does not decide legal correctness, factual truth, sufficiency or regulatory acceptance.
What gets wrapped.
The product object is not the hash alone. It is the complete evidence bundle that an organisation can disclose later.
| Bundle part | Purpose |
|---|---|
| Evidence files | PDFs, emails, logs, CSVs, screenshots, forms, reports and exports disclosed for review. |
| Evidence manifest | Canonical list of files, roles, hashes, package ordering and included metadata. |
| Optional source context | The form, policy, standard, legal article, checklist, control or contract clause included by the producer. |
| Signed statement | The producer's statement over the package commitment. |
| Receipt metadata | Proof that the statement or commitment was registered, timestamped or included under a signed root. |
| Verification report | Machine-readable and human-readable result explaining what passed and what is outside scope. |
Source-binding is a consequence of sealing complete evidence.
ActProof does not need to sell source-binding as a separate feature. If the evidence package includes the source context that explains why the evidence was created, that context is sealed with the rest of the package.
The verifier can later see that the context was included. ActProof does not monitor the source, interpret it, or claim that it remains current.
Strong proof, narrow claim.
ActProof should earn trust by saying exactly what is verified and what is not.
- the disclosed package matches the committed package root
- the disclosed files match the manifest
- the signed statement verifies under the issuer key
- the receipt matches the recorded commitment
- the included context was part of the sealed package
- whether the underlying facts are true
- whether the organisation was compliant
- whether the evidence is sufficient
- whether other relevant evidence was omitted
- whether an authority accepted the submission
What complete evidence can include.
An evidence bundle can include the files, the manifest, producer metadata, source context, supporting documents and the signed statement that describes what was sealed.
If source context is included, it is preserved as part of the evidence record. ActProof does not treat that context as a separate product feature. It is simply part of the package that was sealed.
Evidence should be easy to prove without becoming easy to overclaim.
The evidence stays with the organisation. The proof can be checked later.