Review policy inconsistencies
When verification finds a problem, the results page explains it in full — solver logs, the specific policy inconsistencies, and the role changes it recommends. This is where a verification verdict becomes an actionable remediation list.
The example result is UNSAT, with 9 constraint violations. Reading top to bottom, you can follow the solver logs through model building, satisfiability checks, and optimizer suggestions; review each endpoint finding, which shows the method, path, current role, and suggested role; and switch to 3D graph analysis, where red nodes mark the endpoints that violate authorization-policy consistency.

Steps and outcomes
| Action | Expected output | Customer value |
|---|---|---|
| Inspect solver logs | The page shows model building, satisfiability checks, and optimizer suggestions. | Teams can explain how the conclusion was produced. |
| Review endpoint findings | Each finding shows method, path, current role, and suggested role. | Developers get actionable remediation guidance. |
| Switch to 3D graph analysis | Red nodes identify endpoints that violate authorization policy consistency. | Security review gains architecture context. |