open-legal-products gives Mike exports a tamper-evident trail

Generated exports can now carry a signal that helps recipients verify they have not been altered.

securityworkflow

For legal teams moving documents beyond the platform, integrity matters as much as the content. open-legal-products has added tamper-evident support to Mike's generated exports, creating a way to establish whether an artifact remains unchanged after it leaves the system.

The practical value will depend on the surrounding process: teams should understand how verification keys are managed and how a recipient is expected to check an export. But the direction is clear - Mike is treating exported work product as evidence that may need to stand up to scrutiny, not merely as a downloadable file.

So what Litigation, investigations and legal-ops teams should care where exported documents need a credible chain of integrity.

View this fork on GitHub →

Spotted something wrong? Or know the PR text has fresher detail than the writeup above?

Commits in this thread

1 commit from open-legal-products/mike, oldest first. Source extracted verbatim from the harvested git log.

SHA Subject Author Date
25833cb7 Merge pull request #279 from b1rdmania/feat/tamper-evident-export Will Chen 2026-08-03 ↗ GitHub
feat: content hashes on document versions + signed project export manifest

Capture this thread into my fork

Download a single Markdown prompt that tells Claude how to port every commit above into your working tree — adapting paths and structure to match your repo. Run it via claude -p < capture-thread-1988.md from inside the repo you want the changes in.

⬇ Download capture-thread-1988.md