MO Bill Watch

I read bills for a living once, as a legislative budget analyst, so I know exactly where the official record fails you. Bills are hard to track: the real work isn't watching a status line, it's reviewing what changed from version to version, the substitute that swaps out the whole text, the new statutes quietly added along the way. And the same statute can be written into several bills at once, so following one bill never means you've seen the change coming. Bills are hard to understand: they're written as instructions for amending statute, not as an explanation of what they'd actually do. The people who need that picture (lobbyists, associations, reporters, citizens) rebuild it by hand, and everyone else goes without it.

Treat the whole session as data. Every bill gets a page. Every sponsor, every topic, and the shape of the session itself: how many bills go in, how few come out. Say what a bill does in plain language, because the bill text won't. Then a watchlist so a reader can follow the ten bills they care about instead of scanning three thousand.

3,403 pages: a page for every one of the 3,142 bills filed in 2026, including each of the 3,040 that died, plus 191 sponsor pages, 17 topic pages, and a live visualization of the session's attrition. Plain-language summaries for the 102 that became law. Accounts and watchlist sync. Two ingest scripts, both hermetic, so a slow upstream can never break the site.

The site factory I built for exactly this (a manifest, a scaffold, a QA gate, a launch packet) turned a niche I know cold into a live product before the week was out. That's the whole argument for the AI moment in one build.