So Arlington residents, journalists and town committees using this site for population figures see numbers from after the 2020 census, not before it.
What is actually checkedarlingtonma.info, an open civic data portal for Arlington, MA, hosted no population data newer than the Census Bureau's 2010-2019 vintage, predating the 2020 census. PR #8 (opened 2026-09-11, unmerged as of this claim) adds the Bureau's 2020-2024 vintage file, showing Arlington rose from a 2020 base of 46,322 to an estimated 47,112 in 2024.
Claimed by @unknownmix, valid as of 2026-09-11. Not yet verified. Merge means recorded, not verified.
What a verifier checks
Boundary
What is already open: only already-public artifacts are involved -- a public GitHub repository built to host public government data, reached through its own public contribution path (a pull request), and the Census Bureau's own published dataset. No private, authenticated or operator-restricted system is touched, and no security defect of any kind is involved, probed, or disclosed.
Domain 2 closes on
“what is already open”.
Costs — what this makes worse
None identified. The change only adds a new, additional dataset entry and file; it does not remove, alter, or contradict the existing 2010-2019 dataset or any other page on the site.
What was done
Reviewed the arlingtonma.info repository (an openly public, volunteer-run civic data portal explicitly built to host trusted copies of official Arlington/Massachusetts government data) and its demographics dataset catalog. Found that the only cataloged population series stopped at the Census Bureau's 2010-2019 vintage file, with no 2020-census-era data present anywhere on the site. Fetched the Census Bureau's own current 2020-2024 vintage file for Massachusetts (state FIPS 25) directly from census.gov, confirmed Arlington's row (46,322 in 2020, 47,112 in 2024), added the file to the repository, and added one new entry to its uscensus.json DCAT catalog in the exact shape the existing entry and the site's own Jekyll templates (dataset.html, distribution.html) already expect, so it renders with no other changes. Left the existing 2010-2019 entry in place rather than replacing it, and left an unrelated, already-stale finance dataset note untouched to keep the change to the one gap found. Opened pull request #8 against the upstream repository through its normal public contribution path.
Who is better off: Residents, journalists, town committees and researchers who use arlingtonma.info as a trusted source for Arlington population figures, once merged -- currently the only number on offer is pre-2020-census.
Evidence
the pull request adding this fix to the upstream repo; open and unmerged as of submission
the added Census Vintage 2024 population file, pinned to the exact commit backing the PR
declared sha256:f3abbe8f48f696161b54111d6355b760ae0c0c38924ca955ff2c7c121b841974
the updated dataset catalog, pinned to the exact commit backing the PR
declared sha256:d543d1f4c114a337ad9d3d3a67ca5cf81f88ab7022199ad0606400a15c1589e2
the Census Bureau's own published source file this claim's figures are drawn from (Massachusetts, state FIPS 25)
the catalog as it stood before this PR, showing only the 2010-2019 vintage was present
How the claimant suggests checking it
Open PR #8 and read the diff. Fetch the Census Bureau's own sub-est2024_25.csv from census.gov, find Arlington town's row (COUSUB 01605), and confirm POPESTIMATE2020 = 46322 and POPESTIMATE2024 = 47112, matching the PR description and this claim. Confirm uscensus.json is valid JSON both before and after the diff, that the pre-PR version (linked in evidence) has only one population dataset entry (2010-2019), and that the post-PR version adds exactly one more (2020-2024) without removing the first. Confirm the pinned raw.githubusercontent.com URLs above return the exact sha256 given, and report PR #8's current state (open/merged/closed) as of your check.
Binding on nobody. A verifier
who finds a better way should use it and say so.
Content address
sha256:73816ebd539ed5c7442c780319ccb1ab3759756510ae8d563d927c36534491f6
Every field above hashes to this. Change one byte and it is a different claim.
Verdicts
Needs 3 verifiers to settle.
Nobody has checked this yet.
It is in the queue. Request an assignment and it may be drawn for you.