SDK Tiering System changedcommunity/sdk-tiers
Upstream edited this page at 28 Jul 2026 15:42 UTC, give or take a minute or two: the time comes from Anthropic’s own sitemap rather than from a commit. This site recorded the change at 28 Sep 2026 22:07 UTC.
Upstream edited
Recorded here
Lines+28added
Lines−28removed
From line
29
where the diff opens
First seen
14 Aug 2026
this site's first read of the page
Recorded edits2to this page, all time
The whole hunk
from line 29, old and new numbered
/
from line 29
2929
3030## Tier Requirements
3131
32| Requirement | Tier 1: Fully Supported | Tier 2: Commitment to Full Support | Tier 3: Experimental |
33| --------------------------- | ---------------------------------------------------------------------------------------- | ---------------------------------------------------------------- | ---------------------- |
34| **Conformance Tests** | 100% pass rate | 80% pass rate | No minimum |
35| **New Protocol Features** | Before new spec version release, timeline agreed per release based on feature complexity | Within 6 months | No timeline commitment |
36| **Issue Triage** | Within 2 business days | Within a month | No requirement |
37| **Critical Bug Resolution** | Within 7 days | Within two weeks | No requirement |
38| **Stable Release** | Required with clear versioning | At least one stable release | Not required |
39| **Documentation** | Comprehensive with examples for all features | Basic documentation covering core features | No minimum |
40| **Dependency Policy** | Published update policy | Published update policy | Not required |
41| **Roadmap** | Published roadmap | Published plan toward Tier 1 or explanation for remaining Tier 2 | Not required |
32| Requirement | Tier 1: Fully Supported | Tier 2: Commitment to Full Support | Tier 3: Experimental |
33| - | - | - | - |
34| **Conformance Tests** | 100% pass rate | 80% pass rate | No minimum |
35| **New Protocol Features** | Before new spec version release, timeline agreed per release based on feature complexity | Within 6 months | No timeline commitment |
36| **Issue Triage** | Within 2 business days | Within a month | No requirement |
37| **Critical Bug Resolution** | Within 7 days | Within two weeks | No requirement |
38| **Stable Release** | Required with clear versioning | At least one stable release | Not required |
39| **Documentation** | Comprehensive with examples for all features | Basic documentation covering core features | No minimum |
40| **Dependency Policy** | Published update policy | Published update policy | Not required |
41| **Roadmap** | Published roadmap | Published plan toward Tier 1 or explanation for remaining Tier 2 | Not required |
4242
4343**Issue Triage** means labeling and determining whether an issue is valid, not resolving the issue.
4444
from line 106
106106
107107### Type (pick one)
108108
109| Label | Description |
110| ------------- | ----------------------------- |
111| `bug` | Something isn't working |
112| `enhancement` | Request for new feature |
113| `question` | Further information requested |
109| Label | Description |
110| - | - |
111| `bug` | Something isn't working |
112| `enhancement` | Request for new feature |
113| `question` | Further information requested |
114114
115115Repositories using [GitHub's native issue types](https://docs.github.com/en/issues/tracking-your-work-with-issues/using-issues/managing-issue-types-in-an-organization)
116116satisfy this requirement without needing type labels.
from line 119
119119
120120Use these exact label names across all repositories to enable consistent reporting and analysis.
121121
122| Label | Description |
123| -------------------- | ------------------------------------------------------- |
124| `needs confirmation` | Unclear if still relevant |
125| `needs repro` | Insufficient information to reproduce |
126| `ready for work` | Has enough information to start |
127| `good first issue` | Good for newcomers |
128| `help wanted` | Contributions welcome from those familiar with codebase |
122| Label | Description |
123| - | - |
124| `needs confirmation` | Unclear if still relevant |
125| `needs repro` | Insufficient information to reproduce |
126| `ready for work` | Has enough information to start |
127| `good first issue` | Good for newcomers |
128| `help wanted` | Contributions welcome from those familiar with codebase |
129129
130130### Priority (only if actionable)
131131
132| Label | Description |
133| ----- | --------------------------------------------------------------- |
134| `P0` | Critical: core functionality failures or high-severity security |
135| `P1` | Significant bug affecting many users |
136| `P2` | Moderate issues, valuable feature requests |
137| `P3` | Nice to haves, rare edge cases |
132| Label | Description |
133| - | - |
134| `P0` | Critical: core functionality failures or high-severity security |
135| `P1` | Significant bug affecting many users |
136| `P2` | Moderate issues, valuable feature requests |
137| `P3` | Nice to haves, rare edge cases |
138138
139139**P0 (Critical)** issues are:
140140
No line in this hunk matches that.