Legalese.com, deep-tech for law

I just published “Code is Law is Code” medium.com/p/code-is-law-…

@craigaatkinson @StanfordLaw @CodeXStanford @wabisabiyo Open standards, granularity of specification, and a conceptual separation from any particular implementation (in natural language or machine code), are part of the vision for computable contracts. The contract analytics industry takes the first step on the codification journey.

@craigaatkinson @StanfordLaw @CodeXStanford @wabisabiyo Document assembly creates contracts at scale – your contract with your mobile carrier or your ISP is a computer-generated contract. Computerized contracts are found in financial trading (e.g. ISDA) and in e-commerce … or food delivery … or Uber … but they aren't computable.

A moment of Tweets from @StanfordLaw @CodeXStanford #FutureLaw2021 ⚡️ “#FutureLaw2021” To be updated throughout and following the conference. #ComputationalLaw twitter.com/i/moments/1380…

@WhataNutso @agazdecki Wish us luck!

@WhataNutso @agazdecki In the meantime, you can check out our scholarly research on the past and present of contract and legal formalization: docs.google.com/presentation/d…

Another problem I’d love to solve... Streamlining legal doc creation specifically for acquisitions. - letter of intent - NDAs - purchase agreements - existing team contacts - new corp creation - etc Lots of this is standardized for investing. So, why not for acquisitions too?

@shazteca @SamRosmarin @imran_amjad @grepmoney @Suhail @rememberlenny @DoNotPayLaw @NeotaLogic Some say lawyers should adopt these tools. Others say the tools are at odds with the billable hour. William Gibson says "the street finds its own uses for things." What if the people using the tools aren't the lawyers, but the end-user clients who no longer have to hire them?

An industry waiting to be disrupted one day:

@forrestblount @jslez @shantohagopian @Suhail Working on it! On the one hand, labor vs capital says: what can be automated will be automated, so software will eat law. On the other hand, law is a credence good hand-holding clients through high-stakes, once-in-a-lifetime situations, so why not go bespoke? Money no object.

@jslez @shantohagopian @Suhail I think there’s a fundamental issue in the structure of traditional firms that prevents moving power away from attorneys. New models are coming. Trust is paramount but opaque services and downside risk of changing firms are the reason clients haven’t driven firms to modernize.

@windrush followed by dl.acm.org/doi/abs/10.114…

@windrush arxiv.org/abs/1109.2658 should work

Excited about Fernando Schapachnik's presentation on FormaLex next at #icail2017 …paper publicaciones.dc.uba.ar/Publications/2… code github.com/formalex/FL

@CowboyVC @twang Working on it! 🔧🔧🔧🔧🔧🔧🔧🔧 We'll be launching an early release of our DSL soon, with a demo encoding of the YC SAFE. But we can do Series Seed as well to provide a point of comparison. Elements of the toolchain will follow: IDE support, NLG to English, formal verification.

Many legal contracts are relatively standard yet the workflow is highly manual 📑 @twang has a #legaltech idea he’s looking to incubate @CowboyVC Check out his post and let us know if you’re the right person to build it 🔧 medium.com/cowboy-venture… #opensource #startupidea

@lex_node @CommonForm @kemitchell @mbutterick We're bushwhacking just upstream of CommonForm and CommonAccord, to hook the text against semantics. That's where @roundtablelaw's work on declarative logic formalisms comes in: if we have a semantics of contracts, a logic, and a (formal) language, we can compile down to English.

@lex_node @CommonForm @kemitchell Also, we are 100% behind the choice of font: @mbutterick's Equity, as seen in practicaltypography.com and in typographyforlawyers.com

just finished a tedious legal form-building project that has me more interested in good legaltech solutions than ever we really need a legal git and a legal react-like system of reusable components for deal contracts

@sehurlburt Working on it!

Want to learn Alloy? Know Alloy but occasionally forget stuff? I wrote a full online reference! alloy.readthedocs.io You can read the announcement here: hillelwayne.com/post/alloydocs/

@dr_c0d3 Because of👇, the OSS components on the language and functionalities will be published under our research programme with SMU. We’re recruiting for use cases (and researchers) at the moment. We’ll PM you about linking up to discuss how we could help. thetechnolawgist.com/2020/03/31/leg…

@legalese Do you have resources to share on your L4 language? Got a renewed interest in law-as-code and checked out your website but could not find link to a description of the DSL. Worked a while ago on CSL (github.com/abailly/csl) but never finished it.

🎤Full-time positions for CS / Complaw research engineers in Singapore ✅ healthcare & benefits ✅ opensource ✅ use-inspired research / no academic silo ✅ well-resourced research programme ✅ @legalese’s @mengwong @wabisabiyo and @SgSMUSOL Details: docs.google.com/document/d/1wZ…

@aimee_maree Thank you so much! We will take everything you said into account and hopefully be able to rev the site in the near future. Bit strapped on webdev at the moment, but who isn’t nowadays?