docs: architecture and v2 plan for MCP + REST agent layer#36
Open
vishwakt wants to merge 2 commits into
Open
Conversation
Captures the agent-native trading lab design: stdio MCP server + FastAPI REST + bundled local UI sharing a single typed service layer. Includes the v1.0/v1.1/v1.2 roadmap, security model (one API key + confirmation gates), tool inventory, and a 7-branch implementation plan with file lists and acceptance criteria per phase. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
Resolves the naming clash between the agent-layer initiative's
internal milestones ("v1.0/v1.1/v1.2") and the project's semver
release line (v0.1.0 already shipped). Codenames now map cleanly
onto semver releases:
v2 → 0.2.0 (local-only agent layer, this initiative)
v3 → 0.3.0 (self-host bundle on user's AWS)
v4 → 0.4.0 (native Tauri wrapper)
Branch prefix updated from `v1/<feature>` to `v2/<feature>` to match
the milestone vocabulary. Adds a release-strategy note to PLAN.md
(all seven phases land as `[Unreleased]` entries, cut as a single
0.2.0 release at the end — no per-phase tags) and a codename/semver
mapping table at the top of MCP-ARCHITECTURE.md's Roadmap section.
vishwakt
changed the title
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.
Summary
0.2.0/0.3.0/0.4.0), security model, and the launch-tweet draft.requiresConfirmationannotations + REST 409→token flow) instead of three-tier RBAC. RBAC adds zero protection in single-user-local mode; gates handle prompt-injection and accidental destructive calls. RBAC reintroduced in v3 when multi-user is real.mainas[Unreleased]changelog entries; once Phase 7 ships, cut a single semver0.2.0release. No per-phase tags, no patch versions in between — one launch moment.No code changes in this PR — pure documentation. Implementation begins on
v2/service-layerafter this lands.Naming convention going forward
v2/v3/v4track the agent-layer initiative0.2.0/0.3.0/0.4.0track project releases (current shipped:0.1.0)v2/<feature>for v2 work; existingdocs/,ci/,fix/,chore/prefixes retained for non-feature workTest plan
v1.0/v1.1/v1.2references remain (verified viagrep -nE 'v1\.[012]|v1/' docs/)