# 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](/roadmap/scope.md): what the server will and will not serve, and how the markdown-only rule is enforced
- [protocol phases](/roadmap/protocol-phases.md): the six numbered phases from the read-only MVP to universe deployment, and the verb set
- [realtime](/roadmap/realtime.md): WATCH, the change hub, replica hints, and the live layers above them
- [knowledge layer, catalog, and store](/roadmap/knowledge-layer.md): LOOKUP, OKF metadata, universe-wide lookup, the bucket store commit log, federation, store consistency
- [graph and storage backends](/roadmap/graph-and-backends.md): graph hub seeding, edge semantics, backend parity, and the remaining gaps
- [deterministic memory](/roadmap/deterministic-memory.md): memory continuity and hygiene computed from versions, metadata and typed edges
- [MCP and agent surface](/roadmap/agent-surface.md): the MCP tool surface agents see and the host-agnostic layer planned above it
- [plugins and vocabulary](/roadmap/plugins.md): per-host memory plugins, their release history, and the product vocabulary they expose
- [distribution, deployment, and hosted service](/roadmap/deployment.md): packaging, install, token issuance, the production knowledge system, the memory broker, rollouts
- [backlog and polish](/roadmap/backlog.md): TUI polish, deliberately unprioritized features, operational polish, docs hygiene

## Graph delivery

- [Graph implementation roadmap](/roadmap/graph-focus.md): ordered slices for graph correctness, relevance, performance, usability, and the benchmark discipline behind them
- [Graph evaluation delivery](/roadmap/graph-evaluation.md): real-corpus benchmark prerequisites

## Related documents

- [Five-minute appliance](/plans/five-minute-appliance.md): the appliance work this roadmap section records
- [OKF type adoption](/plans/okf-type-adoption.md): the type policy behind the OKF section
- [Postgres backend](/plans/postgres-backend.md): the second store backend in the knowledge layer
- [Version retention](/plans/version-retention.md): the retention work named in the backlog
- [Token-efficient retrieval](/plans/token-efficient-retrieval.md): the body match and lean envelope work in the knowledge layer section
- [Realtime demarkus](/plans/watch-agent-messaging.md): the plan behind the realtime section
- [Bucket store change journal](/plans/bucket-store-change-journal.md): the plan behind the bucket store change journal entry
- [Broker in process](/plans/broker-in-process.md): the plan behind the broker in the knowledge server process entry
- [Bucket store commit log](/plans/bucket-commit-log.md): the plan behind the commit log entry
- [Commit log rollout](/plans/bucket-commit-log-rollout.md): the plan behind the production rollout entry
- [Agent in process](/plans/agent-in-process.md): the plan behind the federation graph entry
- [The memory wall](/plans/memory-wall.md): the plan behind the memory wall entry
- [Purge](/plans/purge.md): the plan behind the purge entry
- [Knowledge policy hardening](/plans/knowledge-policy-hardening.md): the plan behind the knowledge policy hardening entry
- [demarkus 1.0](/plans/v1.md): 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.