Go To Top

Return to Risks and Open Decisions

The team should maintain an open issues register for unresolved risks, decisions, assumptions, and deferred work. The register may live in this section, in an appendix, in repository documentation, or in an issue tracker. The important requirement is that the team can find, review, and resolve open issues deliberately.

Each open issue should identify:

1. Issue identifier.
2. Issue title.
3. Description.
4. Affected handbook section, repository area, Node, script, tool, container, or acceptance criterion.
5. Current status.
6. Owner or responsible role.
7. Target resolution date or milestone, where applicable.
8. Related implementation decision record, risk, pull request, or Evidence item.
9. Resolution notes when closed.

The team should review open issues before accepting a baseline, tagging a release candidate, or preparing a demonstration. If an issue remains open, the team should decide whether it blocks the baseline, remains an accepted risk, or moves to a later phase.