Evidence and decisions
What evidence do you need to investigate an AI agent’s action?
A workflow reports that a step is complete, but the client’s team cannot find the expected result. To understand the gap, you need to connect what was requested, what was authorised and what the systems actually confirmed.
This guide proposes an evidence record for investigating a mission. Each conclusion should have identifiable support, while missing information remains visible.
In brief
The question and the useful result.
- Question
- What can we establish about this action and its outcome, and what remains unknown?
- Useful result
- A record distinguishing the request, authorisation, decision, attempt, acknowledgement and confirmed result.
Evidence and decisions
Establish what each record can show
Before declaring a mission complete, give each piece of evidence a precise meaning.
| Record | What it can establish |
|---|---|
| Original request | The requested outcome and the scope involved. |
| Authorisation | The permitted action and its conditions. |
| Human decision | A person’s choice about an identified action, when required. |
| Execution attempt | The operation the system tried to perform. |
| Acknowledgement | Receipt or acceptance of the request, according to the response’s exact meaning. |
| Outcome confirmation | The result confirmed by the relevant system, within the observed scope. |
A decision allowing an action does not prove execution. The mission’s status should therefore point to the evidence supporting it, including the limits of that evidence.
Evidence and decisions
Example: an order accepted for processing
In this illustrative scenario, an agent requests the creation of an order in an ERP. The service accepts the request, but the workflow has received no confirmation that the order was created.
The team has the request, the authorisation and an acceptance acknowledgement. It can establish that the request was accepted for processing. It cannot yet conclude that the order was created or that it failed.
HTTP provides a specific example: 202 Accepted means a request has been accepted for processing, which is not yet complete. It does not guarantee eventual completion, as explained in RFC 9110, section 15.3.3.
The evidence record should therefore keep the outcome as unconfirmed, alongside the request reference and the information still needed. This example does not establish that an ERP integration is available in DUBSAR.
Evidence and decisions
Build a record the team can investigate
For each action under review, bring together evidence the team can connect:
- The mission identifier and the identifier of the action involved.
- The request and the version of the content or record examined.
- The applicable authorisation, its scope and the relevant rule.
- Any human decision, its reviewer and its date.
- The execution attempt, the responses received and their source.
- Available confirmations, contradictions and missing information.
Keep references that let the team consult the relevant material, together with its context. If a referenced source becomes inaccessible, make that limitation visible in the record.
Choose what to retain according to the questions the investigation needs to answer. Understanding a decision does not require copying every exchange. References alone may also be insufficient if the material they point to is no longer available.
Evidence and decisions
Review the facts without triggering another action
An investigation should let the team read events and inspect their supporting material without sending the original operation again. Clearly distinguish this review from any command that would retry the action.
Finish with a scoped conclusion: a confirmed result, an observed failure or an outcome that remains uncertain. State the source, time and scope of the observation. Confirmation of one operation does not establish that every step in the mission succeeded.
The team then has a basis for deciding what should happen next. The operations guide to resuming interrupted missions addresses that decision process.
Evidence and decisions
Frequently asked questions
Are our workflow tool’s logs enough?
Check which questions they answer. If they connect the request, the decisions and the confirmed outcome, reuse them. Add missing links rather than building a second collection without context.
Must we record every conversation with the model?
Define what the evidence record needs. A complete chat history does not replace an explicit link between the authorised action, its execution attempt and its result.
Is an uncertain outcome a failure?
No. It means the available evidence does not support a conclusion. Keeping that distinction avoids presenting an assumption as a fact.
Evidence and decisions
Where DUBSAR fits
DUBSAR is developing a foundation that connects mission state, authorisations, human decisions and execution evidence alongside existing tools. Selected workflows have been tested; end-to-end validation for B2B use is still underway. Pilots are not currently open.
Evidence and decisions