Skip to main content
Percio’s issues are generated by an AI reviewing a browser flow. It’s accurate much of the time, but not always. The validation actions let you annotate each issue so your report reflects what your team actually agrees with.

​
The three states

Every issue has three actions in the UI: Confirmed. You agree this is a real issue. Use this when the issue matches a real user problem you recognize or plan to fix. False positive. The persona flagged something that isn’t actually a problem for your product. Maybe it misread the UI, maybe it applied a heuristic that doesn’t apply, maybe it hallucinated a detail. Dismissed. You’ve seen it, you don’t disagree, but you don’t plan to act on it. Could be “we know, it’s on the roadmap” or “not important right now.” Issues start unvalidated. Validating is optional but recommended — it keeps reports useful over time and gives you a filter when you come back to the report later.

​
Why validate

  • Filters noise. Future you (or a teammate) can focus on confirmed issues.
  • Tracks what’s been triaged. Dismissed and false-positive issues are no longer on your plate.
  • Calibrates your understanding of the persona. If a persona produces lots of false positives, it may need tuning (see Creating personas).

​
Validation is per issue

Each issue is validated on its own. Validation lives with the specific report — if you run the same scenario again (even with the same persona) and a similar issue comes back, you’ll validate it again in the new report.

​
Changing your mind

You can toggle the validation state at any time. Marked something false positive that turned out to be real? Flip it back.

​
Validation does not delete issues

Validation annotates — it doesn’t remove. All issues stay in the report regardless of their validation state so you can always see what Percio originally found.

​
What’s next