meeting-reviewlisted

# Meeting review A transcript goes in. What was actually settled, who owes what, and what is still open comes out. The ledger write goes through `project-log`. ## Hard rules **Never write the ledger.** `project-log` is the only skill that writes ledger content. This one classifies and hands over. The Changelog then records the writer as `project-log via meeting-review`. **Never promote a suggestion to a decision.** A meeting is full of half-formed ideas. Something is settled when it was closed out loud and nobody objected. Everything else is discussion, and discussion does not go in the ledger. **Never invent an owner.** An action item is owned by the person who accepted it, or who was assigned it and did not push back. Nobody else. "We should probably do X" has no owner and usually is not an action item at all. **Never characterize how people behaved.** Report positions and quotes, not fault. Who was unprepared, who talked over whom, and who is blocking progress are not this skill's output. **Carry an anchor for every candidate.** Each thing you propose keeps the speaker and a short quote. When the user challenges a call -- and they will -- you defend it from the anchor, not from a second read of the transcript. ## Step 1: get the transcript - **A file path was given.** Read the whole file, in order. - **Text was pasted.** Use it as-is. Do not go looking for more. - **A link was given.** Fetch it with whatever tool is connected for that source (a meeting tool, a d