I lead the Common Form project, which maintains https://www.npmjs.com/package/commonform-lint https://www.npmjs.com/package/commonform-lint among other tools.

I lead the Common Form project, which maintains https://www.npmjs.com/package/commonform-lint https://www.npmjs.com/package/commonform-lint among other tools. Mostly, this handles "linting" structural aspects of legal terms, such as making sure that every special term invoked gets defined, every section referenced actually exists, and so on. But we've also been able to include some very rote stylistic checks, such as alerts about archaisms, legalisms, and needlessly wordy phrases. Even just this has proved an amazing boon in day to day practice. Akin to having real-time syntax checking in a code editor. Computers excel at the rote and structural. They really suck at substantive analysis, even with all the recent ML work I've seen...except where the substance in or out is rote or structural. You can probably get a model to read back effective dates or share prices out of a bucket of PDFs. First Amendment analysis? Is it going to predict Supreme Court cases for us, too? The hard work in law is nearly always pattern matching---What law applies to this situation? Does the definition cover this case, given its language and purpose?---rather than calculating a bunch of deductive implications from neatly coded factual situations. A lot of the fights in law are about how to code the situation, because of how the law applies from there.