[FuSa] Add ChangeTrigger and ChangeImpactAnalysis for safety change analysis - #1442
Draft
devashridatta-dotcom wants to merge 1 commit into
Draft
Conversation
devashridatta-dotcom
force-pushed
the
agent/fusa-reassessment-source
branch
from
August 28, 2026 19:17
18744d4 to
d8fd642
Compare
devashridatta-dotcom
changed the title
devashridatta-dotcom
force-pushed
the
agent/fusa-reassessment-source
branch
from
August 28, 2026 20:01
d8fd642 to
d60c650
Compare
devashridatta-dotcom
changed the title
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
2 participants
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.
Updates the FunctionalSafety profile with the change impact pattern discussed in the SPDX FuSa SIG on August 28, 2026.
This revision proposes:
ChangeTrigger: a FunctionalSafety artifact representing the source, reason, event, report, or external record that initiates change impact analysis. It can carry inherited Core externalRef / externalIdentifier values for CVEs, field incidents, lab findings, customer reports, regulatory events, configuration changes, environmental changes, business decisions, or other external records.
ChangeImpactAnalysis: a FunctionalSafety artifact representing the documented impact analysis of a change trigger against safety-relevant SPDX elements. It can identify impacted, added, changed, or invalidated elements, reference the impact-analysis process, communicate analysis status, communicate impact level, identify approval, and carry rationale.
investigatedBy: an additive Core RelationshipType so a ChangeTrigger can be linked to the ChangeImpactAnalysis that investigates it.
FunctionalSafety guidance text describing how ChangeTrigger, ChangeImpactAnalysis, RequirementVerification, EvaluationResult, EvidenceRelationship, and Core/Bundle work together for SRAP-style communication.
RequirementVerification remains focused on how a verification or assessment is performed. The trigger is upstream of verification and is connected to the impact analysis instead.