Repository navigation
fix audit findings chm - #834
Merged
Merged
Conversation
masc2023
requested review from
PandaeDo,
RolandJentschETAS,
aschemmel-tech and
pahmann
as code owners
October 17, 2026 05:10
10 of 11 tasks
|
The created documentation from the pull request is available at: docu-html |
This was referenced Oct 17, 2026
PandaeDo
approved these changes
Oct 19, 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
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.
Addresses the remaining change-management clarifications from #567:
Define what the Change Management Plan identifies and when change management applies, reusing existing work-product and configuration-item identification.
Clarify the request date, reason, description and starting release version.
Extend impact-analysis prompts to cover interfaces, connected elements, affected versus modified work products, distributed responsibilities, and implementation/verification timing.
Record who implements an accepted change and when it is due, considering the interfaces involved.
Align existing checklist items and traceability with ISO 26262-8:2018, 8.4.1.2, 8.4.1.3, 8.4.2.2, 8.4.3.1 and 8.4.4.2.
No changes to workflow behavior, responsibilities or approval gates. Workflow files only receive updated references to revised guidance.
Updates to SCORE’s Change Management Plan and shared GitHub issue forms are outside this PR’s scope.
Validation
Documentation build passed: bazel run //:docs
Whitespace checks passed: git diff --check