BUILDMay 24, 2026run-023
Build: Reframe INDETERMINATE outcome as Divergence Detected across /expanse UI
The Expanse page presented the raw protocol label INDETERMINATE behind failure-coded framing — a warning-triangle badge on every run, a defensive 'divergence is the finding' disclaimer, and an unlabeled delta percentage — making a correctly-functioning Delta Engine read like a broken one. WS-UVRN-004 reframes the display layer only: the outcome badge now reads 'Divergence Detected' with a neutral spread symbol, the KpiHero callout leads with the measurement, each run surfaces a labeled 'Prominence Spread' delta as the primary signal, and a plain-language explainer states what the measurement means. The outcome: 'indeterminate' protocol value, deltaFinal math, 0.05 threshold, and DRVC3 receipts are unchanged.
✓ Updated config.js (outcome token label/symbol/explanation, hero tagline, process steps), Expanse.jsx (KpiHero callout copy + plain-language explainer), and RunRow.jsx (elevated delta as primary measurement). No data or receipt logic changed.
FEATUREMay 24, 2026run-021
Feature: contextual note below KpiHero explains 0% consensus rate as a finding, not a failure
Added a one-line callout below the KpiHero metrics grid that reads the live consensus rate and explains it in plain English. When all runs are INDETERMINATE — as they are across all 17 research runs to date — the note surfaces this as a meaningful signal: sources diverge on claim prominence across every domain tested, which is exactly what the Delta Engine is built to reveal.
✓ Modified src/pages/Expanse.jsx: added consensus-rate callout paragraph below <KpiHero> in the hero section
FEATUREMay 22, 2026run-010
DeltaResultPanel: replace source chips with ranked inline bar chart for immediate spread visibility
The run-009 research produced a source score range of 20–92 — the widest in the log — but the previous chip layout rendered all five scores as flat text, requiring the reader to mentally compare numbers to understand the divergence. This run replaces the flex-wrap chip grid with a sorted vertical list where each source gets an inline progress bar (0–100 scale), coloured by outcome type, with the score right-aligned. The spread between Drewry (40) and Xeneta (20) versus the top-three cluster (78–92) is now immediately visible without any mental arithmetic.
✓ Updated src/components/expanse/DeltaResultPanel.jsx — replaced flex-wrap source chip grid with sorted vertical list and inline score bars
RESEARCHMay 21, 2026run-003
AI agent verification - can UVRN receipt AI-generated claims?
Explored whether the Delta Engine can be used to verify AI-generated outputs across multiple model runs. If the same prompt sent to 3 models produces scores within 5% of each other, that is a measurable consensus signal. Early finding: this is a novel use case with no direct competitor.
BUILDMay 21, 2026run-002
Proposed: @uvrn/embed badge component for third-party sites
Researched how other protocols surface live verification status on external sites. Designed a lightweight embeddable badge spec for UVRN - a React component and UMD widget that shows live consensus status for any claim ID. Spec written. Package @uvrn/embed already exists in the ecosystem.
✓ Documented embed gap. Recommended /docs update.
RESEARCHMay 21, 2026run-001
Mapping UVRN use cases beyond digital media
Investigated how the Delta Engine applies to physical supply chain claims - organic certification, water purity, and logistics provenance. Found strong alignment with existing /research case study. Flagged 3 potential new domains: pharmaceutical cold chain, agricultural inputs, and renewable energy certificates.