Git for the US Code

Original Article ↗ Hacker News Discussion ↗

Using Git-style version control to track changes in legislation is attracting interest as a way to make laws more transparent and navigable over time. Commenters point to existing efforts in the U.S. and Europe, the commercial role of services like LexisNexis, and the importance of knowing not just the current text but what the law said at a given time and how it was amended. Others argue that legal change-tracking has requirements Git wasn’t designed for, and that real gains will depend as much on better public access, tooling and journalism as on any specific technical system.

Concept: “Git for the US Code”

  • Core idea: treat statutes like code in a VCS, tracking every textual change, who proposed it, and when.
  • Enthusiasts see benefits for transparency, accountability (“git blame” for legislators), and easier diffs between versions.
  • Some want full PR-style workflows for bills, with branches per chamber and visible merge histories.

Bills vs. Laws, Text vs. Meaning

  • Several comments distinguish between:
    • Bills: where authorship and amendments matter a lot.
    • Enacted law: where many argue only the vote record should matter, not line‑by‑line authorship.
  • Others stress that “text history” is not enough to know “what the law is” because case law and constitutional rulings can leave text unchanged but unenforceable.

Existing Systems and Prior Art

  • US: Library of Congress, GPO, and commercial platforms (LexisNexis, Thomson Reuters) already track historical text, often via messy PDF/web scraping.
  • Multiple foreign examples: French “La Fabrique de la Loi,” Polish ISAP, Swiss Fedlex, German laws/constitution repos, DC’s law-xml, EU XML tools, and the “archive framework.”
  • Some commenters are building or have built specialized systems (e.g., compiler-like pipelines, legal diff tools) and say naïve Git is a poor conceptual fit.

Technical and Structural Challenges

  • Hard problems: section renumbering/moves, cross-references, amendments that both move and edit blocks, multiple jurisdictions, and time-aligned linking of statutes, regulations, and cases.
  • Distinction between changes to the law vs. corrections to the change-log itself (“metachanges”).
  • Debate over what the “atomic unit” of legislation is; unclear consensus.

Access, Transparency, and Politics

  • Strong support for free public access to both statutes and case law; frustration with paywalled codes and lawsuits against open publishers.
  • Some argue more transparency (and a clean history) would help journalists and voters; others say the real bottleneck is lack of good journalism, civic engagement, and moneyed influence.
  • Concerns that total transparency of drafting could chill bold proposals or just create new avenues for political gaming.

Usability and Governance

  • Many stress Git’s UX is unsuitable for legislators and the public; call for higher-level, non-technical interfaces (wiki-like or custom) using Git only as a backend, if at all.
  • Agreement that such infrastructure should be a public, non-proprietary function, though how to implement and fund it remains contested.