Roadmap

Where demarkus has been and where it's going. This page is a hub: links to the topic files under /roadmap/ and to each entry in them. Status lives in the entry, on the Status: line under its heading, never here.

Topics

• scope and content contract: What the server will and will not serve, and how the markdown-only rule is enforced.

  • Scope: Markdown-Only Server
  • Markdown-Only Content Contract

• protocol phases: The six numbered phases from the read-only MVP to universe deployment, and the verb set.

  • Phase 1: MVP (Read-Only)
  • Phase 2: Publish Operations
  • Phase 3: Agent-Native & Advanced Features
  • Phase 4: The Information Graph
  • Phase 5: The Demarkus Agent & Private Networks
  • Phase 6: Universe Deployment
  • Verb Set

• knowledge layer, catalog, and store: LOOKUP, OKF metadata, universe-wide lookup, and store consistency work.

  • LOOKUP Catalog Verb
  • Open Knowledge Format (OKF) Compatibility
  • Store: make LIST and FETCH agree on flat files
  • Universe-wide LOOKUP

• graph and storage backends: The 2026-07-13 knowledge-layer analysis: graph hub seeding, edge semantics, backend parity, and the remaining gaps.

  • Knowledge Layer & Storage Backends

• MCP and agent surface: The MCP tool surface agents see and the host-agnostic layer planned above it.

  • MCP Agent Ergonomics & Attach Surface
  • Host-Agnostic MCP Layer

• plugins and vocabulary: Per-host memory plugins, their release history, and the product vocabulary they expose.

  • Plugins
  • OpenCode Memory Plugin
  • Vocabulary: soul becomes memory
  • Cursor Memory Plugin
  • Vocabulary revision: soul is the instance name

• distribution, deployment, and hosted service: Packaging, the single-host install, token issuance, the production knowledge system, and the memory broker.

  • Distribution & Package Management
  • Build Targets
  • Remote Token Issuance
  • Five-Minute Appliance & Install Hardening
  • Production Shared Knowledge System
  • Memory Broker: memory-as-a-service for MCP hosts
  • Tenant identity pinning

• backlog and polish: TUI polish, deliberately unprioritized features, operational polish, and docs hygiene.

  • 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 and the hub stays a link page.

• /roadmap.md (this file): links to every topic file and, under each, to its entries by name. No status, dates, or summaries copied from entries.
• /roadmap/<topic>.md: one ## section per entry, headed by the entry name alone, with Status: <active|planned|done|backlog> (<dates, PRs>) as the first line under it. Append new entries at the end of the topic file and add the hub link in the same edit.
• Headings are the link anchors and never change; status changes edit the Status: line and add dated lines below.
• New topic file when an area has none or a file passes about 16KB; never a second catch-all.