meeting-minuteslisted

# Meeting minutes Minutes that survive contact with the people who were in the room. Most write-ups fail the same three ways: they file an action as a decision, they call a settled limitation a risk, and they quietly replace a garbled transcription with a product name that was never said. Each has its own gate below. --- ## Step 0: establish the setting Ask once, at the first run, and record the answers in this file's conventions section so they are never asked twice. 1. **Who is in the room, and on which side?** A recurring meeting usually has two or more parties: a client and a supplier, two departments, a steering group. Name them, and list the participants under each. 2. **Who has authority to decide?** Name the person or party. This single answer drives the decision gate below, and getting it wrong turns a supplier's proposal into a client decision. 3. **What is the naming convention for people?** For example `FirstName L.` everywhere, with full names in the attendee block only. Pick one and it applies in prose and in tables alike. 4. **Language, time zone, meeting cadence, filename convention.** 5. **Does the user want a private briefing alongside the minutes?** Some readers want a second, unshared document holding the analysis and the sensitive material. If yes, ask where it goes and in what language. 6. **Is the user a participant?** If so, they are named like everyone else in the minutes. See the naming rule below, which exis