Add ROADMAP.md outlining the path toward SEP-1730 Tier 1#465
Open
koic wants to merge 1 commit into
Open
Conversation
## Motivation and Context The SDK tiering system (SEP-1730) requires a published roadmap for both Tier 1 and Tier 2. Until now the Ruby SDK had no roadmap document, which left users without visibility into upcoming feature support and blocked the tiering requirement. This document records the SDK's current conformance status (all server and client scenarios passing), the API stability policy backed by Semantic Versioning and VERSIONING.md, the handling of features deprecated by the 2026-07-28 spec revision (SEP-2577), and how new MCP spec revisions will be tracked. Legacy SSE transport is explicitly called out as out of scope so users are not left guessing about it. ## How Has This Been Tested? Documentation-only change; there is no code to exercise. The conformance figures cited in the roadmap were taken from the current SEP-1730 tier assessment run against the latest main. ## Breaking Changes None. This adds a new top-level Markdown document and touches no code.
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.
Motivation and Context
The SDK tiering system (SEP-1730) requires a published roadmap for both Tier 1 and Tier 2. Until now the Ruby SDK had no roadmap document, which left users without visibility into upcoming feature support and blocked the tiering requirement.
This document records the SDK's current conformance status (all server and client scenarios passing), the API stability policy backed by Semantic Versioning and VERSIONING.md, the handling of features deprecated by the 2026-07-28 spec revision (SEP-2577), and how new MCP spec revisions will be tracked. Legacy SSE transport is explicitly called out as out of scope so users are not left guessing about it.
How Has This Been Tested?
Documentation-only change; there is no code to exercise. The conformance figures cited in the roadmap were taken from the current SEP-1730 tier assessment run against the latest main.
Breaking Changes
None. This adds a new top-level Markdown document and touches no code.
Types of changes
Checklist