Memory you can audit.
Watcher is a local-first AI librarian with cryptographic provenance. Point it at your documents, transcripts, and code, and it builds a wiki where every paragraph traces back to its source through a verifiable hash chain. It is built by 3030 Labs LLC.
We started from a single frustration. The systems that put a model between a person and their own documents ask for trust at exactly the moment they should be offering proof. We wanted the opposite default: a tool that hands you the receipt instead of asking you to believe the answer. Everything else followed from holding that line.
Three rules we do not bend.
Memory belongs to the user
The daemon runs on your machine. The wiki is markdown on disk and the facts are a store you can grep. Your key is injected at spawn time and never persisted. Nothing leaves your machine unless you say so.
Every mutation is reversible, inspectable, and signed
Each operation appends a signed record rather than overwriting state in place. The history of the wiki is a checkable artifact. You can see what changed, when, and that nothing in the sequence was rewritten after the fact.
Grounded or silent
A claim that cannot point to its source does not belong in the wiki. Every paragraph cites the chain it came from, and the system never returns a fact without a source attached.
What is shipped, and what is coming.
The daemon and the verifier
The local daemon compiles a cited wiki and exposes 17 MCP tools to agents. wotw-verify is a separate, cosign-signed binary that checks a Pack on a clean machine with no daemon running.
Hosted provenance dashboard
An always-on hosted daemon with a web dashboard for the people who want managed infrastructure without giving up the audit trail. Self-hosting stays free and AGPL, forever.
Shared workspaces and compliance packs
Roles, connectors, and retention policies for teams. Immutable audit and signed Compliance Packs for the environments that have to prove what they kept and what they redacted.
Talk to the people who built it.
Questions about provenance, hosting, or a compliance deployment? The fastest way to reach us is email. The code, the issues, and the changelog live on GitHub.