April 3, 2026
Order in the source code!
United States Code (federal laws) in Git
Coders want to track laws like code; lawyers swoop in with “actually”
TLDR: Someone put the entire U.S. Code into a change-tracking system so anyone can see how laws evolve. Commenters dreamed of open-source lawmaking, debated legal nitpicks about “positive law,” asked for the missing Statutes at Large, and sparred over duplicates—proof that transparency thrills techies and terrifies pedants.
America’s laws just got checked into version control, and the internet is losing it. A new project stores the entire United States Code in a Git repository—think a timeline of edits for federal law—so you can see exactly what changed and when. Devs are hyped: one commenter cheered, “this is how legislation should work”, imagining open comments, pull requests (public edits), and even AI to filter trolls. Cue the memes about “git blame” for lawmakers and “Ctrl+Z for Congress.”
But this is the internet, so the lawyers arrived with footnotes. A heated aside erupted over what counts as “positive law” versus “evidence of the law,” with one user correcting the wording and citing 1 USC § 204 like it’s the Rosetta Stone. Meanwhile, another asked the practical question everyone else missed: where’s the Statutes at Large? (That’s the official book of every law as passed.) International comedy break: a Dane lamented that their laws get updated by swapping words line-by-line, inspiring jokes about a nation ruled by “find and replace.” And, of course, the dupe police linked a prior post, because tradition never sleeps (link).
Nerd fights aside, this is actually big: seeing the law’s history in plain text makes power legible. Today it’s tracking changes; tomorrow, the crowd wants to collaborate.
Key Points
- •Entire United States Code is stored as Markdown in a Git repository, enabling versioned tracking of legal text.
- •Each commit maps to an OLRC release point, with tags marking annual and congressional snapshots from 2013 to 2025.
- •Repository scope: 53 titles, ~2,950 chapter-level files, and ~60,400 sections with full text and notes.
- •Data originates from OLRC USLM XML and is transformed to Markdown using us-code-tools, with YAML frontmatter for metadata.
- •Git commands (log, diff, blame) and tags allow users to view history, compare versions, and trace changes to specific provisions.