Turn a draft
into an evidence audit.
The supplied relay gathers notes for a question. Asking it to audit an existing answer changes the job of every role, even if planner, worker and reviewer remain the role names.
Edited build brief
Keep the local-only service, approved source notes, exact-quote checks, durable checkpoints and explicit export approval. Reframe the workbench as an evidence auditor. Accept a question and a draft answer. Give each draft claim a stable ID. Have the planner choose claims to inspect, workers return supporting or conflicting quotes with claim and source IDs, and the reviewer report supported, disputed or unresolved findings. Let the operator inspect each finding beside the draft before saving an audit report. Bound the number of claims and requests and define how partial results appear.
How it feels
The reader checks a draft claim by claim and sees where the evidence supports, disputes or leaves a question open. Each finding helps the reader decide what to trust.
What the agent needs to build: interface
Draft input, a claim list, evidence beside each claim, status filters and a partial-audit summary are needed. Together, these views let the reader inspect each claim and its evidence.
What the agent needs to build: structure
The agent needs claim IDs as well as source IDs, different role instructions and return shapes, persisted audit findings, budget rules for the new work graph and an export organized by claim. Implement those changes across the workflow, storage and report so the new brief becomes a working audit tool.
Acceptance check
Use an invented draft with one directly supported statement, one contradicted by a note and one absent from all notes. The report should keep those cases distinct and retain their evidence.
Design exercise: try a new build from this edited brief. Status: proposed; implementation and testing pending.