Knowledge Mgmt

Your LLM Wiki. Verified.

Karpathy's wiki pattern stores knowledge as markdown. VerifiedState makes it verified, searchable in 0.01ms, and queryable from any AI agent.

Get API Key →

The Problem

LLM Wiki is a great pattern — store everything you learn as markdown files, organized in folders. But it's local-only. Search is linear file scanning. Contradictions between pages go undetected. And no other tool or agent can access your knowledge. Your wiki is a silo.

Your wiki. Queryable from any AI tool.

• • • Wiki page edited

# python_asyncio.md (updated)

asyncio.run() is the main entry point...

✓ 2 assertions synced · rct_55cd

• • • Claude Code

> How do I use asyncio?

✦ From LLM Wiki, synced 1 min ago

asyncio.run() is the main entry point

Receipt: rct_55cd · source: llm_wiki

Edit a wiki page. Query it from your IDE.

The Fix

npm install @verifiedstate/llm-wiki

typescript
import { LLMWikiBridge } from '@verifiedstate/llm-wiki';

const bridge = new LLMWikiBridge({
  apiKey: 'vs_live_...',
  wikiPath: './my-wiki',
  namespaceId: 'my_knowledge',
});

await bridge.start();

// Your wiki pages are now:
// - Verified with cryptographic receipts
// - Searchable in 0.01ms (zero-hop filter)
// - Queryable from Claude Code, Cursor, Goose, any MCP client
// - Monitored for contradictions across pages

What You Get Back

✓ VERIFIED

receipt.json
{
  "receipt_id": "rct_7f3a...",
  "assertion": "User prefers dark mode",
  "status": "verified",
  "confidence": 0.94,
  "signature": "ed25519:a8c3f1...",
  "verified_at": "2026-04-06T14:32:01Z",
  "chain_position": 42
}

Without VerifiedState vs. With VerifiedState

Feature	Without	With VerifiedState
Contradictions	Manual — you notice or you don't	Automatic conflict detection across all pages
Search	Linear file scan, slows with scale	0.01ms zero-hop + seven-channel retrieval
Access	Local filesystem only	Any MCP client, any agent, any tool
Verification	None — it's a text file	Ed25519 signed receipt per fact
Scale	Breaks at 500+ files	Postgres-backed, scales indefinitely
History	Git blame	Bitemporal queries — "what did I believe in January?"

FAQ

Do I need to change my wiki structure?

No. Point the bridge at your wiki folder. It reads markdown files, extracts assertions, and syncs to VerifiedState. Your folder structure and files stay exactly as they are.

Does it work with Karpathy's exact LLM Wiki format?

Yes. Plain markdown files in folders. No special frontmatter required. Links between pages are preserved as assertion relationships.

Can I query my wiki from Claude Code or Cursor?

Yes. Once synced, your wiki is accessible through the VerifiedState MCP server. Add the MCP config to your IDE and your wiki knowledge is available in every coding session.

What happens when I update a wiki page?

The file watcher detects the change and re-syncs that page. New assertions are created (append-only). If the update contradicts an existing fact, the conflict is flagged automatically.

Your LLM Wiki. Verified.

The Problem

The Fix

What You Get Back

Without VerifiedState vs. With VerifiedState

FAQ

Related Integrations

Start building with verified memory.