How Locus checks task results

​

How it works

• Fixed requirements. Before it spends on data, Locus turns your goal into an acceptance contract: the deliverable, the count, the fields, and the criteria each result must meet. That contract stays fixed for the life of the task.
• Every value needs a source. Each delivered value must appear in a response from a call this task made, or in the inputs you supplied. Values without that support are withheld.
• Verified emails are really verified. An email counts as verified only when a verification call for that exact address returned a valid result. Other mailbox statuses are reported as the provider returned them.
• A separate check judges the result. A verification step judges each row and the whole result against your criteria. If it cannot run, those criteria are marked as not checked.
• Summaries aren’t proof. Values taken from a model-written research summary are labeled as such and cannot prove a specific fact on their own.

​

What you get back

​

Files

• results.csv for a table. You get results.json instead if you asked for JSON, and results.md as well if you asked for Markdown.
• answer.md for a question-style goal.
• evidence.json with the requirements, per-row checks and verdicts, answer citations, and every paid call the task made.
• Generated files the task produced from a tool response, up to 10 per task and 20 MB each.

​

Next steps