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.

Every write creates a new immutable version (v1, v2, v3). No branching, no divergent histories, no reconciliation needed. Two people documenting the same thing in git means a merge conflict. In demarkus, it just works.

Instead of "where is the context for X?", you can fetch by content hash across multiple servers without central coordination. Federation handles the rest.

The persistent graph enables backlinks — "show me everything that references this topic." Git gives you git grep and hope. Demarkus builds a navigable graph that agents traverse through MCP tools and humans browse in the TUI.

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 available to everyone. Grouped by domain, by discipline, by whatever makes sense. Not locked in one repo, not scattered across wikis.

Demarkus solves this with structure and links. Each expert domain gets its own evolving docs, linked to related context. You 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? You can fetch by content hash — ask "show me everything about X" without knowing where it lives. And federation means 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.