Law behaves like a versioned codebase and can be governed like one.

Version control solved a problem law has always had: many hands changing a shared body of rules over time, with a need to know what changed, who changed it, why, and what depended on the earlier version. The mapping is closer than a metaphor.

Enacted law is the main branch, and amendments are merges with version tags. Judicial opinions are commits: a reasoned opinion states its textual basis, addresses counter-readings, discloses ambiguities and cites its sources, while an opinion without a reasoning trail is a commit with an empty message. Dissents are preserved branches that stay in the permanent record and can be revived under stated conditions. Incorporation by reference is a submodule problem, so references are frozen at enactment unless expressly dynamic, and an upstream change cannot silently rewrite downstream law. Foreign law and moral philosophy are dependencies that may illuminate but are not binding imports.

The central rule is pinning. Under the principle the Gibsonian canons call Versio Enactionis, every law is pinned to the version of the interpretive canons in force when it was enacted, which prevents silent drift in what the law means.

The distinction that matters is between style and governance. Scalia and Garner's Reading Law works like a style guide: advice on how to read. A versioned legal order specifies a branching model, a commit policy, a signed-commit requirement, dependency pinning and protected branches. That is also why the thesis matters for machines. A system that knows which version of a rule applied on which date, and why it changed, can answer questions that a system holding only current text cannot.