Credibility registry
Every number, with its source.
The rule this site is built on: if a claim has no source, it does not get published.
Verification statuses are honest about their kind — machine-verified means I re-ran the suite
and dated it; pilot-verified means it comes from real pilot records that contain client data and are
shown redacted, not published. A consistency check (check-claims.mjs)
runs against every page before deploy and fails on drift or on any retired number reappearing.
| Claim | Source | Status | Public evidence |
|---|---|---|---|
| 20 qualified opportunities | Referral Desk pilot records (production DB) | Pilot-verified | Attribution schema public (attribution kind + confidence enums); redacted ledger in walkthrough · evidence → |
| ~$10K written premium influenced | Producer policy records, attributed via the schema above | Pilot-verified | Schema separates premium from revenue and stamps confidence (confirmed/probable/assumed) · evidence → |
| 1,666 automated checks (Referral Desk) | vitest run, private production repo | Machine-verified 2026-08-30 | Invariant subset runs green in public CI; 92/37/3 file split · evidence → |
| 93 tests (Load Desk) | node:test run | Machine-verified 2026-08-29 | Open sandbox at loaddesk-omega.vercel.app · evidence → |
| 2–3 wks → same day (Load Desk) | Workflow comparison: outsourced Manual-J vs in-app process | Design-verified | Full workflow demonstrable in the open sandbox · evidence → |
| 88 checkpoints (ProWAX) | Deployment build for the facility | Client-deployment | Facility system is private; walkthrough on request · evidence → |
| 4 production incidents documented | Migrations, route comments, and tests in the repos | Repo-documented | Two are published verbatim in the public repo (postmortem migration, two-tenant test) · evidence → |
Retired numbers this check now forbids anywhere on the site: “868 automated tests” (stale — the suite is 1,666), “12 products” (the count was 11, and counts are no longer a headline), “940+”.