docs(claude.md): reframe architecture around Workspace launcher + Trading-context injector#213
Merged
Conversation
…ding-context injector
The opening one-liner was selling the persistence model ("file-driven,
no database") — accurate but the wrong layer for an incoming-session
briefing. From a code-writing perspective Alice is now a Workspace
launcher (capability ships as templates + satellite repos, not src/
deps) plus a Trading-context injector (market data / analysis / news /
UTA SDK, surfaced into workspaces via MCP). Re-anchored the opening on
that, and reorganized Key Architecture to match:
- Added Inbox section (Workspace → user push via InboxStore +
inbox_push MCP tool), distinct from the legacy NotificationsStore
- Renamed "AI provider layer" → "Provider routing — GenerateRouter";
dropped AgentCenter from the "top-level orchestration" framing and
noted the Workspace path runs its model loop inside the native CLI
- Consolidated AgentCenter / ConnectorCenter / NotificationsStore
into a dedicated "Legacy chat path" section — still wired for
Telegram / MCP Ask / heartbeat / /chat SSE, but no new feature
work routes through it
- ToolCenter section now names workspace-tool-center as the actual
Trading-context injection point inside a workspace
- Project Structure tree: core/ flags the legacy trio and adds
InboxStore; connectors/ marked as legacy push channels
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
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
InboxStore+inbox_pushMCP tool — the Workspace → user push channel)./chatSSE, but no new work routes through it.core/flags the legacy trio and lists InboxStore;connectors/marked legacy).The README itself already moved past "file-driven" as a tagline some time ago; this just brings the dev-facing briefing in line.
Test plan
AgentCenter/ConnectorCenterreferences all sit in legacy-flagged contextsBoundary touch
None — docs only.
🤖 Generated with Claude Code