Relocate CRA mapping into docs/compliance_mapping/ (Phase 3'.1 step B-1)#10
Merged
Conversation
… B-1
Sets up the four-document compliance-mapping suite that Phase 3'.1
delivers (CRA Annex I / FDA Section 524B / ISO 21434 / UN R155).
The existing CRA file is preserved verbatim except for the header,
which now declares the suite layout and tightens the "compatible
with" wording requirement so subsequent mapping documents inherit a
single, consistent style.
- git mv docs/cra_compliance_mapping.md docs/compliance_mapping/cra_annex_i.md
(history preserved; SCOUT 2.5.0+ release evidence stays intact)
- header revised: doc version 1.0 -> 1.1, added "Last revised" field,
added explicit non-substitution rule for the "compliant with" /
"compliance" / "ready" wording (already enforced by
check_doc_consistency.py rule 3 -- this is the documentary side)
- "Companion mappings (Phase 3'.1, planned)" section added so readers
see the four-file roadmap and which Phase 3'.1 step ships each one
- references updated:
README.md, README.ko.md (Regulatory Alignment row)
docs/status.md (v2.5 CRA bullet)
CHANGELOG.md (v2.5 release-line entry)
scripts/check_doc_consistency.py (REQUIRED_DOCS list)
Verification:
grep -rn 'docs/cra_compliance_mapping' . # 0 stale references
python3 scripts/check_doc_consistency.py # OK
pytest -q # full suite green
Phase 3'.1 Track B first PR (Pivot 2026-04-19).
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
… (Phase 3'.1 B-2 + B-3)
Completes the four-document compliance-mapping suite established by
B-1. All three new files reuse the cra_annex_i.md template (header
with version + last-revised + standard reference, mandatory "compatible
with" disclaimer, companion-mappings cross-link, executive summary,
regulatory-context section, per-requirement coverage table, output
formats section, coverage gaps, roadmap, references).
- docs/compliance_mapping/fda_section_524b.md
Maps the four 21 USC §360n-2(b) statutory obligations and the
September 2023 FDA premarket cybersecurity guidance content
elements. Calls out the sponsor-side responsibilities (security
objectives, threat-model documents, QMS, labelling, postmarket
cybersecurity management plan).
- docs/compliance_mapping/iso_21434.md
Maps ISO/SAE 21434:2021 work products across clauses 8, 9, 10, 11,
13, and 15 (TARA). Distinguishes tool-friendly work products
(WP-08-01..04, WP-10-04..05, WP-13-02) from manufacturer-side
narratives.
- docs/compliance_mapping/un_r155.md
Maps §7.2 (CSMS) and §7.3 (vehicle type) requirements, plus a
per-threat guide covering the 15 most relevant Annex 5 threat
categories (manipulation, replay, malware insertion, network-design
vulnerabilities, etc.). Co-published with iso_21434.md per the
standard / regulation pairing.
Verification:
python3 scripts/check_doc_consistency.py # OK
pytest -q # full suite green
Phase 3'.1 Track B second + third commits on PR #10 (Pivot 2026-04-19).
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
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.
Summary
Phase 3'.1 Track B first PR. Sets up the directory structure for the four-document compliance-mapping suite (CRA Annex I / FDA Section 524B / ISO 21434 / UN R155) that ships through Phase 3'.1.
The existing
docs/cra_compliance_mapping.mdisgit mv'd intodocs/compliance_mapping/cra_annex_i.md(history preserved) and its header is rewritten to:scripts/check_doc_consistency.pyrule 3 — this is the documentary side).docs/compliance_mapping/fda_section_524b.md(Phase 3'.1 step B-2)docs/compliance_mapping/iso_21434.md(Phase 3'.1 step B-3)docs/compliance_mapping/un_r155.md(Phase 3'.1 step B-3)Why this is a separate PR
Track B is independent of Track A (Phase 2C+ detection work, PR #9): Plan
~/.claude/plans/twinkly-hugging-leaf.mdruns them in parallel. This PR has zero file overlap with PR #9 and zero dependency on it; both can merge in either order.References updated
README.mdandREADME.ko.md— Regulatory Alignment rowdocs/status.md— v2.5 CRA bulletCHANGELOG.md— v2.5 release-line entryscripts/check_doc_consistency.py—REQUIRED_DOCSlistTest plan
grep -rn 'docs/cra_compliance_mapping' .— 0 stale referencespython3 scripts/check_doc_consistency.py— OKpytest -q— full suite greenPlan reference
See
~/.claude/plans/twinkly-hugging-leaf.mdfor the broader Track A / Track B parallel plan and the Phase 3'.1 sub-step breakdown (B-1 through B-5).🤖 Generated with Claude Code