Evidence and findings
Learn how Invokeable supports results with evidence and turns repeatable failures into actionable findings.
Evidence is the record used to decide what happened. A finding is a product problem supported by one or more assessment results.
Evidence
Evidence can include:
- The actions the agent selected
- Sanitized request and response facts
- Product state before and after an action
- Independent verification results
- Timing and retry observations
- Cleanup or restoration checks
- The agent's final claim, clearly separated from verified state
- Limitations and excluded observations
Evidence is not the same as a raw log. Invokeable excludes secrets and applies workspace access rules before showing or exporting evidence.
Missing or conflicting evidence
Invokeable does not infer success from silence. If important evidence is missing, expired, restricted, or contradictory, the relevant check remains inconclusive and the run cannot be counted as a verified pass.
Findings
A finding groups a reliability or safety problem into a record the product team can act on. It can show:
- Severity and lifecycle status
- The affected journey and test frequency
- What was expected and what was observed
- Customer impact
- Supporting runs and evidence
- A recommended fix
- Fix execution and verification state
Severity
| Severity | Meaning |
|---|---|
| Informational | An improvement or coverage observation without demonstrated harm |
| Low | A minor consistency, clarity, compatibility, or efficiency problem |
| Medium | A meaningful but recoverable failure or avoidable need for human help |
| High | A core journey completed incorrectly, created bad state, claimed false success, or failed to recover safely |
| Critical | Unauthorized, destructive, privacy-sensitive, financially harmful, broadly duplicated, or otherwise severe unsafe behavior |
Finding lifecycle
A finding may move through open, investigating, needs evidence, confirmed, remediating, verifying, resolved, intentional, or merged states. A resolved finding can reopen if the problem recurs.
Resolved means a later assessment verified the expected behavior. Closing a ticket or deploying a code change is not enough on its own.
See Review results and Fix and verify.