From 2895a08be4c0a82e1396208656cb152d0739a266 Mon Sep 17 00:00:00 2001 From: chaksaray Date: Fri, 31 Jul 2026 21:10:08 +0700 Subject: [PATCH] fix: GOVERNANCE.md claimed a deprecation_reason schema field that doesn'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. --- GOVERNANCE.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/GOVERNANCE.md b/GOVERNANCE.md index e6b31e0..802591b 100644 --- a/GOVERNANCE.md +++ b/GOVERNANCE.md @@ -16,8 +16,8 @@ and having positive + negative detection fixtures. removal, required field addition) require a new schema version and a migration script. Minor additions (new optional fields) are non-breaking and can ship in a patch release. -**Deprecation:** a record is deprecated by setting `status` to `"deprecated"` with a -`deprecation_reason`. `ave_id` values are never reused or deleted. +**Deprecation:** a record is deprecated by setting `status` to `"deprecated"`, with a +note explaining why. `ave_id` values are never reused or deleted. **Crosswalk updates:** maintainer or contributors may update crosswalk JSON files to add new tool mappings. No record changes required.