Clarify SEP-58 scope to common workflow - #1964
Merged
Merged
Conversation
leighmcculloch
marked this pull request as ready for review
June 18, 2026 13:10
leighmcculloch
enabled auto-merge (squash)
June 18, 2026 13:10
Contributor
There was a problem hiding this comment.
Pull request overview
This PR updates SEP-58 (Contract Build Reproducibility for Verification) to explicitly scope the proposed vocabulary to the common contract build workflow, preventing the SEP from being implicitly obligated to cover every bespoke build pipeline.
Changes:
- Bumped SEP-58 metadata (
Updateddate andVersion) to reflect the new revision. - Added a new Limitations bullet stating the vocabulary targets the common build workflow.
- Added a Design Rationale entry (and a Changelog entry) explaining why the SEP intentionally does not cover all possible workflows.
Co-authored-by: Copilot Autofix powered by AI <[email protected]>
fnando
approved these changes
Jun 18, 2026
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
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.
What
Add a scope statement to SEP-58 — a Design Rationale entry and a Limitations bullet — establishing that the vocabulary targets the common contract build workflow, not every possible build.
Why
Without a stated boundary, SEP-58 invites endless expansion to capture every bespoke build; the statement makes explicit that bespoke build inputs may not be fully expressible and that contracts should converge towards the common workflow rather than the proposal growing to satisfy each one.
Generated by Claude Code