The Evidence Packet is a reproducible record tying a forensic verdict to the exact object received at intake — designed so an opposing expert can verify it independently, without trusting Plica. This page describes the design. It is being built, not yet shipped end-to-end, and we are honest about exactly where each piece stands.
When a regulator or an opposing expert questions a decision months later, an approval log is not enough. The serious question is: what object did the system rely on, and can you reproduce it independently? Most workflows have an approval trail. Almost none have a true evidence trail for the object itself. The Evidence Packet is designed to be that trail.
We mark every component honestly — shipped, partial, or design. This is the same status language we share with the forensic experts reviewing the approach. No overstated certainty.
Illustrative structure — not a live export. Fields marked partial or design match the build status above.
An opposing expert should be able to verify intake bytes and detector witness today. Seal, transform chain, and timestamp are on the roadmap.
Stating the boundary up front is what makes the rest credible. A forensic expert probes the limits first — so we name them.
We'd rather show you the design and its gaps than demo something that falls apart under scrutiny. The Evidence Packet is being pressure-tested with working forensic examiners before it ships — because a sealed record you can't independently verify is worse than none.
If evidence-grade reproducibility is on your roadmap and you want to shape it — or stress-test it — early access is open. You'll see exactly what works today and what is still design.
Early access · honest status · forensic-reviewer input welcome
Request early access →