What are the 14 verdicts in Nexus Studio?

Nexus Studio is an on-prem QA Operating System that classifies every run into one of 14 forensic verdicts instead of pass or fail, so a real defect is told apart from a slow network, a bot challenge or a crashed browser. The table shows, for each verdict, what it means, whether it opens a Jira ticket and whether its failure video is kept.

Verdict	Type	What it means	Jira ticket?	Video?
SECURE	Passed	Passed on its own: no retry, no repaired selector.	No	No
CHAOS_RESILIENT	Passed	Passed while a fault was injected, so the app held.	No	No
AUTO_RECOVER	Passed, with a reservation	Passed, but a selector had to be repaired.	No	No
FLAKY	Passed, with a reservation	Failed, then a retry passed it; nothing was fixed.	No	No
PERFORMANCE_DEGRADED	Passed, with a reservation	Assertions passed, the page was too slow.	No	No
A11Y_VIOLATION	Passed, with a reservation	Assertions passed, accessibility did not.	No	No
SECURITY_VIOLATION	Passed, with a reservation	Assertions passed, a security check did not.	No	No
BREACHED	Application broke	A real finding: an assertion failed and nothing in the environment explains it.	Yes	Yes
BREACHED_FLAKY	Application broke	Failed, and the failure itself is inconsistent.	Yes	Yes
CHAOS_BREACHED	Application broke	Broke under injected chaos.	Yes	Yes
TIMEOUT	Environment	Never answered in time, which is not proof it is broken.	Yes	Optional, off by default
UNREACHABLE	Environment	The host could not be reached at all.	No	No
BLOCKED	Environment	The site defended itself with a 403, a 429 or a bot challenge.	No	Optional, off by default
CRASHED	Harness	The browser or the process died.	No	No

Jira and Azure Boards open one issue per test, and only when the integration is switched on. Video follows the setting Keep failure video for: BREACHED, BREACHED_FLAKY and CHAOS_BREACHED by default. How the 14 verdicts are decided, and the files each one leaves.