Go To Top

Return to Risks and Open Decisions

The team should use implementation decision records for decisions that affect the shared baseline. A decision record should capture the decision, context, alternatives considered, selected option, consequences, and any remaining risks.

A decision record should exist when the team decides:

1. DDS product or products.
2. Runtime implementation language.
3. Java, Python, or other language version baseline.
4. Container runtime.
5. Repository platform.
6. Build tool or package manager.
7. Generated Artifact policy.
8. CI/CD runner environment.
9. Logging or Evidence format.
10. Significant Node or QoS convention.

Decision records should live in a controlled repository location, such as:

docs/decisions/

The handbook should reference decision records where they define baseline assumptions. The decision records should not replace the handbook. They explain why the team made a choice. The handbook explains how the team applies the choice.