# Evaluate task results

Test a repeatable workflow against its intended outcome and record what the evidence actually establishes.

Use this guide when deciding whether a workflow is ready to rely on or whether a change improved it. Choose a real task and check the outcome a person needs, including the important recovery step.

A list of available tools or a passing build is useful evidence, but it does not establish that an account, native permission, or complete user workflow works.

## Choose one assessable task

Write down the starting state, input, expected result, and completion check. For example:

| Part | Browser-read trial |
| --- | --- |
| Starting state | Indra installed, existing Vault selected, browser provider available. |
| Task | Open the chosen public page and read its main heading. |
| Expected result | The observed URL and heading match the requested page. |
| Completion check | Inspect the returned snapshot, then confirm session cleanup. |
| Recovery case | If a control becomes stale in an interactive task, observe again before acting. |

Follow [Use a browser](/docs/vision/browser-computer/browser-use) to execute the normal path. This table is a trial definition, not a claim that the trial has already passed on your computer.

For a connector task, choose a small read from the intended account. For a document task, inspect the saved output. For a handbook change, use the guide to attempt a representative task and record where the instructions are missing or ambiguous.

## Record the evidence you actually obtained

| Evidence | What it establishes | What still needs separate evidence |
| --- | --- | --- |
| Source inspection | The code or contract contains an implementation path. | That the released installation and real account work. |
| Controlled automated check | The specified behavior passes under those inputs. | Native permissions and provider acceptance outside that setup. |
| Screenshot | The visible state at that moment and size. | The full interaction and downstream result. |
| Executed navigation or tool call | The observed operation reached its reported state. | Unexercised branches and other environments. |
| Destination readback | The observed object, content, or version is present there. | Delivery to another client or account. |
| User feedback | That person's reported judgment. | A judgment from people who did not provide feedback. |

Keep examples, test data, and actual user results distinguishable. Report a rate or duration only when the observations and denominator support it.

## Exercise a meaningful failure branch

Choose a case that could change whether the task succeeds: no matching records, missing account access, pending work, stale controls, an interrupted response, or an unsaved output. Not every workflow needs every case.

Check that the recovery preserves the original goal and resource identity. A failed read should not silently switch accounts. A lost write response should lead to readback before another write. A valid empty read should not trigger repeated sign-in.

## Record a mismatch without changing the goal

Use a compact record:

```text
Workflow and handbook page:
Environment and installed version:
Starting state and input:
Expected result:
Observed result and evidence:
Recovery attempted:
Remaining gap:
```

When the product falls short, keep the intended experience and the observed defect separate. A deliberate change to the intended experience should be recorded as such. Do not rewrite the expectation merely to make the existing result pass.

## Decide what is ready

State the scope established by the trial: the account, platform, task, and outcome actually exercised. Identify any remaining gap that affects use.

For documentation, check task findability, instructions, expected results, recovery, and consistent rendered/Markdown content. Working links and a chapter count do not establish usable instructions. A documentation update can be complete without automatically changing the product.

Repeat checks only to resolve a concrete failure or remaining risk. Once the relevant evidence is sufficient, deliver the result and retain the record for the next change.
