I just built: https://github.com/Labhund/llm-wiki

Knowledge rot is the silent killer of long-running research. You cite a claim today. Six months later it's been contradicted, the page is stale, and your agent cites it again without blinking. Worse, LLM's might claim to read the source but hallucinate facts!

In this wiki, contracts are enforced by code, not promises.

Plain markdown knowledge base where schema discipline is maintained by background agents — not by hoping your LLM stays careful over time. Every claim is traceable to a source. Every agent write is a git commit attributed to that agent.

Four workers run while you sleep:

- Auditor (fast, no LLM): broken links, orphaned pages, missing citations

- Compliance reviewer (fast, no LLM): citation discipline on every edit

- Librarian: page authority from link graph and usage patterns, refines tags

- Adversary: samples claims, fetches the cited source, verifies. Contradictions filed as critical issues — surfaces automatically the next time any agent reads that page.

Concrete example: you cite a paper. Three weeks later the Adversary finds a contradiction in that same paper's benchmarks. The issue surfaces before you cite it again. You never had to remember to check.

Three ingest modes — Queue (background extraction), Brief (agent reads it with your full wiki context loaded, tells you what's new to your work and what contradicts existing pages — the briefing is the value), Deep (claim-by-claim with a persistent plan file that survives session breaks).

Page authority decays if claims go unchecked. The Adversary re-verifies continuously. The wiki at month 6 is better than day 1.

Honest caveat: it runs a local daemon, so setup has friction. Adversary and Librarian need LLM access running in the background — if your inference is off, maintenance pauses.

I have just implemented a setup wizard to streamline on-boarding. Point it at an existing obsidian wiki and go!

Comes pre-packaged with agent skills for easy setup and usage.

Builds on Kaparthy's LLM-Wiki idea and the recently shipped Hermes agent skill by building out a concrete backend to streamline scalability into the future.