Fix #31: drop the 21 MAESTRO sub-controls, keep the seven layers - #184
Merged
Merged
Conversation
Maintainer ruling on #31: drop the sub-controls and retarget INC-137. The CSA source defines "a seven-layer reference architecture" and no numbered sub-controls. L1.1–L7.3 came from the initial seed, written against the superseded layer model, so several sat under a layer whose definition no longer described them (e.g. Runtime isolation under L5 Evaluation & Observability). - data/frameworks/maestro.json: 28 → 7 controls (the layers). inventory_completeness unknown/21 → complete 7 of 7, quoting the source. A changelog entry lists every removed id. - data/incidents.json: INC-137's three draft control_failures cited L5.1/L5.3 (added in #182); retargeted to the layer L4. Still drafts, confirmed_by empty. Each now attaches as drafted evidence to ASI03's existing L4 mapping, so evidence-orphan warnings drop 7 → 5. - Regenerated: docs/frameworks-registry.js, docs/data.js, docs/incidents.js, data/entries/ASI03.json, data/stats.json (registry controls 994 → 973). No mapping row cited a sub-control; MAESTRO rows all use L1–L7. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This was referenced Oct 3, 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
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.
Closes #31. Maintainer ruling (2026-10-01): drop the sub-controls and retarget INC-137.
Why drop rather than re-home
The CSA source this registry cites defines MAESTRO as "a seven-layer reference architecture", with no numbered sub-controls (checked on the CSA post today).
L1.1–L7.3came from the 2026-04-09 seed, written against the superseded layer model. Re-homing them would have meant authoring a taxonomy the framework doesn't have.Changes
data/frameworks/maestro.jsoninventory_completeness:unknown, 21 included →complete, 7 of 7, quoting the source. A changelog entry lists all 21 removed ids.data/incidents.jsoncontrol_failurescitedL5.1(×2) andL5.3, added in #182. Retargeted to the layerL4. Outcome, basis and source are unchanged. Still drafts,confirmed_byempty.docs/frameworks-registry.js,docs/data.js,docs/incidents.js,data/entries/ASI03.json,data/stats.json. No hand edits.Effects worth knowing
L4mapping as drafted (unconfirmed) evidence, soASI03.jsongains anevidenceblock. Confirming those drafts is still an SME step.Verified on this head
main's 93), 328 passedstats:checkcurrentgenerate.jsrun produces no drift🤖 Generated with Claude Code