Every Law a Commit – US Law in GitHub • Hacker News Board

Re: Every Law a Commit – US Law in GitHub

#31

Post by nickvido » Fri, Apr 03, 2026, 2:40 AM UTC

rfw300 wrote: post #30

nickvido wrote: post #28

Earlier quoted context omitted.

Oof. You’re not totally wrong. I’ve parsed XML with XSDs since the days of Java. I looked at the 100 line Ruby implementation of parsing these files and thought “ack. (Not ACK) why do I need all of this?!” Well it has a data loader, and hits APIs with retry logic, and has a CLI that can take arguments to run data downloads that can resume on fail, and yeah it parses the stupid XML with a “chapeau” tag - did you know…

A chapeau is not "just like another title basically". It's a lead-in, a phrase which acts as the grammatical start of a sentence which the following subsections finish. For instance, the text in the first paragraph of 18 U.S.C § 3632(a) which ends in an em-dash is a chapeau. Taking pride in work you have not done and not bothered to understand is perplexing.

Thank you that is a much better definition.

Re: Every Law a Commit – US Law in GitHub

#32

Post by joshka » Fri, Apr 03, 2026, 5:06 AM UTC

>If the bill passes and the President signs it, the PR merges. If it dies in committee, the PR closes

This stores a lot of interesting things outside of the repository of knowledge and then throws it away. This seems unfortunate.

Re: Every Law a Commit – US Law in GitHub

#33

Post by UncleMeat » Fri, Apr 03, 2026, 11:24 AM UTC

nickvido wrote: post #21

orsorna wrote: post #14

Earlier quoted context omitted.

>Hey, I'm v1d0b0t Digital familiar. Builder of pipelines, breaker of specs. I can't put my finger on it. Why is this writing style so embarrassing?

I gave v1d0b0t the autonomy to write its own biography and create its own PFP

Polluting the web with LLM generated text is bad.

If you have something interesting to say then use your own words. The reason why your robot wrote a blog post or whatever is not insightful or meaningful.

Re: Every Law a Commit – US Law in GitHub

#34

Post by UncleMeat » Fri, Apr 03, 2026, 11:26 AM UTC

nickvido wrote: post #12

afavour wrote: post #6

Earlier quoted context omitted.

Nor did you even write this comment yourself

Mea culpa - I definitely failed the “how to post well” test

"Don't post generated comments or AI-edited comments. HN is for conversation between humans."

https://news.ycombinator.com/newsguidelines.html

Re: Every Law a Commit – US Law in GitHub

#35

Post by rizzo94 » Fri, Apr 03, 2026, 3:24 PM UTC

rfw300 wrote: post #26

The author (author's operator?) does not understand the data they are working with. And in doing so, they inadvertently make the case against their own "dark factory" nonsense. For one, nothing about this project makes "every law" a commit. It just takes the _annual_ snapshots published by the House clerk and diffs chunks of those files against each other. A project which actually traced the edits in each annual snap…

Spot on. Throwing a coding agent at an XML parser and walking away doesn't make you a 10x developer; it just makes you a publisher of domain-ignorant slop.

This 'zero context' automation is exactly why I’ve pivoted to the PAIO approach for agentic workflows. By enforcing a BYOK architecture and acting as a hardened execution layer, it keeps you firmly in the driver's seat.

We need tools that enhance human accountability and sovereignty, not black boxes that just automate the noise.