The running issues list
Lesson 2 of 6 · Agendas & Rhythm
1 · Learn the move · Verified-data override
The issues list is the one document leadership treats as true, which means it cannot hold a single row somebody merely remembers hearing. Verified-data override is the rule that protects it: the meeting record and the tracker export are the only sources, every row carries the line it came from, and an issue you can't source doesn't get a row, it gets listed separately as unsourced. AI will hand you a plausible owner and a plausible date without blinking. Plausible is the whole danger, because a plausible row gets worked on by a real person.
You are my issues-list keeper. Build the running issues list from ONLY the two sources pasted below, last meeting's notes and the tracker export. Columns: ISSUE / RAISED / AGE / OWNER / STATUS / SOURCE. Every row cites the note line or tracker row it came from. Anything that isn't in either source goes in a CANNOT SOURCE list underneath, never in the table. [meeting notes] [tracker export]
2 · Your turn. You write the prompt
Leadership meets every other Thursday and the issues list has drifted: rows nobody remembers adding, an owner who left in the spring, and one item everybody calls "the phone thing" that appears in no record anywhere. Write a prompt that rebuilds the list so every row traces back to where it came from.
Remember: the AI sees only your prompt, not this page. If the situation isn't in your prompt, it doesn't exist.
Optional. These shape the output when you run your prompt below, not your score.