List view
- No due date•1/1 issues closed
how we look and sound to the rest of the world, sometimes with a very specific audience and deadline in mind.
No due date•0/3 issues closedbusiness goals related to being investor-ready
Overdue by 9 year(s)•Due by June 29, 2016•14/28 issues closedour captable and esop objects should be able to answer any query posed to them.
No due date•0/12 issues closedCertain early adopter investor partners have agreed to work with us to develop templates they can use for their deals.
No due date•2/2 issues closedhelp users understand the things they need to know
No due date•0/3 issues closedtechnical debt accumulates here. fix this for brownie points. also, nontechnical issues that relate to the project/product/company as a whole.
No due date•2/7 issues closedv5.0: round-trip isomorphism from reading English and turning it into the DSL. If the government offers us $50M in funding to do a LegalTech Research institute and they want Computational Linguistics to be a component, and they want to know how we will spend the money, we will say that some of it will be spent on this. Data61 has already done a bit of that. Hack the above using simulated annealing in the opposite direction.
No due date•0/1 issues closedIn the course of a single deal, during negotiations, deltas will appear from the counterparty; maintain a parallel branch that applies those deltas, at the text/string level, to that deal’s paper, even while the master branch templates continue to update. But it would be even cooler if lawyers could submit patches in the high-level DSL.
No due dateCompilation to Ethereum and/or Hyperledger need an R&D team on this.
No due dateVersion 4.0 has a more sophisticated working DSL that supports Natural Language Generation. To get from v3 to v4, the IP-heavy product development R&D will be built with the assistance of academia. We will output to English and at least one other language. Monetization at scale will also happen in v4!
No due date•0/1 issues closedThe DSL is usable by a determined lawyer or law student at a law firm to build its own proprietary templates. It can build the agreements, or we might support a third party consultant who wants to help the law firm build the agreements, but we would prefer not to be supporting the law firm directly on a consulting/services model.
No due date•0/1 issues closedLegalese v3.0 has a working, very simple, DSL to English compiler, with some ugly hardcoded crap in there. We have expressed at least three seed investment agreements in the DSL. The three seed investment agreements compile to working templates. Those working templates are available for actual use by the v1.0 system. The DSL compiler can handle inter-document references and definitions compilation to english compilation to something other than english
No due date•0/5 issues closedv1.3 handles, for any Singapore startup, incorporation NDAs / confidentiality ESOP adding a co-founder employment agreements volunteer agreements seed fundraising round
Overdue by 9 year(s)•Due by July 4, 2016•1/11 issues closedwe need to be able to develop code and templates with the confidence that we haven't broken anything.
Overdue by 9 year(s)•Due by May 13, 2016•0/8 issues closedLegalese v1.0 is the current Google Docs app, whose UI is, well, a Google Spreadsheet. The resolution of a few issues would make the app usable by a determined end-user. It would then become version 1.2. We have a couple of determined end-users willing to work with us toward v1.2. Let's aim for end of April to get these issues resolved.
Overdue by 9 year(s)•Due by April 28, 2016•0/3 issues closedAfter templates have been filled, end-users typically want to make further final edits. Our current workflow outputs to INDD and PDF. It would be nice to output to Google Docs native format. One nit is that Google Docs doesn't currently (late 2014) make it easy to programmatically set headings to be tiered numbers (1.2.3). This may change.
No due date•0/1 issues closedAfter templates have been filled, end-users typically want to make further final edits. Our current workflow outputs to INDD and PDF. It would be nice to output to Microsoft Word. Dragonlaw has put a lot of work into supporting Word as an output format, but their work is not opensource. We may have to reinvent this particular wheel. Maybe we can use commonform's work?
Overdue by 9 year(s)•Due by June 16, 2016•0/2 issues closedBetter UI for end-users than just the raw Google Spreadsheet.
Overdue by 8 year(s)•Due by November 15, 2017•7/37 issues closedThe system understands the semantics of the desired high-level paperwork, and correctly computes the required procedural prerequisites. The CONFIGURATION section of a given spreadsheet automatically populates correctly.
No due date•0/10 issues closedReady for third-party developers to jump in and start being productive. (Initial 3rd-party developers are arjun and lauren.) Developer documentation, etc.
Overdue by 9 year(s)•Due by April 8, 2016•5/17 issues closed