specs: ingest idea #1143 — DecisionTable versioning rules#1144
Merged
ahouseholder merged 1 commit intoMay 18, 2026
Merged
Conversation
- Add VR-05 group to specs/versioning.yaml with VR-05-001 through VR-05-007 covering DecisionTable SemVer identity, major/minor/patch triggers, pre-stability (v0.x), and optional status field - Downgrade VR-01-006 from SHOULD to MAY (status field) - Tighten VR-02 to cover only DecisionPointGroup; remove stale 'or DecisionTable' clause and incorrect 'successor' framing - Update file-level description to mention decision tables - Archive idea #1143 to plan/history/ideas.md Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
ahouseholder
requested review from
cgyarbrough,
j--- and
sei-vsarvepalli
as code owners
Contributor
There was a problem hiding this comment.
Pull request overview
Docs-only PR that introduces SemVer rules for DecisionTable objects in specs/versioning.yaml (addressing issue #1143), tightens the existing DecisionPointGroup rules to remove stale DecisionTable references, and archives the processed idea.
Changes:
- Adds new VR-05 group (VR-05-001 through VR-05-007) defining SemVer rules for DecisionTable objects, including pre-stability (v0.x) and optional lifecycle status.
- Downgrades VR-01-006 (DecisionPoint status field) from SHOULD to MAY and removes the stale "or DecisionTable" clause from VR-02-001; updates the file-level description.
- Archives IDEA-1143 to
plan/history/ideas.md.
Reviewed changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.
| File | Description |
|---|---|
| specs/versioning.yaml | Adds VR-05 DecisionTable SemVer rules; tightens VR-02 wording; downgrades VR-01-006 priority; updates file description. |
| plan/history/ideas.md | New archive file recording IDEA-1143 and where its design was captured. |
This was referenced May 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.
Docs-only PR: adds DecisionTable SemVer rules to
specs/versioning.yaml.Changes
plan/history/ideas.mdRef #1143
No .py files changed.