fix: GOVERNANCE.md deprecation_reason field claim - #106
Merged
Conversation
…sn't exist Found while writing v1.2.0 roadmap issues (#103-105): deprecation_reason appeared nowhere else in the repo -- not in the schema, not on any record (none currently use status: deprecated), and not named by docs/specs/scaling-and-governance.md Section 3, the newer canonical policy doc, which only ever says 'a note explains why,' never a specific field. Corrected GOVERNANCE.md's wording to match, rather than adding the field to make the claim true -- that's a separate, deliberate schema decision if it's ever wanted, not implied by this fix.
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
1 participant
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.
GOVERNANCE.md claimed deprecation requires setting a
deprecation_reasonfield, which doesn't exist anywhere: not in the schema, not on any record, and not named by scaling-and-governance.md Section 3 (the newer policy doc), which only ever says 'a note explains why.' Corrected the wording to match reality rather than adding the field, which would be a separate schema decision. Found while verifying claims for the v1.2.0 roadmap issues (#103, #104, #105).