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 Oct 11, 2026 — this page rebuilds every time the fleet pushes.
6/7
pipelines current
2,318
records kept live
29
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.
29/29 series PASS · next refresh Oct 12, 2026
A Claude agent runs two deterministic scrapers, rent.com for rentals and Redfin for homes for sale; scripts/housing-merge.mjs diffs both against the tracked history (first-seen, price changes, dropped listings), scripts/housing-validate.mjs refuses a corrupt catalogue, and only then does the JSON land on 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.
Re-reads UltraSignup’s public event search around Ogden and re-snapshots the two anonymized Strava views (long runs, weekly roll-up) after the dbt gate has passed them, commits only when a row moved, and lets Vercel rebuild — at build the pages read the views live anyway, so the site is never more than a day behind the log.
events feed Oct 10, 2026 · run snapshots Oct 10, 2026
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 · Covers 2 of 4 showcase models; rerun dbt build and write-status.mjs
Asks each publisher in the registry what it has out. When a new release lands and the dataset has a committed fetch script, it runs the script, the tests and the build, and opens a pull request; datasets that need a person go into one issue.
8 refresh unattended · 14 by hand
An agent prices two sworn DoorDash baskets to the same door every Wednesday (never ordering, never tipping, no promos) into the mission-control database, and a Thursday job exports them here. The Larder tab sets them against CPI food prices from the FRED pipeline.
2 weeks of prices; grocery last priced 2026-10-03, pizza last priced 2026-10-03
“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.