1. Purpose
Reviews, gates, bring-up and production all generate actions and issues. If they are scattered across meeting notes and chat threads, important ones are lost and others are worked twice. This procedure keeps every action and issue in one log, with one owner, a date and a closure rule, so that the programme always knows what is open and what blocks its next commitment.
It also makes closure mean something. An item closes when its closure evidence is accepted by the person who raised it, so that a gate can rely on the closed status it sees.
How actions and issues raised at reviews, gates and in daily work are logged, owned, worked and closed. An issue is a problem that has happened; an action is a task someone has agreed to do. Each has one owner, a due date and a closure rule, and closure needs evidence, not just a status change.
10 more sections for registered members.