Repository navigation
Conversation
…e mirror replaces it Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01NczDiGthqcWLSoHxXN7UFG
The outcome covers both directions FSD speaks MCP: flows as servers proven on real clients (placeholder epic), and workforce connectors (FIX-2615). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01NczDiGthqcWLSoHxXN7UFG
|
The latest updates on your projects. Learn more about Vercel for GitHub.
1 Skipped Deployment
|
Codex Review Summary: ✅ CompletedThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
Second look + architecture passVerdict: Appropriately scoped. This PR adds only docs under Findings
Considered and left alone
Architecture notes for the epics below this projectI am recording these here rather than as requests, since the epics own them.
No other changes requested. Generated by Claude Code |
Code Review ✅ Approved🟢 Low risk · Adding MCP project-spec documents and a diagram records scope and status without changing executable behavior, so impact is limited to documentation. Standing project-spec for the MCP Linear project, covering how FSD speaks MCP as a server and as a client, the outcome it targets, and the epics under it. No issues found. VerificationRules No rules evaluated Functional validation Not enabledFor more verification details, comment OptionsAuto-apply is off → Gitar will not commit updates to this branch. Comment with these commands to change the behavior for this request:
Was this helpful? React with 👍 / 👎 | Gitar |
Requested by Jake · project thread
As of 2026-11-10 · set at 2681f7d
FSD speaks MCP in two directions, and both should be solid enough to release. As a server, any flow is its own MCP server; that shipped with FIX-22 and has not been tested hard against real clients. As a client, workforce reaches other MCP servers for its workers and coding runs; FIX-2615 is deciding what a connector is and what a project is.
Above the fence is how FSD speaks MCP. What a given flow exposes over its server, such as workforce's own tools in FIX-2331, belongs to that flow's owner.
The arc has no figure yet: one epic is filed and has not started, and the other lane is a placeholder. It becomes a figure when a second epic is filed.
The epics (live table):
Reviewers · look here
Spec · Decisions · Rules · Plan · Prior Linear description, verbatim
How to review this
This is a project-spec: the standing outcome, the cross-epic decisions, and the live state of one Linear project, in four documents. It is not an implementation plan, not any one epic's objective, and not a design.
In scope to challenge:
DECISIONS.mdthat binds several epics, or a rule inBUSINESS-RULES.mdwith no owner or two.Out of scope — owned by the epic specs below it:
Feedback in the second list is routed to the epic it concerns, not folded in here.
🤖 Generated with Claude Code
https://claude.ai/code/session_01NczDiGthqcWLSoHxXN7UFG