Use cases

One substrate, every part of what you know. Namespaces keep it organized; every view (wiki, graph, git, files) reads the same store.

The professional practice

Cases, precedents, court rules and client facts — one place your assistant actually remembers the matter history across sessions and tools.

projects.law.cases · projects.law.library

The small business

Invoices, reconciliation notes, tax dates and vendor terms. Ask "what did Zeta pay in August" and get the memory, not a guess.

projects.accounting.invoices · projects.business

The builder

Project decisions, architecture notes, scraped reference libraries and error post-mortems — the context that makes your coding agent smarter every week.

projects.build.notes · projects.build.library

The personal life

Health, finance, goals, taste. Your assistant remembers the podcast you mentioned, the prescription schedule, the budget rule you set.

personal.health · personal.finance · taste.music

The researcher

Papers, quotes, sources and your own margin notes as a graph — recall by meaning, browse by connection, export when you publish.

research.papers · research.quotes

The household

Home automation preferences, maintenance schedules, warranty receipts and the manual you'll need in eight months.

home.automation · home.maintenance

How it looks in practice

// you, in any MCP-connected assistant:
"Remember: Meridian v Zeta hearing is Oct 14, dept 43."

// a month later, different assistant, different machine:
"when is the Meridian hearing?"
→ projects.law.cases: Meridian v Zeta — hearing Oct 14, dept 43  (score 7.8)

That's the whole product. Everything else — the wiki, the graph, the git history, the file attachments — is your same store, viewed.

Scraped libraries

Point the substrate at reference material (court rules, tax tables, docs) and it becomes a per-project library your assistant cites instead of hallucinating.

Start free — 14 days