Source views: Source JSON(ish) on GitHub (VSCode)   Doc views: Document (&k=r00t): Visual Print Technical: OpenParameters Xray
Ti = Legal codification by software methods
1.sec = Legal codification has a long history.
2.sec = Codification is one of the most effective means for improving collaborative relations.
3.0.sec = There are many methods:
3.1.sec = treaty;
3.2.sec = legislation;
3.3.sec = rules;
3.4.sec = model documents;
3.5.sec = master agreements;
3.6.sec = precedents;
3.00.sec = This is not intended to be exhaustive.
3. = [G/Z/ol/s6]
4.sec = Despite the usefulness of codification, much of transacting is not codified, including many areas where there are high volumes and low degree of customization.
5.sec = The entire stack of codification can be handled as a single phenomenon by adopting the methods of open source.
6.sec = Effects.
7.1.sec = It is common to insist that software code and legal code are fundamentally different. It is true that interests systematically oppose in legal text, while many aspects of software do not involve opposing interests. But this difference is of degree and not fundamentally an obstacle.
7.2.sec = In both cases, texts readable by humans with special training, are used to manage something. In both cases, it is better to start with a text that has a history of success and a community of users. In the case of law, there is an additional reason, of great importance. The text does not run "deterministically" on a machine, it "runs" in the minds of people, and the people whose minds count most are strangers to the transaction - judges, litigators, management, insurers, creditors. Legal text runs socially.
7. = [G/Z/para/s2]
= [G/Z/ol/s7]