Skip to main content
Audited and standardised 2026-10-12 against version 1.0.0. The rule this page tracks: a feature that works in the CLI must also be reachable from multimind backend, visible in the governance dashboard where a UI makes sense, and documented here. A dash means the surface does not exist. CI runs scripts/check_docs_parity.py, which fails when a CLI command or a backend route is not named anywhere under docs/. The API column lists routes on multimind backend (see openapi-platform.json). The dashboard has eight views: overview, audit, costs, inventory, guardrails, scan text, evidence report, compliance.

​
Matrix

​
Remaining gaps, by decision

  • CLI only, by design: models download, models export, models delete, convert, and context-transfer need torch or local files and are not server features. The CLI page says so.
  • SDK only, by design: the guard wrapper, regulatory watcher, differential privacy, framework adapters, hallucination detection, tracing, ModelSession, agents, memory, and fine-tuning are Python APIs. They have docs pages and tests but no CLI or route.
  • No dashboard view for chat, sessions, models, and RAG routes. The governance dashboard covers governance artifacts only. A chat playground lives in the separate frontend workspace.
  • Compliance history is per process. /v1/compliance/dashboard and /alerts reflect the POST /v1/compliance/monitor calls recorded in that backend process and reset on restart. From the CLI each command is its own process, so compliance dashboard prints nothing recorded. The durable artifacts remain the JSONL audit and cost logs.
  • Cross-origin calls from the dashboard page to the backend and the proxy need MULTIMIND_CORS_ORIGINS set on both servers. The views show a curl fallback when blocked.
  • models metrics prints empty tables from the CLI because the gateway monitor is per process. Documented on the CLI page.

​
Fixed on 2026-10-12

  • multimind compliance run-compliance no longer exits 1 after printing results.
  • multimind --version works.
  • Compliance dashboard and alerts record checks instead of rebuilding an empty shard per request.
  • compliance run-example names the real missing import.
  • Backend gained period, include_env, and the evidence-report filters, plus session save and load routes.
  • Dashboard gained scan text, evidence report, compliance, and proxy reload views.
  • Guard proxy accepts MULTIMIND_CORS_ORIGINS.
  • Docs gained the tracing page, full convert and context-transfer references, and eleven feature-status rows.