Go To Top

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:

1. Resolved.
2. Accepted for Phase 0.
3. Deferred to a later phase.
4. Converted into an implementation decision record.
5. Converted into an issue.
6. Treated as a blocker.
7. 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 Artifacts, Node execution, Control Plane behavior, container operation, logging, 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.