# The new design

> How to try the redesigned Keryn Web, what changes on each of its six screens, and the one status colour system it uses.

Source: https://keryn.dev/docs/guides/new-design/

> **Caution: Optional and off by default**
> The new design is a second look for Keryn Web that you can switch on and off. The current design stays the default until every screen of the new one matches it feature for feature and passes the accessibility checks.

## Try it

Open **Settings** in [Keryn Web](https://keryn.app) and turn on **Try the new design**. Turn it off the same way. To look at it for one page without changing the setting, add `?ui=exploration03` to the address (`?ui=classic` shows the current design); that choice is never stored. The theme choice applies in the new design too, so it has a light version as well as a dark one. Your scans, results and decisions are the same in both designs: only how they are laid out changes.

## What changes

The left rail becomes six places in a fixed order: **Start, Scan, Decision, Evidence, Trust graph, AI-BOM**. On a phone the rail is a bar at the bottom. Each screen leads with one sentence. The pictures below are of the new design scanning [the help-desk sample](https://keryn.dev/samples/helpdesk.zip) and [the trip-planner sample](https://keryn.dev/samples/trip-planner.zip); the pictures below show the dark theme.

### Start: "See where input becomes action."

The place to give Keryn a repository, folder or file, with a faint path from code to agent to tool behind it. Next to it, the lines that say where the scan runs: in your browser, local files never uploaded, rules run locally, and that results are saved only in this browser.

![The Start screen of the new design: the sentence "See where input becomes action.", a faint path from code to agent to tool behind the input, a line saying where the scan runs, and the rail on the left.](https://keryn.dev/screens/x03-start-1280-dark.webp)

*Start, in the new design. Taken from keryn web 0.5.2 at monorepo commit 561fef67.*

### Scan: "Evidence is taking shape."

The stages of the scan, each marked done, running, waiting or skipped, and the findings found so far. Each early finding carries its state (a raw match, provisional or final), and the list does not reorder as the scan goes on.

![The Scan screen of the new design while the help-desk repository is being scanned: the sentence "Evidence is taking shape.", a timeline of the scan stages with the finished ones checked, and the findings found so far.](https://keryn.dev/screens/x03-scan-1280-dark.webp)

*Scan, in the new design. Taken from keryn web 0.5.2 at monorepo commit 561fef67.*

### Decision

The status as one large object with its word, HOLD here, the reason in one sentence, the number of findings, the trust score and the risk score, and what would make it Go. There is an **Inspect blocker** action and a count of accepted risks.

![The Decision screen of the new design after a scan of the help-desk repository: the status as a large object with its text label, the reason in one sentence, the findings, trust and risk numbers, and what would make it Go.](https://keryn.dev/screens/x03-decision-1280-dark.webp)

*Decision, in the new design. Taken from keryn web 0.5.2 at monorepo commit 561fef67.*

### Evidence

The finding as a sentence, its severity, status and proof level (pattern, path, confirmed), the code at the line, and why it matters, the trace, the fix and the owner. Previous and Next move through the findings.

![The Evidence screen of the new design for the blocking finding: the finding written as a sentence, its proof level, the code at the commit on the left, and why it matters, the trace, the fix and the owner on the right, with Accept risk and Verify fix.](https://keryn.dev/screens/x03-evidence-1280-dark.webp)

*Evidence, in the new design. Taken from keryn web 0.5.2 at monorepo commit 561fef67.*

### Trust graph: "One path crosses the boundary."

Three layers (external input, agent runtime, tenant data), the one path drawn in amber with a marker where it crosses a boundary, and the path card docked at the bottom with a link to the full map. When there is no such path, the sentence says so.

![The Trust graph screen of the new design: three planes (external input, agent runtime, tenant data) with one path and the place where it crosses a boundary marked, and the path card docked at the bottom.](https://keryn.dev/screens/x03-trust-1280-dark.webp)

*Trust graph, in the new design, for the trip-planner sample. Taken from keryn web 0.5.2 at monorepo commit 561fef67.*

### AI-BOM: "Know what your agent depends on."

Models, SDKs, MCP servers and other tools in groups, each with a Passed or Review mark and where it was found (source, lockfile, config or endpoint), and a ring that counts the policy checks that pass.

![The AI-BOM screen of the new design for the help-desk scan: the sentence "Know what your agent depends on.", the models, SDKs, MCP servers and other tools grouped, each with a Passed mark and where it was found (source, lockfile, config or endpoint), and a ring showing 5 of 5 policy checks passing.](https://keryn.dev/screens/x03-aibom-1280-dark.webp)

*AI-BOM, in the new design, for the trip-planner sample. Taken from keryn web 0.5.2 at monorepo commit 561fef67.*

## One status colour system

The same four states look the same on every screen, and each one is also written out in words, so colour is never the only signal.

| State | Colour | Label |
|---|---|---|
| Hold or blocking | Amber | Hold, Blocking |
| Go or passed | Mint | Go, Passed |
| Needs review | Violet outline | Review |
| Unknown | Grey | Unknown |

Severity and where a finding came from stay neutral: colour is reserved for what you should do about it.

## For designers and engineers

The new design adds tokens to the existing design system and does not replace it: the design system lists them next to the current ones. Every screen works at 1363 and 390 pixels wide and is checked for contrast, keyboard use and screen readers.
