Run Evidence

Every Autonomy run produces a reviewable evidence workspace. It is designed for the moment after a run finishes, when a reviewer needs to decide whether the product is safe to merge, whether a failure is real, and who should act on it.

Summary first

Start with the run summary. It shows the plan, target environment, status, failure point, and the most useful artifact links. Passing runs should be quick to scan. Failed runs should make the next action obvious.

Timeline and replay

The timeline shows each step Autonomy attempted and what it observed. For browser and mobile runs, screenshots and replay help confirm whether the issue is user-visible. For API, inbox, and SMS checks, the timeline records the request, response, message, or wait condition that proved the result.

Cross-channel artifacts

Autonomy can attach multiple evidence types to the same journey:

• Browser replay and screenshots.
• Mobile screenshots and device-state snapshots.
• API request and response assertions.
• Network waterfall and HAR export.
• Email inbox and OTP messages.
• SMS messages and verification codes.
• Generated checks, warnings, and repro notes.

Failure review

For a failed run, open the failed check, compare it with the raw artifact, then use the linked replay, screenshot, request, or message to confirm the behavior. If the failure belongs in a pull request, Autonomy’s PR comment should point to the same evidence rather than creating a second summary.

Access and retention

Evidence is scoped to the organization that owns the run. Retention, sharing, and environment access depend on your organization settings and deployment mode.