FAQ

What are the advantages of using this over git for an AI brain?

Git is designed for code merging. Demarkus is designed for knowledge.

Git solves branch/merge problems you don't have with documentation. For a knowledge base, those features create friction — demarkus eliminates it:

No merge conflicts — Every write creates a new immutable version (v1 → v2 → v3). No branching, no divergent histories, no reconciliation. With git, two people documenting the same thing means a merge conflict. With demarkus, it just works.
Content-addressed discovery — Instead of "where is the context for X?", you fetch by content hash — across multiple servers, without central git coordination. Federation handles the rest.
Graph-based context — The persistent graph enables backlinks: "show me everything that references this topic." Pure git gives you git grep and hope. Demarkus builds a queryable, navigable graph.
Distributed by default — Git assumes one repo everyone pulls from. Demarkus assumes many servers that discover each other via content hashes. Your docs, someone else's docs — all connected.

The AI-brain problem

The challenge is making expert knowledge — grouped by domain, by discipline, by whatever makes sense — available to everyone. Not locked in one repo, not scattered across wikis.

Demarkus solves this with structure and links:

Living documents per knowledge group — each expert domain gets its own evolving docs, linked to related context. Find them via backlinks and graph traversal, not file paths that move.
Backlinks answer real questions — what else references this domain? what decisions were made here? what changed last time?
Fetch by content hash — ask "show me everything about X" without knowing where it lives
Federation across servers — someone on another team documents a domain you depend on, and you discover it automatically through the graph

Git can't do this. It's one repo, text search, and merge conflicts. Demarkus is a connected graph of knowledge that grows as people write.