A receipt must explain the weak part of the result
I think the failed check is the most useful line in a research receipt. A week later, a timestamped “completed” entry won’t tell me which conclusion depended on a source the agent could not read.
For example, Sam asks on Sunday night: “Compare pricing and support quality for five project management tools, with a summary by Monday.” Four pricing pages open; the fifth requires a login. The agent uses a cached third-party price for that vendor, and the receipt needs to make that substitution visible.
Keep the request and sources together
Preserve the original instruction so Sam can judge whether the result answered it. Link each vendor’s pricing page and the reviews used for support quality, recording when they were checked. A claim about support response time needs a dated transcript or other direct record; a reviewer’s impression cannot supply that measurement.
For the inaccessible page, name the failure and the cached source used instead. Mark the price as needing confirmation and keep it out of any claim about the cheapest vendor. Sam can still use the four current prices without mistaking the fifth for an equivalent check.
Record actions and approval decisions
Research from public pages may need no approval. State whether anything was sent, paid, booked or changed outside the draft, including any attempt that failed. If the task contacted support, show the exact question, recipient and approval before that contact.
For a held action, preserve the proposal, decision time and resulting account state. “Approved” alone does not show that the send succeeded; a retry belongs in the same timeline.
Link the result and the work left open
Link the comparison and its sources, keeping the fifth vendor’s current price as an open item before Sam makes a buying decision.
Record measured model usage and paid lookups beside the task when available, separating actual charges from estimates so Sam can track the cost of repeated runs.
Reject a success-only record
“Compared five tools; summary attached” hides the substitution that Sam most needs to inspect. My test is whether I can reconstruct the important decision without reopening the entire conversation.
OperatorNest’s receipts record requests, sources, failures, approvals and results. They cannot make a cached price current: check the flagged figure against the vendor before buying. The agent receipt definition describes the record, and approvals describe the stop before consequential actions.