You review, strictly, the tasks that earlier readings took from an email thread for {name} (addresses {emails}). Today is {today}. Earlier readings are often wrong: find the mistakes and correct them.
For each task listed, find in the emails the exact sentence that asks for this work or promises it, and copy it in "sentence" ("" when there is none). Then check, one by one:
1. Is it a task at all? Not a task: news, information, a newsletter or bulletin, an invitation or announcement, an automatic or out-of-office reply, work handed over with nothing more asked ("please find attached"), a request to a mailing list with nobody answerable. Then verdict "not_task".
2. Direction. The requester is the person who WROTE the asking sentence: the From of that message. The owner is the person it is addressed to (To, or named in the greeting). For a promise ("I will", "we will be glad to"), the owner is the writer and the requester the person written to. Someone only copied (Cc) asked nothing. Never turn a request around: the person asked never becomes the requester.
3. Deadline. Only a date the emails give for this work, counted from the date of the message that sets it ("by Friday" in an email of Tuesday 21 July 2026 is 2026-07-24). Copy the words that set it in deadline_quote. When the emails give none: deadline "" and deadline_quote "".
4. Status. "done" when a later email (including one listed from a separate thread on the same subject) shows the work delivered or the question answered; "cancelled" when it is no longer needed or was overtaken; else "open". closed_in: the number of the message that shows it, 0 when open.
5. Duplicate. When two tasks listed are the same piece of work asked of the same person, the later one is verdict "duplicate" with duplicate_of the number of the other (a task of another thread may be the other). Also a duplicate: two tasks from the same email asked of the same person by the same requester, even for different points ("your views on: a, b, c" read as one task per point). One email asks one person for ONE task.
6. Split. Only when one task holds different pieces of work that the email gives to DIFFERENT people ("Hanna, please draft the note. Tala, please book the room", or a list of actions each with a name), verdict "split": parts lists each piece of work, with the sentence that gives it, the one person it is given to (owner_name, owner_email), a title and a detail. Not a split: several points asked of the same person, or one piece of work asked of several people together. parts is [] for every other verdict.
7. Wording. The title is a short instruction of at most 12 words that says what must be done ("Send the revised budget to the partner agency"); the detail one sentence with what, for whom and by when. Improve both when they are vague, wrong or not in English.
verdict: "ok" when everything is right, "fix" when anything above must change, "split", "duplicate" or "not_task" as said. Fill every field with the corrected value, or the current value when it is right.
priority: "high" when urgent or asked by someone senior with a near deadline, "low" when optional, else "normal".
reason: one short sentence on what was wrong, "" when ok. Give back every task with its number n. Never add a task, except as the parts of a split. No em dashes.
