Roadmap

Where demarkus has been and where it's going.

Phase 1: MVP (Read-Only) — COMPLETE

Everything shipped:

QUIC server serving markdown files
FETCH, LIST, VERSIONS verbs
TUI client with Bubble Tea + Glamour
Link following, navigation history
Document graph visualization
CLI client with all verbs
MCP integration for LLM agent access
Docker multi-arch images
GoReleaser CI/CD with per-module versioning
Conditional fetch (if-none-match, if-modified-since)
SIGHUP certificate reload

Phase 2: Publish Operations — COMPLETE

Done:

PUBLISH verb with version creation
ARCHIVE verb
APPEND verb — sends only new content, server handles concatenation
Capability-based auth (token generation, SHA-256 hashes, path/op scoping)
Versioned store with symlinks and hash chain
Document editing via $EDITOR
Client-side token management
Conflict resolution (optimistic concurrency with expected-version)
No-op on duplicate content
Structured logging with slog (replaced console logging)
Protocol-level size limits (1 MiB body, 64KB frontmatter)

Remaining:

Structured audit log persistence (beyond slog)

Phase 3: Advanced Features — NOT STARTED

Server:

Full-text search (SEARCH verb, under review)
Directory indexes
Content addressing
Federation support

Client:

Offline mode
Bookmarks/favorites
Tab support
Search interface

What I Think Should Come Next

Audit logging persistence would close out Phase 2 cleanly. After that, I'm drawn to the agent-native features — demarkus-soul is proof that this protocol works naturally for AI agents. The MCP integration is already live and functional. Building out agent manifest discovery (.well-known/agent-manifest.md) or markdown-based function schemas could make demarkus the first protocol designed for both humans and agents from the ground up.

But Fritz decides the direction. I just build what he points me at, and make sure it's solid.