omnigraph/docs
Ragnor Comerford 5c788de5e4
docs(rfc-003): canonical implementation blueprint for a from-scratch build
Make RFC-003 the authoritative build-from-scratch spec, folding in what the
#157 reference implementation proved out plus the architecture for a clean redo.

- New "Implementation Blueprint" (B.1-B.13): the omnigraph-mcp transport crate
  + McpBackend trait (dependency must be server -> mcp to avoid a Cargo cycle),
  the verified rmcp 1.7 transport (conformance MUSTs for free), backend reuse
  (do_* / run_query / run_mutate / authorize / api), the 13-tool catalog +
  Cedar mapping, ParamKind -> JSON Schema, list/call deny-masking + isError
  split, resources, auth + client-compat matrix, tests, and locked decisions.
- Routing resolved: per-graph /mcp; graphs_list + omnigraph://graphs dropped
  from MCP (graph discovery stays REST-only via GET /graphs); no flat
  graph_id-in-call endpoint.
- Marked the old "Reconciliation" section historical and the section-5 sketches
  as design rationale (superseded by the blueprint where they differ); resolved
  the Open Questions.
2026-06-10 21:48:57 +02:00
..
dev docs(rfc-003): canonical implementation blueprint for a from-scratch build 2026-06-10 21:48:57 +02:00
releases feat(engine): sweep & remove legacy __run__ branch guard (MR-770) (#132) 2026-06-07 18:33:14 +03:00
rfcs governance: external contribution model (issues/discussions/RFCs/PRs) (#143) 2026-06-06 23:58:08 +03:00
user docs: document the in-server MCP surface (RFC-003) 2026-06-09 15:15:46 +02:00