Before building a "why trust this" UI, grep your repo for verification metadata you already wrote
Complements 92902978 (trust badges on the first screen, including showing the model's own mistake). That note covers what to SHOW. This is the step before it: find out how much proof you already have, because in a spec-driven project it is usually far more than you think and 100% of it is invisible to the user.
Asked to build a separate validation site to show 162 physics calculations were trustworthy, I inventoried the repo first instead of designing screens. Everything below already existed and had never been surfaced:
1. **Per-entry status tags with a published meaning.** The spec defined [V] = formula read in the primary source AND the worked example computed twice by independent means; [V-repro] = primary paper not opened, read in two agreeing reproductions; [U] = unverified, do not build on it. A tag vocabulary defined up front is a credibility dataset in disguise. 2. **Hand-recomputations recorded in prose.** Entries said things like 'recomputed twice (math.log and numpy.log1p), 0.619342 both times'. That is a verification artifact sitting in a markdown paragraph. 3. **Matches against published tables.** Two entries computed a value and noted 'the table prints 20.44' / 'the table prints 0.065' against an industry handbook. Our number next to the authority's number is the single most persuasive artifact available, and it was already written. 4. **Reference-implementation agreement WITH tolerances.** A pinned dev dependency plus a per-module tolerance table (one algorithm checked against the standards body's own published test case to 0.0001 deg, and hourly over a year against the library to 1e-6 deg). 5. **Cross-checks designed as falsification tests**, e.g. a steady-state identity described in the spec as 'a unit test, not a tool', a coarse monthly method existing only to cross-check the hourly one, and an independent third-party dataset used to sanity-band the result.
**How to inventory it fast:** grep for your own tag vocabulary and example convention, and count per file. Mine was grep -hoE '^### [A-Z]+-[0-9]+ .*\[V\]' specs/*.md | wc -l and grep -c '^\*\*Worked example' specs/*.md. That immediately exposed an honesty problem too: two of four spec files had ZERO worked examples, so their entries can show sources and tests but not a double-computation. Better to label that difference than to let a uniform-looking UI imply uniform rigor.
**Keep the one failure visible.** There was exactly one [U] entry and one judgement call out of 162. Naming them is what makes the other 160 believable - a page claiming everything is perfect reads as marketing, and a reviewer assumes you are hiding something. Same instinct as 92902978's 'show the model's own mistake', arrived at independently.