docs: architecture reference + clarify CLI vs MCP-server usage - #1
Merged
Conversation
New docs/ARCHITECTURE.md: the one-core/two-surface design, every capability (what/why/source), the grounding model, the read-only/no-keys security model, and — front and center — that you never host a server: the CLI is one-shot, and 'rome mcp' is a stdio server your MCP client launches on demand. README MCP section updated to say the same.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds
docs/ARCHITECTURE.md(one core / two surfaces, every capability, grounding + security model) and clarifies the common question: you never host a server — the CLI is standalone one-shot, androme mcpis a stdio server your MCP client spawns on demand (no port, no daemon). README MCP section updated to match. Docs-only; 27/27 tests still green, links resolve, leak-clean.