17.10 Relationship to Issues and Decision Records

Go To Top

Return to Git and Review Workflow

Git review should connect implementation changes to issues, risks, acceptance criteria, and implementation decision records where those Artifacts exist. This connection helps the team explain why the Baseline changed.

A change should reference an issue, decision record, risk, or acceptance criterion when it:

1. Changes tool requirements.
2. Changes Repository layout.
3. Changes IDL definitions.
4. Changes generated Artifact policy.
5. Changes Node lifecycle behavior.
6. Changes Topic names, types, publishers, or subscribers.
7. Changes QoS expectations.
8. Changes scripts or exit-code behavior.
9. Changes container build or runtime assumptions.
10. Changes logging, observability, or Evidence collection.
11. Changes acceptance criteria.
12. Resolves an open risk or decision.

The team should not create excessive process overhead for small editorial corrections or obvious fixes. However, any change that alters shared Baseline behavior should leave enough review trail for future team members to understand the decision.