Roadmap
Where demarkus has been and where it's going. This page is the hub: one row per roadmap item, with the detail in a topic file under /roadmap/.
Active and planned
| Item | Status | Where |
|---|---|---|
| Phase 5: The Demarkus Agent & Private Networks | active | protocol phases |
| Phase 6: Universe Deployment | planned | protocol phases |
| Distribution & Package Management | planned | distribution, deployment, and hosted service |
| Plugins | active | plugins and vocabulary |
| Knowledge Layer & Storage Backends | active | graph and storage backends |
| Store: make LIST and FETCH agree on flat files | active | knowledge layer, catalog, and store |
| Host-Agnostic MCP Layer | planned | MCP and agent surface |
Topic files
- scope and content contract: What the server will and will not serve, and how the markdown-only rule is enforced. (2 entries)
- protocol phases: The six numbered phases from the read-only MVP to universe deployment, and the verb set. (7 entries)
- knowledge layer, catalog, and store: LOOKUP, OKF metadata, universe-wide lookup, and store consistency work. (4 entries)
- graph and storage backends: The 2026-07-13 knowledge-layer analysis: graph hub seeding, edge semantics, backend parity, and the remaining gaps. (1 entry)
- MCP and agent surface: The MCP tool surface agents see and the host-agnostic layer planned above it. (2 entries)
- plugins and vocabulary: Per-host memory plugins, their release history, and the product vocabulary they expose. (5 entries)
- distribution, deployment, and hosted service: Packaging, the single-host install, token issuance, the production knowledge system, and the memory broker. (7 entries)
- backlog and polish: TUI polish, deliberately unprioritized features, operational polish, and docs hygiene. (4 entries)
Done
| Item | Where |
|---|---|
| Phase 1: MVP (Read-Only) | protocol phases |
| Phase 2: Publish Operations | protocol phases |
| Phase 3: Agent-Native & Advanced Features | protocol phases |
| Phase 4: The Information Graph | protocol phases |
| Verb Set | protocol phases |
| LOOKUP Catalog Verb | knowledge layer, catalog, and store |
| Open Knowledge Format (OKF) Compatibility | knowledge layer, catalog, and store |
| MCP Agent Ergonomics & Attach Surface | MCP and agent surface |
| Remote Token Issuance | distribution, deployment, and hosted service |
| Five-Minute Appliance & Install Hardening | distribution, deployment, and hosted service |
| Markdown-Only Content Contract | scope and content contract |
| OpenCode Memory Plugin | plugins and vocabulary |
| Production Shared Knowledge System | distribution, deployment, and hosted service |
| Universe-wide LOOKUP | knowledge layer, catalog, and store |
| Memory Broker: memory-as-a-service for MCP hosts | distribution, deployment, and hosted service |
| Tenant identity pinning | distribution, deployment, and hosted service |
| Vocabulary: soul becomes memory | plugins and vocabulary |
| Cursor Memory Plugin | plugins and vocabulary |
| Vocabulary revision: soul is the instance name | plugins and vocabulary |
Backlog and reference
- Scope: Markdown-Only Server
- Build Targets
- TUI Polish
- Features Not Prioritized
- Operational Polish
- Docs Hygiene
Related documents
- Five-minute appliance: the appliance work this roadmap section records
- OKF type adoption: the type policy behind the OKF section
- Postgres backend: the second store backend in the knowledge layer
- Version retention: the retention work named in the backlog
- Obsidian plugin plan: the plugin released in the plugins section
Format
The roadmap is a hub plus topic files, so no single document outgrows the full-body fetch threshold.
/roadmap.md(this file): one row per item with status and a link; no detail here. Statuses: active, planned, done, backlog./roadmap/<topic>.md: the entries for one area, each a##section titled<Name>: <STATUS> (<dates, PRs>). Append new sections at the end of the topic file and add the row here in the same edit.- New topic file when an area has no file yet or a file passes about 16KB; never a second catch-all.
- Anchors are stable: the section heading is the link target. Do not retitle a shipped entry; add a dated line under it.