01Evidence
Files and records.
Reports, forms, exports, logs, emails, PDFs, CSVs, screenshots or other evidence objects.
Regulated evidence / receipt / verifier
Prove the evidence before it is questioned.
ActProof creates independently verifiable receipts for evidence bundles used in regulated workflows.
The evidence stays with the organisation. The receipt lets a later auditor, reviewer, counterparty or regulator verify that the disclosed package matches what was sealed earlier.
ActProof is intentionally narrow. It does not decide whether the evidence is true, sufficient or legally correct. It proves that a specific evidence package existed in a specific form and can be checked later without relying only on the producer's internal archive.
Balanced scope
ActProof is not a compliance platform, not a legal opinion engine and not a generic document vault. It is a small evidence infrastructure tool for cases where a later reviewer needs proof that a disclosed package is the same package that was sealed earlier.
If the package includes source context - a form, policy, standard, legal article, checklist, control, contract clause or source document - that context is sealed with the evidence. Source-binding is a by-product of complete evidence, not a separate product promise.
01 / Why
Regulated evidence is often questioned after the moment has passed.
Files move between systems. Reports are regenerated. Screenshots lose context. Emails are archived. Internal timestamps may not be enough for someone outside the system that produced the evidence.
ActProof gives the evidence package a verifiable receipt before the later question appears.
| Later question | Weak answer | ActProof answer |
|---|---|---|
| Is this the same package? | Trust the archive export | Recompute the package hash and verify it against the receipt |
| Were the files changed? | Rely on filenames and metadata | Check every file against the manifest |
| When did this package exist? | Use internal system timestamps | Check the signed statement and receipt time |
| What context was included? | Reconstruct notes later | Inspect the sealed manifest and included context |
02 / What gets sealed
Evidence first. Context when needed.
An ActProof bundle is the object that later gets verified. It can contain files, a manifest, metadata, a signed statement, receipt metadata and optional context explaining why the evidence was created.
02Manifest
Package structure.
Canonical list of files, roles, hashes, ordering and metadata needed to recompute the package.
03Receipt
Proof layer.
Signed statement, package commitment, receipt metadata and verification result.
04Context
Included if useful.
Form, rule, policy, standard, legal article, checklist, control or contract clause sealed with the package.
03 / Boundary
Strong proof, narrow claim.
The page should earn trust by saying exactly what ActProof verifies and what remains outside scope.
ActProof can show
- the disclosed package matches the sealed commitment
- the files still match the manifest
- the signed statement verifies
- the receipt matches the recorded commitment
- the included context was part of the sealed package
ActProof does not show
- that the underlying evidence is factually true
- that the organisation is compliant
- that the legal interpretation is correct
- that a regulator, auditor or court will accept it
- that source material has not changed since
04 / Where it fits
Useful when evidence must stand outside the system that produced it.
ActProof is useful when evidence may later be challenged, reviewed or relied on by someone outside the producer's own systems.
AuditEvidence
Audit evidence packages.
A reviewer checks whether the disclosed evidence matches the package sealed earlier.
RegulatorySubmission
Submission support.
A team keeps verifiable proof of the package behind a reporting or notification event.
AdvisorWork-product
Professional records.
An advisor, lawyer or consultant preserves the exact materials relied on for later review.
AISystem output
Machine-produced evidence.
An AI or workflow system seals the inputs, output and context behind an action or recommendation.
The goal is not to build another compliance platform.
The goal is to make regulated evidence easier to prove.