20.10 Risk Review and Baseline Acceptance [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.10 Risk Review and Baseline Acceptance =====

[[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 review risks and open decisions before it accepts a Phase 0 baseline. Baseline acceptance should not require every risk to be eliminated, but it should require every known risk to be visible, classified, and dispositioned.

A risk or open decision may be:

  - Resolved.
  - Accepted for Phase 0.
  - Deferred to a later phase.
  - Converted into an implementation decision record.
  - Converted into an issue.
  - Treated as a blocker.
  - Removed because it no longer applies.

The team should not accept a baseline while a hidden or undocumented issue affects repository structure, required tooling, DDS/IDL generation, generated [[dido:99_annexes:annex-b-terms-and-definitions:a:artifact|Artifacts]], [[dido:99_annexes:annex-b-terms-and-definitions:n:node|Node]] execution, [[dido:99_annexes:annex-b-terms-and-definitions:c:control_plane|Control Plane]] behavior, container operation, logging, [[dido:99_annexes:annex-b-terms-and-definitions:e:evidence|Evidence]], or acceptance criteria.

The practical rule is simple: the Phase 0 baseline may contain limitations, but those limitations should be known, recorded, and explainable.

----

<WRAP centeralign>

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

</WRAP>