Proof · the fleet
Scrapers, validators, and agents refresh the data behind these pages on their own schedules — pull, validate, commit, redeploy — with no one at the keyboard. Every number below is read at build time from the actual data files, not typed by hand. When a pipeline slips past its cadence, this page says so rather than painting itself green.
Ledger regenerated Aug 24, 2026 — this page rebuilds every time the fleet pushes.
4/4
pipelines current
2,115
records kept live
27
economic series validated each run
0
hours of my week spent refreshing them
Pulls fresh series from FRED, validates every one against release-window and drift thresholds, gates on a clean build, commits the snapshot, and lets Vercel redeploy. A failed check opens a GitHub issue and emails an alert instead of shipping bad data.
27/27 series PASS · next refresh Aug 25, 2026
A scheduled Claude skill scrapes the rent and buy catalogues, diffs them against the tracked history (first-seen, price changes, dropped listings), merges, and commits the JSON straight to main.
Rentals + homes tracked since May 24, 2026
Pulls recent analytics-leadership openings by role family, rewrites the openings feed and the newsletter digest, and pushes to main.
Anonymized dbt views over the private task database — allow-list models that emit only aggregates, then a leak gate (allow-list, PII patterns, a contacts oracle) plus range and derivation tests. A red test blocks publish; the site never reads a view the gates have not passed.
27/27 gates green · leak gate PASS
“Records kept live” sums the validated economic series, the active rent and buy listings, and the tracked roles — each read from its own file at build. The economic pipeline’s validation output is public too, at the dashboard it feeds.
The fleet is rentable. This is the same automation the Bench puts on your data — the scheduled refreshes, the validation gates, the alert-on-failure. What it does for this site, it can do for your warehouse. The Upbound build is what the first one looks like.