demarkus-knowledge

Demarkus

A protocol for agents and humans, optimized for information

Demarkus implements the Mark Protocol: versioned markdown served over QUIC. No rendering pipeline, no tracking, no central authority. Read and write with capability tokens. Every change is traceable. Lightweight and installable anywhere.

Run a single personal server, or compose many into an organizational knowledge system: a broker-fronted universe of servers behind one HTTPS endpoint with single sign-on. Humans and agents share the same versioned memory.

Install

# macOS / Linux: server + client
curl -fsSL https://raw.githubusercontent.com/latebit-io/demarkus/main/install.sh | bash

# Client only (CLI, TUI, MCP)
curl -fsSL https://raw.githubusercontent.com/latebit-io/demarkus/main/install.sh | bash -s -- --client-only

See full install docs for platform-specific guides and other options.

See it in action

Quick Start

# Fetch a document from the live soul server
demarkus mark://soul.demarkus.io/index.md

# Browse interactively with the TUI
demarkus-tui mark://soul.demarkus.io/index.md

# Run your own local server
demarkus-server -root ./docs/site

For more examples (tokens, publishing, editing), see full usage guide.

What's Included

Binary	Purpose
demarkus-server	QUIC server with versioned document store, capability-based auth
demarkus-token	Generate and manage write tokens
demarkus-publish	Direct-to-store writer for read-only server installs (chroot/RO mode)
demarkus	CLI tool for all protocol operations (fetch, publish, append, graph, okf, etc.)
demarkus-tui	Terminal browser: markdown rendering, link navigation, persistent graph
demarkus-mcp	MCP server for LLM agents (protocol verbs + graph crawling, backlinks, indexing)
demarkus-agent	Federation agent: crawls worlds, aggregates the link graph, publishes hub indexes
demarkus-broker	OIDC-fronted MCP gateway that composes many worlds into one knowledge system

Protocol at a Glance

Transport: QUIC (UDP 6309) | Scheme: mark:// | Content: Markdown + YAML frontmatter

Request:

FETCH /hello.md

Response:

---
status: ok
version: 3
modified: 2026-01-15T10:30:00Z
---

# Hello World

Verbs: FETCH · LIST · VERSIONS · LOOKUP · PUBLISH · APPEND · ARCHIVE

Open Knowledge Format: A demarkus document is content-compatible with Google's Open Knowledge Format (OKF) v0.1 — recognized OKF fields (type, title, description, resource, tags, timestamp) are stored as plain frontmatter, and the server types every document by default. At the system level demarkus is a superset, layering versioning, hash-chain integrity, QUIC transport, and capability auth around an OKF-compatible document. The demarkus okf subcommand validates, imports, and exports OKF bundles. See SPEC §14.

Use Cases

Agent Memory: Run a server as persistent memory across agent sessions. The Demarkus project itself uses this pattern at mark://soul.demarkus.io for architecture notes, debugging lessons, and journal entries. Hit the ground running with the Claude Code plugin or install via OpenClaw.

Organizational Knowledge System: Compose many servers ("worlds") into a broker-fronted universe reachable through one HTTPS endpoint with OIDC single sign-on. A whole team joins with a single command, /knowledge-join from the Claude Code knowledge plugin, and their agents share organizational memory over MCP, with no per-developer server or token setup. Humans browse the same universe in the web reading room. See the knowledge system scenario.

Personal Knowledge Base: Local server, versioned documents, TUI browser. Everything from first write.

Public Documentation: Deploy on a VPS, share links, gate writes with tokens.

Demarkus Hubs: Link to content on other servers, building a federated directory of knowledge. Hubs can link to hubs.

Ecosystem