--- title: Git for US Legislation | daily.dev description: A project rebuilds a Git-like history for nine titles of the US Code by replaying every amendment in order. Of 365 changes tested since 2017, 361 reproduced... canonical: https://daily.dev/posts/git-for-us-legislation-qi8rhupla twitter:card: summary_large_image twitter:site: @dailydotdev og:type: website og:site_name: daily.dev og:title: Git for US Legislation | daily.dev og:description: A project rebuilds a Git-like history for nine titles of the US Code by replaying every amendment in order. Of 365 changes tested since 2017, 361 reproduced... og:url: https://daily.dev/posts/git-for-us-legislation-qi8rhupla og:image: https://api.daily.dev/og/posts/qi8rHuplA.png og:image:alt: Git for US Legislation og:image:width: 1200 og:image:height: 630 og:locale: en --- > ## Documentation Index > Fetch the complete documentation index at: https://daily.dev/llms.txt > Use this file to discover all available pages before exploring further. # Git for US Legislation **[Hacker News](https://daily.dev/sources/hn)** · 6 min read · 2 upvotes · 0 comments ## Summary A project rebuilds a Git-like history for nine titles of the US Code by replaying every amendment in order. Of 365 changes tested since 2017, 361 reproduced the next official release point exactly, with the other four flagged by how far they could be confirmed. Each change records the law and effective date: 261 took effect by default on enactment, 72 by an effective-date note, 29 by a date stated in the amendment. A Technical University of Munich study found a model answered 24% of post-cutoff statute questions correctly alone versus 87% with the relevant text retrieved, and amendment-applying models matched official text exactly only about half the time for single amendments. The tool still can't show when a later law reaches back to cover earlier dates, like the 2022 bankruptcy debt-limit gap. ## Full article daily.dev links to this article rather than hosting it. Read it at the original source: ## Questions this post answers ### How accurate are LLMs at answering legal questions about laws changed after their training cutoff? One model answered only 24% of post-cutoff statutory questions correctly when relying on its own knowledge, but accuracy rose to 87% when the relevant statutory text was retrieved and provided to it. A Technical University of Munich study on German statutes found models also tend to apply superseded rules and favor newer provisions over older ones that actually govern the facts, concluding temporal validity must be treated as a hard constraint. _Developers building legal AI tools can track retrieval-vs-memory accuracy research like this on daily.dev._ ### Can an LLM accurately reconstruct an old version of a law by applying amendments in reverse? Not reliably. When a model applied German amending laws to earlier statutory text, the output looked 93 to 99% similar to the official version by text similarity, but only about half of single amendments and a fifth of amendment chains matched exactly, with experts finding legally significant errors in the near misses that looked correct. _Anyone evaluating LLM output against ground-truth text can follow this kind of accuracy benchmarking on daily.dev._ ### What was the small business debtor debt limit under 11 USC 1182(1) for a bankruptcy case filed in May 2022? The lower, original small business debt limit applied, not the CARES Act's raised $7.5 million threshold. The CARES Act increase lapsed on March 27, 2022, and was not restored until June 21, 2022, when Congress reached back to cover cases commenced on or after March 27, 2020 that were still pending, creating a gap for cases filed in between. _Practitioners tracking statutory effective dates and retroactive fixes can follow bankruptcy law changes like this on daily.dev._ ## Community take How the wider developer community reacted, aggregated from 1 discussion and 98 comments across hackernews (as of 2026-10-28). **TL;DR:** Many find the idea of version-controlling US law appealing and overdue, but a large chunk of the discussion pushes back on whether commit-style tracking actually solves the transparency/accountability problem it's aimed at, citing legal complexity, attribution issues, and existing tools lawyers already use. **Sentiment:** 40% positive · 40% mixed · 20% skeptical **The case for** - The underlying concept of applying git-style diffs to track legislative text changes is seen as an obvious, long-wanted idea by many developers. - Some see it as a genuine win for transparency and for enabling AI/agent-based research into legal text. - Similar systems already exist abroad (France, Poland) and at the DC/local level in the US, suggesting the approach is viable and useful. **The pushback** - Several argue the real problem is lack of journalism/oversight, not lack of a commit graph, so the tool wouldn't fix accountability on its own. - Attribution is seen as technically and politically fraught since actual drafters are often legislative counsel or lobbyists, not the named legislators, and tying authorship to text could break confidentiality/privilege norms. - Commenters note law's meaning depends heavily on court interpretation and legislative history, so a pure text diff is insufficient for understanding what a law actually does. - Some pointed out that similar git-for-law tools already exist elsewhere, and that lawyers already have comparable (if commercial) change-tracking tools (LexisNexis, Thomson Reuters), making this less novel than it seems. - A couple of commenters found the writeup itself read like AI-generated prose, which they found off-putting. **By community** - hackernews (mixed): Enthusiasm for the git-for-law concept is tempered by substantial skepticism about whether it solves the real transparency/accountability problem and concerns about attribution, legal complexity, and existing alternatives. **Hottest debate:** Whether tracking authorship/provenance of legislative changes would actually improve transparency and accountability, or just create new ways to game or obscure responsibility. **Open questions** - Is there a public, authoritative, long-term data source for historical versions of US legislation at federal and state levels? - Can such a system meaningfully represent legal complexity like court rulings effectively striking text without removing it, or later laws retroactively covering earlier dates? - Would a transparent commit-authorship system break the confidentiality/privilege norms of legislative counsel, and is that a worthwhile tradeoff? **Highlights** > We don’t need version control for legislative bills. We need journalists that track down who tried to insert what, summarize it, and present it to the public with context. That would satisfy the oversight purpose without getting lost in technicalities. Our problem is that the press isn’t doing their job, not that legislation doesn’t have a commit graph. The latter, even if it existed, would not fix the former. > — [p-e-w on hackernews · 6 comments](https://news.ycombinator.com/item?id=50269808) > Such a requirement would not do what you think it would. There would not be names legislator or even aids as commit authors. The commit authors would be members of the House Office of the Legislative Counsel[1]. The House Office of the Legislative Counsel is non-partisan, impartial, and confidential. Whether transparency has merit or not, tracking provenance would make the office partisan. Is more partisanship in government not a concern? The second issue with transparency is that communication between legislators and legislative counsel member is subject to the attorney-client relationship. Breaking attorney-client privilege is a serious decision. Knowing how such a change would affect the organization and its members is not something to be taken lightly. A more convincing argument for transparency would address impartiality and confidentiality. This is pretty clearly a Chesterton's fence type situation where advocating to change a system should anticipate criticisms. Addressing opposition preemptively is an implicit demonstration of knowing why the system exists which is table stakes for changing it. 1. https://legcounsel.house.gov/ > — [kelseyfrog on hackernews · 1 comments](https://news.ycombinator.com/item?id=50269714) > I think it's useful to link to a lawyer's take on the utility of a similar tool that was built by somebody else here: https://bsky.app/profile/questauthority.bsky.social/post/3mj... The tl;dr is that doing git-style change-tracking of the legislation isn't as helpful in practice as you'd think (especially because a lot of the very basic change-tracking is already available in the existing tools that lawyers use!). > — [jcranmer on hackernews](https://news.ycombinator.com/item?id=50269104) > Following renumbers has to be one of the worst parts of this. As an example, the text of the US code that was modified by the BCRA in 2002 has been renumbered / moved since Citizens United v FEC was decided. But the text itself is the same as it was since the BCRA passed, because courts don't remove the actual law text with their decisions. So if you want to know what parts of the current US code were ruled unconstitutional by the courts in that decision and are therefore unenforceable, you need to first find the text of the BCRA, because the ruling refers to the sections of that piece of legislation. Then you need to find the version of the US code that was on the books when the BCRA was passed to find the section references that the law talks about. Then you need to find the law that renumbered that part of the US Code and find the new parts. Then you need to see if any changes have been applied since (there hasn't really) and then you need to match the changes to the referenced sections in the old version of the code to the equivalent text in the current version of the code, modulo any changes to references that changed as part of the renumbering but are otherwise the same. I'm not saying lawyers aren't really really expensive, but you don't have to spend a long time digging into just a simple question like "what parts of the law are no longer enforceable after a supreme court decision" before you start to understand why they charge the prices they do. > — [tpmoney on hackernews](https://news.ycombinator.com/item?id=50269600) > I've been working on this problem for several months now: https://www.wordstodata.com/ A surprising amount of tracking and diffing in legal texts is actually very different to git. It's a trap to assume software version control fits the needs for legal work. > — [scronkfinkle on hackernews](https://news.ycombinator.com/item?id=50270056) > The Hacker News Community (hah) needs to lobby hard to pass a law (what boostrapping!) to require the https://en.wikipedia.org/wiki/Office_of_the_Law_Revision_Cou... to maintain the repo as part of their duties, and do it retroactively for the entire history of the US Code. It's a simple idea; it's cheap; there are no outstanding technical questions; it benefits almost everyone. Let's get this done. > — [Ericson2314 on hackernews · 2 comments](https://news.ycombinator.com/item?id=50268920) **Source threads** - [hackernews](https://news.ycombinator.com/item?id=50268380) · 182 points · 98 comments ## Similar posts on daily.dev - [Developer policy update: Transparency, state policy, and what’s ahead](https://daily.dev/posts/developer-policy-update-transparency-state-policy-and-what-s-ahead-eqighayak) · GitHub Blog · 0 upvotes · 0 comments - [Always Be Blaming](https://daily.dev/posts/always-be-blaming-yi37onju1) · matklad · 0 upvotes · 0 comments - [Fish Food for Thought](https://daily.dev/posts/fish-food-for-thought-wp8pjlns9) · Fish Food for Thought · 0 upvotes · 1 comments - [I Improved 15 LLMs at Coding in One Afternoon. Only the Harness Changed.](https://daily.dev/posts/i-improved-15-llms-at-coding-in-one-afternoon-only-the-harness-changed--ureifftu2) · Hacker News · 1 upvotes · 0 comments --- Tags: [#llm](https://daily.dev/tags/llm), [#rag](https://daily.dev/tags/rag), [#legal](https://daily.dev/tags/legal), [#version-control](https://daily.dev/tags/version-control) [View this post on daily.dev](https://daily.dev/posts/git-for-us-legislation-qi8rhupla) ```json {"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://daily.dev/#organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180},"sameAs":["https://twitter.com/dailydotdev","https://github.com/dailydotdev","https://www.linkedin.com/company/daily-dev-ltd"]},{"@type":"WebSite","@id":"https://daily.dev/#website","url":"https://daily.dev","name":"daily.dev","publisher":{"@id":"https://daily.dev/#organization"},"potentialAction":{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https://daily.dev/search?q={search_term_string}"},"query-input":"required name=search_term_string"}}]} {"@context":"https://schema.org","@type":"TechArticle","headline":"Git for US Legislation","url":"https://daily.dev/posts/git-for-us-legislation-qi8rhupla","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/git-for-us-legislation-qi8rhupla"},"datePublished":"2026-10-28T03:51:01.130Z","dateModified":"2026-10-28T07:07:25.640Z","description":"A project rebuilds a Git-like history for nine titles of the US Code by replaying every amendment in order. Of 365 changes tested since 2017, 361 reproduced...","image":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/879881ce7f7c24eab07c338566b4b5dc?_a=AQAEuop","thumbnailUrl":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/879881ce7f7c24eab07c338566b4b5dc?_a=AQAEuop","isAccessibleForFree":true,"articleSection":"Hacker News","inLanguage":"en","publisher":{"@type":"Organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180}},"author":{"@type":"Organization","name":"Hacker News","logo":"https://media.daily.dev/image/upload/t_logo,f_auto/v1/logos/hn","url":"https://daily.dev/sources/hn"},"commentCount":0,"discussionUrl":"https://daily.dev/posts/git-for-us-legislation-qi8rhupla","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":2},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":0}],"keywords":"llm,rag,legal,version-control","timeRequired":"PT6M"} {"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"Hacker News","item":"https://daily.dev/sources/hn"},{"@type":"ListItem","position":3,"name":"Git for US Legislation"}]} {"@context":"https://schema.org","@type":"FAQPage","@id":"https://daily.dev/posts/git-for-us-legislation-qi8rhupla#faq","mainEntity":[{"@type":"Question","name":"How accurate are LLMs at answering legal questions about laws changed after their training cutoff?","acceptedAnswer":{"@type":"Answer","text":"One model answered only 24% of post-cutoff statutory questions correctly when relying on its own knowledge, but accuracy rose to 87% when the relevant statutory text was retrieved and provided to it. A Technical University of Munich study on German statutes found models also tend to apply superseded rules and favor newer provisions over older ones that actually govern the facts, concluding temporal validity must be treated as a hard constraint. Developers building legal AI tools can track retrieval-vs-memory accuracy research like this on daily.dev."}},{"@type":"Question","name":"Can an LLM accurately reconstruct an old version of a law by applying amendments in reverse?","acceptedAnswer":{"@type":"Answer","text":"Not reliably. When a model applied German amending laws to earlier statutory text, the output looked 93 to 99% similar to the official version by text similarity, but only about half of single amendments and a fifth of amendment chains matched exactly, with experts finding legally significant errors in the near misses that looked correct. Anyone evaluating LLM output against ground-truth text can follow this kind of accuracy benchmarking on daily.dev."}},{"@type":"Question","name":"What was the small business debtor debt limit under 11 USC 1182(1) for a bankruptcy case filed in May 2022?","acceptedAnswer":{"@type":"Answer","text":"The lower, original small business debt limit applied, not the CARES Act's raised $7.5 million threshold. The CARES Act increase lapsed on March 27, 2022, and was not restored until June 21, 2022, when Congress reached back to cover cases commenced on or after March 27, 2020 that were still pending, creating a gap for cases filed in between. Practitioners tracking statutory effective dates and retroactive fixes can follow bankruptcy law changes like this on daily.dev."}}]} ```