🟢 #181 feat: content hashes on document versions + tamper-evident project export manifest +180 19d ago by
b1rdmania ↗ analysis ↗ GitHub ## Summary
b1rdmania/mike
A safety-first take on Mike from @b1rdmania, focused on making first-run setup safe and document exports tamper-evident.
This is Mike as @b1rdmania would like newcomers to meet it: carefully, with the guardrails in view. The work here isn't a redesign of the product - it's about the experience around it. The recurring thread is a first-run that steers people toward disposable, throwaway setups before they wire up anything real, and a cleaner separation between the settings that are safe to share and the ones that must stay secret.
Alongside the onboarding work, @b1rdmania has proposed a contributor guide that spells out safe local testing and how contributors should handle data - the kind of ground rules a legal-AI codebase benefits from having written down. There's also a more substantive idea in the mix: recording a per-version fingerprint of stored documents so that once a file leaves Mike, you can tell an untouched export from an altered one.
The direction is coherent - lower the barrier to getting started safely, and close a provenance gap that matters when the documents in question are legal ones. What's here is largely proposals rather than landed change, so treat this as an early, safety-minded reading of where Mike could tighten up. Click through to GitHub if you want the specifics.
What's in it
- Safer first run Reworked onboarding that surfaces safe local-testing guidance up front, steering newcomers toward disposable setups before they connect anything real.
- Public vs. secret settings A cleaner split between configuration that's safe to share and the values that must stay private, to reduce misconfiguration during setup.
- Contributor ground rules A lightweight contributor guide covering local setup, the checks to run before proposing work, and how to handle data in a legal-AI codebase.
- Tamper-evident exports A proposal to record a per-version fingerprint of stored documents, so an untouched export can be told apart from an altered one after it leaves Mike.
Direction
securitycompliance
Activity
## Summary
## Summary
## Summary
## Summary
📝 Document safe local setup and split public vs secret env vars 0 commits — minor change
📝 Add a contributor guide with safe-testing and data-handling rules 0 commits — minor change
📝 b1rdmania wants Mike's exports to prove they weren't tampered with 0 commits — securitycompliance draft
An open proposal to fingerprint every document version so a firm can prove the file it holds is the one the system actually reviewed.
📝 Surface safe local testing guidance and split frontend env vars 0 commits — minor change
📝 Add a contributor guide for the Mike fork 0 commits — minor change
Threads of work (detailed view)
b1rdmania wants Mike's exports to prove they weren't tampered with
An open proposal to fingerprint every document version so a firm can prove the file it holds is the one the system actually reviewed.
Pull requests (detailed view)
🟢 Open (2)
by
b1rdmania · opened 1mo ago by
b1rdmania · opened 2mo ago ⛔ Closed without merge (3)
by
b1rdmania · opened 2mo ago · closed 22d ago by
b1rdmania · opened 2mo ago · closed 2mo ago by
b1rdmania · opened 2mo ago · closed 2mo ago