---
title: "A design validator for a banking app"
url: /cases/validator-for-a-banking-app
description: "A deterministic validator that finds whether a UI bug comes from the implementation, an inconsistent design file or the analysis. It reports and routes; it never blocks."
---

## §0 · problem

# A design validator for a banking app

**Level 4 · 2026 · for a banking software vendor**

Many small UI bugs had three possible origins: the implementation, an inconsistent design file, or the analysis. Nobody could tell which one without hours of comparison.

## §1 · built

### What was built

A design validator that finds the origin. It is a deterministic pipeline. Same input, same findings file, byte for byte [claim case4-deterministic: Own project; source: author's project, internal; confirmed] No language model runs inside the rule engine. Model work lives in skills, where an agent writes claims and code checks them.

## §2 · taught

### What it taught

- The validator reports and never changes code. Another agent changes the code. That separation is the safety property.
- A missing finding is better than a false one.
- A single quality score was rejected. A score can read perfect while blocking findings sit under a baseline.
- A blocking gate was rejected. False blockers burn the agent's limited fix attempts. The validator reports and routes.
- The design file is evidence, not authority. When file and library disagree, the tool reports both values and merges nothing.

## §3 · open

### What is still open

About 13% signal at first contact with real files; precision and recall of 1.0 on the tuning corpus only [claim case4-signal: Own project. The 1.0 holds on the tuning corpus only; source: author's project, internal; confirmed]

Review chose the agent-with-validator arm in every pair that produced a pull request (6 ticket pairs) [claim case4-ab: One A/B test, 6 ticket pairs. Not a clean A/B: the arms could see each other's commit subjects; source: author's project, internal; confirmed]

6 design-tool API calls a month on a view-only seat; retry-after about 4.4 days [claim case4-quota: Own experience; the tool moved to an offline file bridge; source: author's project, internal; confirmed]
