Open
Conversation
Define "reference implementation" for Standards Track SEPs as the spec changes (schema, spec text, changelog entry) added to the SEP PR — not SDK implementations, which follow after release. State that SEPs in Final status can be merged. Aligns the guidelines, status table, workflow diagram, and SEP template.
Rename the section to "Specification Changes" rather than redefining "reference implementation" to mean spec edits. Note that SDKs can begin implementing once the SEP is merged, not after the next spec release.
|
Preview deployment for your docs. Learn more about Mintlify Previews.
|
The SEP document section is for linking the prototype, not describing spec changes — those go directly in the PR as schema/docs/changelog files. Align the guidelines format list with the template.
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
2 participants
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
Tightens up what's required for a SEP to reach
finalstatus and be merged.The previous wording around "reference implementation" was ambiguous — it wasn't clear whether it meant SDK PRs, spec changes, or something else, and in practice most Final SEPs had no reference implementation section at all. Note that the guidelines already have "prototype implementation" as a requirement to review. It seems that "reference implementation" is a leftover phrase from before we added the prototype requirement.
Changes
final.seps/TEMPLATE.mdto match.