This is where "available in many places" stops being abstract. The workspace builds a website, a Restate worker, trigger
jobs, a navigator CLI, an MCP server, and navigator-lsp. The LSP speaks JSON-RPC over stdio, has no telemetry, and
attaches to Markdown. Ordinary prose gets Markdown rules; templates get the notation rules on top, because a legal
template is both a document and a program. Most drafting happens in the WYSIWYG editor on the website; the LSP is what
carries the identical rules into the git side of the work, where the pull request and the GitHub Action see exactly what
the author saw.
Reaching those places is an arrival, not a claim that the migration has already finished. The AIDA catalog lives in
mcp/src/tools and exposes the same grounded operations through A2A and MCP, which is the one seam an assistant comes
through — there is no synthesized filesystem behind it, and long-term files stay in the object storage Navigator hosts.
That is the direction: a lawyer keeps working with documents while the system keeps the shape, the workflow, and the
rendered PDF aligned.