Git-style US Code history records when each statutory change took effect
Original title: Git for US Legislation
Across nine titles, 361 of 365 reconstructed changes matched the next official release point exactly.
Lexifina describes a git-style record of the US Code so lawyers and language models can see which public law wrote a sentence and when it took effect. Outside positive-law titles, the Statutes at Large still govern where they differ from the Code. A cited Munich study found models apply superseded German rules and fail exact amendment chains; the authors say the history must stay checkable.
Unconfirmed: The reproduction counts and the Munich study figures are reported by the authors and the cited paper, not independently verified here.
- Of 365 changes, 261 took effect on enactment, 72 by note and 29 in the amendment.
- One change depends on an agency determination and is left out of the text.
- The tool does not yet show a later law reaching back over earlier dates.
- A cited model scored 24% on post-cutoff questions alone and 87% with retrieved text.
- Countries
- United States
From the original article
4 min read at lexifina.com
A programmer can point at any line of code and see who wrote it, when, and what the file looked like on any past day. A lawyer reading a federal statute usually cannot, at least not without an afternoon in the notes at the foot of the section. But why shouldn't they have the same, convenient system of record?
By alansaber · lexifina.com
A short excerpt; the article and its images belong to the publisher. Summary, key facts and assessment above are AI-written from the article and can be wrong.