Roadmap

Where demarkus has been and where it's going. This page is a hub: one link per topic file under /roadmap/. Each topic file lists its own entries, and status lives in the entry, never here.

Topics

• scope and content contract: what the server will and will not serve, and how the markdown-only rule is enforced
• protocol phases: the six numbered phases from the read-only MVP to universe deployment, and the verb set
• realtime: WATCH, the change hub, replica hints, and the live layers above them
• knowledge layer, catalog, and store: LOOKUP, OKF metadata, universe-wide lookup, the bucket store commit log, federation, store consistency
• graph and storage backends: graph hub seeding, edge semantics, backend parity, and the remaining gaps
• deterministic memory: memory continuity and hygiene computed from versions, metadata and typed edges
• usability: what users and agents hit after install: tool sets, upgrades, first run, vocabulary, warnings
• MCP and agent surface: the MCP tool surface agents see and the host-agnostic layer above it
• plugins and vocabulary: per-host memory plugins, their release history, and the product vocabulary they expose
• distribution, deployment, and hosted service: packaging, install, token issuance, the production knowledge system, the memory broker, rollouts
• backlog and polish: TUI polish, deliberately unprioritized features, operational polish, docs hygiene

Graph delivery

• Graph implementation roadmap: ordered slices for graph correctness, relevance, performance, usability, and the benchmark discipline behind them
• Graph evaluation delivery: real-corpus benchmark prerequisites

Related documents

• Memory and knowledge layering: the active step sequence of October 2026 (model carve-out, gates in both tiers, the binary merge, SDK)
• 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
• Token-efficient retrieval: the body match and lean envelope work in the knowledge layer section
• Realtime demarkus: the plan behind the realtime section
• Bucket store change journal: the plan behind the bucket store change journal entry
• Broker in process: the plan behind the broker in the knowledge server process entry
• Bucket store commit log: the plan behind the commit log entry
• Commit log rollout: the plan behind the production rollout entry
• Agent in process: the plan behind the federation graph entry
• The memory wall: the plan behind the memory wall entry
• Purge: the plan behind the purge entry
• Knowledge policy hardening: the plan behind the knowledge policy hardening entry
• demarkus 1.0: the definition of 1.0 that the memory gateway parity entry gates

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): one line per topic file. No entry links, status, dates, or summaries copied from entries.
• /roadmap/<topic>.md: one ## section per entry, headed by the entry name alone, with the status line first under it.
• Status line shape: Status: <active|planned|done|backlog> (<dates, PRs>). Status changes edit that line and add dated lines below.
• New entries append at the end of their topic file; the hub changes only when a topic file is added.
• Headings are the link anchors and never change.
• New topic file when an area has none or a file passes about 16KB; never a second catch-all.