Roadmap.
The current library already has canonical exports, hashing, signing and local receipt work. The build should now converge on one concrete outcome: a regulated evidence package that can be verified later without relying only on the producer's archive.
Current base.
ActProof already has the pieces needed to support a regulated evidence receipt model: canonical JSON, hashes, signed statements, local receipt pilot and verification commands. These should now be assembled into a clearer evidence-bundle workflow.
Minimum useful client workflow.
The roadmap should prioritize fewer features and a stronger outcome.
| Milestone | Client value |
|---|---|
| Evidence package manifest | Every disclosed file has a role, digest and canonical package position. |
| Optional context manifest | The evidence package can include the form, policy, standard, legal article, checklist or control that explains why the evidence was created. |
| Signed evidence statement | The producer signs the package root and declared metadata. |
| Local append-only log | Statements receive inclusion receipts without sending event detail outside. |
| External root anchor | Batch commitments move outside later unilateral control. |
| Audit bundle export | Producer hands the reviewer one package. |
| Offline verifier | Reviewer verifies without producer server access. |
| SCITT adapter | Future alignment with external transparency-service registration when clients accept it. |
Do not build the wrong product.
Do not lead with a generic hash tool, full compliance platform, public document vault, or full SCITT server clone. The first product should be smaller and more valuable: independently verifiable evidence bundles for regulated workflows.
Roadmap sentence.
Build the bundle, then the anchor, then the SCITT adapter.