YOUR OWN AI WORKSHOP
Change the purpose.
Build a triage tool.
By Alvin
Now give the editor two piles: ready to use and needing follow-up. This sorting of work is called triage. The new function puts confirmed notes in ready and the rest in needs_review, keeping the source label and quotation in both.
Complete brief / keep the acceptance checks
Write Python 3 code containing exactly one function build_report(notes). Return only code, with no imports, markdown, file access, network access or top-level calls. notes is a list of dictionaries with string keys id, text and boolean confirmed. Build an editorial triage tool: help an editor see what is ready and what needs follow-up. Return {"ready": [...], "needs_review": [...]}. Each entry must be {"source_id": note id, "quote": note text}. Put confirmed true notes in ready and confirmed false notes in needs_review. Sort each group by source_id. Preserve every text character exactly and keep repeated IDs as separate entries. Accept an empty list. Do not mutate the input. Use only ordinary builtins, list/dict operations and loops. No prose or example calls.
What changes in the build
The changed purpose creates two queues. A complete app would gain two sections, a confirmation control, persistent status and a way to revisit unresolved notes. This experiment checks the transformation behind that interface.
Both groups retain source identity, exact quotes, sorted order and duplicates. A change of output shape carries these requirements into each branch.