At the December board meeting the chair calls the meeting to order and the secretary records that seven of nine directors are present, which makes a quorum. The board approves November’s circulated minutes by voice, and the approval becomes a numbered decision in the register; the minutes now keep the exact text the directors read. In February a director notices a misspelt name. The secretary starts a correction, which is a new revision of the minutes; she fixes the name, circulates it and the board approves it, after which the original minutes read amended but remain on record. Product decided that approval belongs to the decisions milestone; this journey records what the product already does.
The Formal Contract
The narrative above explains; the sections below are authoritative — the rules, scenarios and tests this document binds.
Goal
Have the board approve November’s circulated minutes at its December meeting, and fix a mistake found later without rewriting the record.
End-to-end policy: required: It crosses meetings, decisions and minutes approval, and the decisions end-to-end suite already drives it against the API; Product decided that approval waits for the decisions milestone, so the journey proves today’s behaviour.