The working A prototype: use its controls to test the build question.
Show what happened to messy data before anyone relies on it.
RN conceived the question, structured the evidence boundaries, designed the experience, implemented the prototype and documented its limits.
This independent prototype demonstrates an approach; it is not a deployed client system, professional advice or proof of real-world outcomes.
Work through the controls with a situation of your own rather than the sample values. The tool responds to what you put in, so the useful output comes from real input, and everything is processed in your browser as you go. Any sample content you find already loaded is there to show the shape of a filled-in state, and you can clear it and start again at any point.
The build overview sets out the question, the purpose, the role and the evidence status in one place, and the public record behind it states what changed, what another person can reuse and what supports the system. If you want to judge how far this build should be trusted, the record is the page to read, not this one.
BUILD 026-A
Messy Data Trust X-Ray
Show what happened to messy data before anyone relies on it.
REVIEW REQUIRED
0 blockers · 1 duplicate groups
Source records
usd
USD
usd
Normalized + traced
Maya Chen
maya@example.org
1250 USD
Source: Synthetic intake form A
4 reversible transformations
- name: “ maya chen ” → “Maya Chen”
name/space-and-case / 026.2.0 - email: “MAYA@EXAMPLE.ORG ” → “maya@example.org”
email/trim-lowercase / 026.2.0 - amount: “$1,250.00” → “1250”
number/strict-currency-parse / 026.2.0 - unit: “usd” → “USD”
unit/trim-uppercase / 026.2.0
Maya Chen
maya@example.org
1250 USD
Source: Synthetic partner CSV B
0 reversible transformations
José Rivera
jose@example.org
980.5 USD
Source: Synthetic intake form A
3 reversible transformations
- email: “JOSE@EXAMPLE.ORG” → “jose@example.org”
email/trim-lowercase / 026.2.0 - amount: “980.50” → “980.5”
number/strict-currency-parse / 026.2.0 - unit: “usd” → “USD”
unit/trim-uppercase / 026.2.0
Duplicate review records
- DUP-01: SRC-101 + SRC-102 · review open · source records remain separate
Review boundary
- 1 duplicate group remain in review; no records were merged or removed.
Boundary: title, job, B-Web sentence, and lineage are frozen canon. The fixture, rules, statuses, and thresholds are derived. A normalized email is only a candidate signal. Runs client-locally; enter no real or confidential data.