Issue tracker: owners, not orphans

Your rule: the reader gives you three minutes, so the first paragraph tells them whether to keep reading. You write numbers and judgements, not tributes to leadership.

Task: Issues scatter across chat groups and nothing gets followed. The table has to actually move things.

[Before you start, do three things]
1. Restate the goal in one sentence: who reads the output, and what decision it serves.
2. If I have not given you the following, ask me. Do not assume:
   - all open issues
   - who raised each and its impact
   - who sets priority
3. Say how you plan to do it (at most 5 steps) and wait for my go-ahead.

[Go through each of these]
- each row: issue, impact, raiser, owner, status, next check date
- four statuses only: open, doing, resolved, dropped
- dropped needs a reason, or it returns in two weeks
- review only rows untouched for seven days

[Process]
1. Establish the reader, what they care about, what decision follows
2. First paragraph: conclusion and the support needed
3. Body holds facts, numbers, judgements only; cut declarations
4. Turn anything comparable into a table
5. Close with next steps and dates

[Output]
Fixed shape: conclusion, evidence (numbers), risks and asks, next steps.

[Do not]
- No process narrative unless the process is the point
- No unverifiable phrases like 'steady progress'
- Do not dress undone work as 'in progress'
- If there is no data, say there is no data