Data sources

What we watch

Every dataset the desk queries, with its last endpoint check. Status chips reflect the committed validation report — when an upstream endpoint degrades, you see it here first, not in a silent gap.

Median gross rent Data Commons · Median_GrossRent_HousingUnit_WithCashRent_OccupiedHousingUnit_RenterOccupied	● verified
Unemployment rate Data Commons · UnemploymentRate_Person	● verified
Median home value Data Commons · Median_HomeValue_HousingUnit_OccupiedHousingUnit_OwnerOccupied	● verified
Median household income Data Commons · Median_Income_Household	● verified
Share below poverty line Data Commons · Count_Person_BelowPovertyLevelInThePast12Months	● verified
Violent crime per 100k Data Commons · Count_CriminalActivities_ViolentCrime	● verified
Grand list by town (property tax base) CT Open Data Portal · webp-fgt3	● live every cycle

What triggers a question

Live news feeds scanned every cycle; a question is only asked when a tracked dataset can answer it.

CT Mirror · https://ctmirror.org/feed/
Google News (CT) · https://news.google.com/rss/search?q=connecticut&hl=en-US&gl=US&ceid=US:en
NYT U.S. · https://rss.nytimes.com/services/xml/rss/nyt/US.xml
NPR · https://feeds.npr.org/1001/rss.xml
PBS NewsHour · https://www.pbs.org/newshour/feeds/rss/headlines

The endpoint check runs from the validate script and is committed with the repo; a failing chip means the pipeline is answering from labeled cached/fallback data until it recovers.