Repository navigation
Webapp: count only mapped frameworks in the home-page headline - #188
Merged
Merged
Conversation
The home page added every registry to the framework list, mapped or not, and summed every registry's controls into "Registry Controls". A registry that lands before its rows (NIST AI 600-1 in #187) would have shown 27 frameworks against the README's 26 mapped, and added 211 unmapped controls (+19%). Frameworks now come from the mapping rows alone, and the controls total only counts registries a row cites. No change to today's numbers: all 26 registries are mapped. New webapp test pins the hero to stats.json's frameworks.mapped. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
8 of 19 tasks
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.
What this changes
The webapp home page added every registry to its framework list, mapped or not, and summed every registry's controls into Registry Controls. A registry that lands before any row maps it would inflate both numbers. NIST AI 600-1 (#187) is the first such case.
Measured with #187 merged onto
main, without this fix:mainmain+ #187main+ #187 + this PRdocs/index.html:FRAMEWORKSnow comes from the mapping rows alone. That one list feeds the hero, the framework browser, the selectors and the score tool, so an unmapped registry no longer shows up as a 0%-coverage framework anywhere. The controls total only counts registries a row cites.scripts/webapp.test.mjs: new test. The hero's Frameworks must equalstats.jsonframeworks.mapped, and Registry Controls must equal the sum over mapped registries only.No visible change today. All 26 registries on
mainare mapped, so every number stays the same until an unmapped registry lands.C2: this is a webapp code change, approved by the maintainer on 2026-10-02 as the guard to land alongside #187.
Verification
main(633c59a): validate 0 errors / 91 warnings,stats:checkcurrent, 89/89.stats:checkcurrent, 90/90 (twice), no regen drift.main+ NIST AI 600-1: register the framework and transcribe its 211 suggested actions #187 merged and regenerated, the new test fails without the fix (actual '27',expected '26') and passes with it (5/5 webapp tests).Not changed
The hero's Registry Controls still counts every registry item (layers and techniques as well as controls), unlike
stats.jsoncontrols.total, which countskind: controlonly (1,107 vs 973). Aligning the two would change a live number, so it's left for a separate decision.🤖 Generated with Claude Code