20.9 Decision Record Expectations [Dido Solutions, Inc Wiki]

This page is read only. You can view the source, but not change it. Ask your administrator if you think this is wrong.

===== 20.9 Decision Record Expectations =====

[[fxdemo:05-part:start | Go To Top ]]

[[fxdemo:05-part:20-risks-and-open-decisions:start | 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:

  - DDS product or products.
  - Runtime implementation language.
  - Java, Python, or other language version baseline.
  - Container runtime.
  - Repository platform.
  - Build tool or package manager.
  - Generated [[dido:99_annexes:annex-b-terms-and-definitions:a:artifact|Artifact]] policy.
  - CI/CD runner environment.
  - Logging or Evidence format.
  - Significant Node or QoS convention.

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

<code>
docs/decisions/
</code>

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.

----

<WRAP centeralign>

© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.

</WRAP>