Release 9/11: short release post on jaredknowles.com #50
Closed
opened 2026-08-08 18:44:53 -04:00 by jared
·
1 comment
No Branch/Tag Specified
main
ci/mirror-canonical-tags
chore/release-47-badges-mirror-pr
docs/readme-perf-remeasure-56
feat/pagination-search-balances-57
feat/duckdb-threads-60
feat/cohort-predicates-58
fix/windows-backslash-paths
ci/mirror-to-github
ci/github-actions-matrix
feat/public-release-0.3.0
chore/fixture-sb203
ci/apt-https
fix/pushdown-pagination
feat/all-categories-37
fix/partial-coverage-signposting-9
fix/schema-v7
fix/cog-categories-balance-subtype
feat/cog-balances-25
feat/revenue-concepts-12
feat/expenditure-concepts-11
feat/coverage-disclosure-13
feat/complete-argument-18
fix/kodor-batch-14-15-16
fix/all-scoped-series-breaks-19
fix/regen-fixture-corpus-18
test/walkthrough-findings
feat/expenditure-concept
fix/3-url-trailing-slash
feat/phase-r3-signposting
fix/fixture-option-b-aggregates
feat/phase-r2-harmonization
feat/phase-r1-forward
feat/cog-gov-search-basket-mode
v0.4.0
Labels
Clear labels
kodor
kodor/feature-proposal
kodor/fix
kodor/needs-review
kodor/triaged
madison-walkthrough
severity/high
severity/low
severity/medium
south-guide
verdict/defect
verdict/definitional
kodor
kodor/feature-proposal
kodor/fix
kodor/needs-review
kodor/triaged
Kodor should process this issue
Kodor has written a feature proposal
Kodor should implement a fix (assigned to Kodor)
Kodor's work or failure needs Jared's review
Kodor has already triaged this issue (skip)
Surfaced while building the client-facing Southern API guide
needs
human
Cannot move without a person -- a decision, a check an agent cannot make, something outside the repo
origin
client
Came from a client ask
origin
obligation
Created by a change elsewhere
origin
review
Came from human review
origin
roborev
Promoted from a roborev finding
type
chore
Maintenance with no behaviour change
type
debt
Owed work -- docs, tests, cleanup a change obligated
type
decision
Needs a decision before work can proceed
type
defect
Something is wrong
type
feature
New capability
ws
api
Query verbs and results
ws
corpus
Corpus, mirror, provenance
ws
docs
Vignettes and guides
Assign a task to kodor
Kodor thinks this needs a feature.
Kodor should fix this
Kodor thinks the user is ready to review this.
Kodor is done with this issue.
No labels
Milestone
No items
No Milestone
Projects
Clear projects
No projects
No Assignees
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: Civilytics/uscogdata#50
Reference in New Issue
Block a user
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Depends on #47 (needs a working install line to point at).
Short release post on jaredknowles.com. Precedent:
content/posts/mertools-1-0-released/— same front matter shape (type,slug,lede,tags,license,citationblock), and note the raw-HTML dropcap convention, since goldmark does not parse markdown inside a raw HTML block.What the post has to say
The pitch is the corpus, not the package. Every dollar US state, county, municipal and township governments reported raising and spending, FY1967–FY2024 — 46,148,034 rows, 190.6 MB, in one queryable place, free.
The honest hook is that the Census of Governments is the only nationwide source for this and is genuinely hard to use: item codes change meaning across vintages, identifiers were renumbered in 2017, and an absent value means "published zero" in one era and "not reported" in the next. The package handles each of those and tells you when it has.
Worth including: the three-line quickstart that runs with no configuration, and one real finding from the data rather than a feature list.
Deliberately NOT in this post
Done when
Draft ready for review:
content/posts/uscogdata-released/index.mdOn branch
feat/uscogdata-r-package-cardin the jaredknowles.com repo (same branch as#51, so they can be reviewed together). Not published — merging is what publishes.
Follows the
mertools-1-0-releasedprecedent: same front-matter shape, and the raw-HTMLdropcap with hand-written HTML inside it, since goldmark will not parse markdown in a raw
HTML block.
The finding is real, and it changed while I was checking it
The issue asked for one real finding rather than a feature list. I computed it against the
published corpus, and the first version was wrong in an instructive way.
A ten-category basket said police went from 40.1% to 45.1% of city spending — emphatic,
and nearly meaningless, because the denominator was a basket I picked. Against all city
current operations:
Police operations grew 2.46x in real terms over 45 years; all city operations grew
2.39x. The share is roughly where it started. What actually moved is per resident:
median city police operations went $109 → $225 in real 2024 dollars.
Both statements are true and which one leads is a choice — which is the argument for the
data being easy to check. That is the post's spine.
Checks run before writing it: census years only (every other year is a sample);
identical under both the
primaryanddirectexpenditure concepts; zero coverage-gapsuggestions from provenance.
The post then names the four breaks the package surfaced unprompted for that query —
including the FY2022 capital-outlay merge, which turned out not to apply because the
series is operations only. That non-applying case illustrates what the tool does better
than a feature list would.
Held back, per this issue
until #52 is designed.
One thing to check on review
The scope paragraph says special districts and school districts being out of scope is
"a real gap, and for school finance questions it is a disqualifying one." That is honest
and I think it belongs, but it is the sharpest self-criticism in the post — worth a
deliberate yes/no from you rather than sliding through.
Renders clean: dropcap intact, table and both code blocks fine, no stray markdown.