Repository navigation
data: NIST AI RMF registry follow-ups to #219 (typography, 8 titles, two notes) - #221
Open
emmanuelgjr wants to merge 1 commit into
Open
emmanuelgjr wants to merge 1 commit into
emmanuelgjr wants to merge 1 commit into
Conversation
- GV-1.3 and GV-1.7: apostrophe U+2019, and MS-2.7: en-dashes U+2013, as printed in NIST AI 100-1 (checked character by character in the PDF). - Eight titles that named a different subject than their published statement: GV-2.2, GV-3.2, GV-4.2, GV-4.3, MP-1.5, MP-5.2, MG-4.1, MG-4.2. Titles are editorial display labels; descriptions are unchanged. - inventory_completeness note: the old registry held 85 entries, but mapping rows cite 15 distinct ids (not "the 85 entries mappings cited"). - nist-ai-600-1.json $comment: all 49 parent subcategories now resolve. No description wording, no mapping row, no count changed. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This branch has not been deployed
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.
Follow-ups from the #219 review. It's all transcription and editorial labels. No description wording, mapping row or count changes.
What changes
'→’(U+2019)–(U+2013) around "as identified in the MAP function"inventory_completeness.notesaid the old registry held "only the 85 entries existing mappings cited"nist-ai-600-1.json$commentsaid MG-4.3, MP-3.4, MS-2.12 and MS-2.13 don't resolve8 title corrections
GV-4.2 is cited by one row (its
control_nameis the row's own label and is unchanged here). The other seven are cited by none.Version check: AI RMF 1.0 (NIST AI 100-1, January 2023) is still current. NIST's framework page says a revision is under way, with no draft or number yet (checked 2026-10-09).
Verification
node scripts/validate.js: 0 errors, 92 warnings, 329 passed (same asmain)npm run test:scripts: 137/137npm run stats:check: current; a secondgenerate.jsrun produces no driftRefs #219, #217, #220
🤖 Generated with Claude Code