Guides
Review results
Preview how documentation can explain summaries, evidence, and timelines.
Open a completed run from Findings or from the journey that produced it.
The summary shows the verified outcome and the findings connected to the run. Start here when you need a quick answer.
Questions to answer
- Did the product reach the expected state?
- Which action caused the problem?
- Is the evidence complete enough to make a decision?
- Does the finding describe something the product team can address?
Use the verified product state as the result. The agent's own message is context, not proof.
Treat the result as unresolved. Run the journey again after the connection or verification problem is fixed.
Share the finding and the evidence needed to reproduce it. Leave credentials and unrelated customer data out of the report.