Skip to content

SEP: Require Conformance Tests for Standards Track SEPs to Reach Final Status#2484

Draft
pcarleton wants to merge 4 commits intomainfrom
pcarleton/conformance-requirement-sep
Draft

SEP: Require Conformance Tests for Standards Track SEPs to Reach Final Status#2484
pcarleton wants to merge 4 commits intomainfrom
pcarleton/conformance-requirement-sep

Conversation

@pcarleton
Copy link
Copy Markdown
Member

Adds a conformance test requirement to the Accepted → Final transition for Standards Track SEPs.

Summary

Before a Standards Track SEP that changes observable protocol behavior can be marked Final:

  • A conformance scenario tagged with the SEP number must be merged in the conformance repository
  • The scenario must include a structured traceability file (sep-NNNN.yaml) mapping each MUST/MUST NOT to a check or a documented exclusion
  • The sponsor verifies the traceability file is complete

Process and Informational SEPs are exempt, as are Standards Track SEPs with no observable protocol behavior.

Why

SEP-1730's SDK tiering depends on conformance tests, but nothing keeps the suite synchronized with the spec. This ties test creation to the SEP lifecycle so the suite grows exactly as fast as the spec does.

Supersedes

SEP-1627 (Conformance Testing)

Changes

  • seps/0000-*.md — the SEP itself (number will be updated to match this PR)
  • docs/community/sep-guidelines.mdx — adds conformance test gate to the Accepted → Final workflow, updates flowchart and status table
  • Generated docs

@mintlify
Copy link
Copy Markdown

mintlify bot commented Mar 27, 2026

Preview deployment for your docs. Learn more about Mintlify Previews.

Project Status Preview Updated (UTC)
mcp-staging 🟢 Ready View Preview Mar 27, 2026, 6:07 PM

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

proposal SEP proposal without a sponsor. SEP

Projects

Status: No status

Development

Successfully merging this pull request may close these issues.

2 participants