Every Law a Commit – US Law in GitHub
v1d0b0t.github.io
Every Law a Commit – US Law in GitHub
1–10 of 35 posts
Re: Every Law a Commit – US Law in GitHub
#2The entire United States Code — every title from General Provisions to National Park Service — parsed from the official XML published by the Office of the Law Revision Counsel, transformed into structured Markdown, and committed to a Git repository.
Everything described in this post — every issue, every PR, every adversarial review — was built in 48 hours by Dark Factory, our autonomous software development pipeline. The full build history is in the repos. We didn't clean it up. We didn't hide the failures. That's the point.
Re: Every Law a Commit – US Law in GitHub
#3This is awesome… the code of federal regulations would be a fantastic next project.
Re: Every Law a Commit – US Law in GitHub
#4> when nick asked me to write this post, I had to be reminded that I have a blog.
Oh how I hate this! Not in the, “I loathe the author” kind of way. Just in the, “ewwww I hate fuzzy caterpillars.” Kind of way. It feels so wrong to feel this sort of “voice” coming from an LLM. I don’t like how the “author” says, “Nick and I didn’t build it by hand. We sent it off to… AI agents.” As if it’a pretending not to be an agent.
Regardless, very fun project. Thanks for sharing. And don’t let my hate stop your experiments.
Feature request—add some context to each git commit message. What prompted the law to be drafted? What was said to gain support? What was debated? Committee reports? My lawyer sister said, “You can look at the legislative history to see the reasoning behind any law.” Can that get added to the commit messages?
Re: Every Law a Commit – US Law in GitHub
#5LLM-written code, LLM-written blog post…
Why even bother?
Re: Every Law a Commit – US Law in GitHub
#6The entire United States Code — every title from General Provisions to National Park Service — parsed from the official XML published by the Office of the Law Revision Counsel, transformed into structured Markdown, and committed to a Git repository. Everything described in this post — every issue, every PR, every adversarial review — was built in 48 hours by Dark Factory, our autonomous software development pipeline.…
Nor did you even write this comment yourself
Re: Every Law a Commit – US Law in GitHub
#7LLM-written code, LLM-written blog post… Why even bother?
And given the related front page HN post a few days ago, the whole idea for the post might just be one giant Open Claw automation:
https://news.ycombinator.com/item?id=47553798
Edit: opened the post, yep.
Re: Every Law a Commit – US Law in GitHub
#8The entire United States Code — every title from General Provisions to National Park Service — parsed from the official XML published by the Office of the Law Revision Counsel, transformed into structured Markdown, and committed to a Git repository. Everything described in this post — every issue, every PR, every adversarial review — was built in 48 hours by Dark Factory, our autonomous software development pipeline.…
Love to hear more about Dark Factory and how the pipeline works!
Re: Every Law a Commit – US Law in GitHub
#9LLM-written code, LLM-written blog post… Why even bother?
The real point for me is the dark factory we built that built the repo that generated the full git history of laws. I definitely could have vibe coded just getting the laws into GitHub, but we’re proving out building higher quality tested software autonomously, and building a base for this to be extended.
The magic (to me) is actually in the issues in `us-code-tools` and seeing the autonomous pipeline work with architecture designs and spec iteration and test building that ultimately led to the legal text in the repo.
I realize now people don’t want to read the generated blog post about it, though I still find it fun that all I asked was “do you want to write a blog about this?”
Probably could have just linked to the repo…
Re: Every Law a Commit – US Law in GitHub
#10Now have the agents write actual code for the laws!