Documentation Map
The public docs are now split into three kinds of pages:
- Start here pages explain what exists and how to use it.
- Planning pages describe future work and implementation sequencing.
- Reference pages preserve detailed decisions, compatibility notes, and checklists.
Start Here
| Page | Use it for |
|---|---|
| Current features | Fast inventory of shipped capabilities. |
| Technical overview | API, MCP, CLI, configuration, containers, testing, and project structure. |
| Agent integration | MCP tools, resources, prompts, and recommended agent workflows. |
| Storage provider examples | Local and provider-specific setup examples. |
| Observability | Logging, readiness, tracing, metrics, and local observability compose setup. |
| Security | Vulnerability reporting and security expectations. |
Planning Pages
| Page | Scope |
|---|---|
| Roadmap | Ordered capability phases from MVP through optional sync/cloud work. |
| Planned features | Human-friendly summary of what is not shipped yet. |
| Prioritized feature plan | Near-term implementation queue and priority notes. |
| First release readiness plan | Release hardening checklist. |
| Release, container, and docs publishing plan | Packaging and publishing work. |
| Plugin readiness plan | Client/plugin setup and verification work. |
| Observability, logging, and telemetry plan | Detailed observability implementation plan. |
Integration And Compliance Plans
| Page | Scope |
|---|---|
| MCP plan | MCP feature direction. |
| MCP client smoke plan | Client smoke strategy. |
| Real-client MCP smoke plan | Real-client verification strategy. |
| OpenClaw native MCP setup | OpenClaw-specific setup. |
| MCP utility compliance plan | MCP utility behavior and compliance. |
| MCP authorization compliance plan | Bearer token and OAuth resource metadata work. |
| Google OAuth Connect UI plan | Google sign-in, web sessions, hub-issued MCP tokens, and client setup UI. |
| Bruno integration test plan | Bruno API/MCP smoke coverage. |
Feature Plans
| Page | Scope |
|---|---|
| Storage BYOA plan | Storage abstraction and provider behavior. |
| Neo4j Aura graph memory plan | Neo4j AuraDB vector provider, graph record mirror, and graph-aware retrieval path. |
| Deterministic ingestion plan | Schema-first ingestion, dedupe, and deterministic behavior. |
| Browser extension capture plan | Browser capture boundary, API contract, and future extension repos. |
| Token budget plan | Token accounting and context construction. |
| CLI implementation plan | CLI commands and behavior. |
| Project workspace collaboration plan | Workspace collaboration model. |
| Handoff memory plan | Cross-agent and cross-environment task continuity when context or budget runs out. |
| Project promotion plan | Promotion assets and external-facing positioning. |
| Release promotion assets | Release announcement and demo assets. |
| Repository governance settings | Repository settings and governance checklist. |
| Recurring codebase cleanup plan | Ongoing engineering-health review. |
Improvement Backlog
The improvement plans collect focused follow-up work for client feedback, MCP result shapes, retrieval precision, context building, conversation grouping, memory quality, edge-case coverage, explicit save intent, handoff memory, Google OAuth connect UX, vector database evaluation, and Neo4j Aura graph memory.