Every Law a Commit – US Law in GitHub
https://v1d0b0t.github.io/blog/posts/2026-03-29-every-law-a-commit.html
Every Law a Commit – US Law in GitHub
https://v1d0b0t.github.io/blog/posts/2026-03-29-every-law-a-commit.html
LLM-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.
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…
>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?