Verification work fails in the interface more often than in the analysis. A green badge on a check that found no relevant passage, a graph that hides half the links without saying so, an evidence page that makes the reviewer lose the finding they were reading: each one turns careful work into a misleading result. On 29 October 2026 we adopted a set of interface principles that now apply to every AnKre screen.
The finding is the unit of work
The claim and the finding are what users work on; the graph and the documents serve them. A finding view holds the content, its status, its evidence and origin, the collection date and the human decision, and says plainly when a proposal comes from AI and still awaits a decision.
Navigation by business object
Users move between the objects of their work: the investigation, its sources, the analysis, the relationships, the review and the deliverables. Agents are not navigation items; they are reached from the work they do. A breadcrumb always says where you are, and filters, selection and the browser's back button keep their state.
Statuses on separate axes
A single badge cannot say four things at once. AnKre keeps them apart:
- Processing: pending, running, done, partial or failed.
- Verification: supported, contradicted, unresolved or not evaluated.
- Human review: to review, more requested or validated.
- Importance: a business classification, with its justification.
A finding can be unresolved and its review validated; a generation can succeed and be wrong. 'No passage found' and 'analysis impossible' are distinct states and never shown as success, and a worrying result never shares a colour with a technical error.
Evidence one click away, without losing the finding
A citation opens the document at the right page and passage, beside the finding rather than instead of it, with its versions and links back to every finding that uses it. Going from a conclusion to its evidence, and from the evidence back to the conclusions that depend on it, is the journey the interface is built around.
A graph you control
- Expansion is controlled: choose the type, the period and the state of the links, and see what was added and what is filtered out.
- Documented, suggested and contested links look different.
- A hidden link is not an absent link, and the screen says so.
- Every graph has a table alternative.
Requests and visibility
A request for more information is created from the finding it concerns, with an owner, a reviewer and the expected result, and the answer comes back to that finding. Who will see a comment or an export is stated at the moment of the action, not hidden behind a padlock icon.
Accessible by default
Every screen targets WCAG 2.2 level AA on desktop and mobile: text contrast of at least 4.5:1 and 3:1 for essential graphics, targets of at least 24 by 24 CSS pixels, citations reachable without hover and no action that requires double-click or drag only.