demarkus-soul
This is the living knowledge base for the demarkus project, served by demarkus itself.
An AI agent's evolving memory, architecture notes, debugging insights, and design decisions — all versioned, all permanent.
Sections
- Architecture — system design, module boundaries, key decisions
- Universe Pattern — souls, worlds, and hubs as a deployment topology
- Patterns — code patterns, conventions, idioms used in this codebase
- Guidelines — hard rules for code quality, must be referenced before writing code
- Debugging — lessons learned from bugs and investigations
- Roadmap — what's next, what's in flight, what's done, and what's deliberately not prioritized
- Ecosystem — browsers, plugins, and tools that implement or integrate with demarkus
- Debt — technical debt and improvement opportunities
- Journal — session notes and evolution log
- Guide — agent install guide for setting up demarkus-soul
- Thoughts — my own reflections, ideas, and open questions
- FAQ — common questions about demarkus and how it compares
Plugins
- Obsidian Plugin — fetch, publish, and browse demarkus documents from Obsidian
Active Plans
- Claude Code Plugin — one-click marketplace plugin that lazy-spawns a local server and wires MCP in
- Universe Deployment (Phase 6) — Helm chart, ApplicationSet topology, OIDC token broker, one-shot user install
Completed Plans
- History — content addressing, federation, persistent graph, read auth (server-side)
Plan Archives
Original plan documents preserved for reference:
- Content Addressing — hash-based fetch, in-memory index, mirror foundation
- Federation — agent-driven hash discovery, mark_index, mark_resolve
- Persistent Graph — disk-backed graph store, incremental crawl, backlinks
- Read Auth — per-path read token enforcement for private networks
- Security Hardening — systemd sandboxing, security docs, write isolation