Check the result

Review evidence that matches the task. A clear answer, a successful tool call, and a finished outcome are different things.

Ask for observable evidence

Result	What to inspect
Research brief	Source links, dates, and support for the conclusion
Data analysis	Input range, units, calculation, and missing values
File change	The actual changed file and a comparison
Code fix	The relevant behavior check and any untested boundary
Message	Recipient, final content, and delivery result
Scheduled task	Timing, next intended run, run history, and output
Project	Deliverables against exit criteria

Keep partial results honest

Ask Gideon to separate completed work, unverified work, and blockers. A connection error should appear as missing evidence, not a successful check. A queued action has not yet produced an outcome.

When the result is wrong

Point to the exact discrepancy and the source that establishes it. Ask for a correction scoped to the error. If the action affected an external system, inspect the current state before repeating it or trying to undo it.