LegalHub: Difference between revisions
Amwelladmin (talk | contribs) No edit summary Tags: Mobile edit Mobile web edit |
Amwelladmin (talk | contribs) No edit summary |
||
| Line 1: | Line 1: | ||
{{a|devil|}}Bringing GitHub to the [[legal eagles]]. Credit to '''Graeme Johnston''' of https://www.juralio.com for the nub of this idea. | {{a|devil|}}Bringing GitHub to the [[legal eagles]]. Credit to '''Graeme Johnston''' of https://www.juralio.com for the nub of this idea. See: [[ClauseHub: theory]] | ||
So the idea is very very formative, but in a nutshell it is like an open-source GitHub, only for [[legal code]] — that is, legal text. ''Words''. The challenge is to keep the simplicity but not throw away the opportunities provided by the network and the digital. | So the idea is very very formative, but in a nutshell it is like an open-source GitHub, only for [[legal code]] — that is, legal text. ''Words''. The challenge is to keep the simplicity but not throw away the opportunities provided by the network and the digital. | ||
| Line 6: | Line 6: | ||
For example: publish the components of a basic [[confidentiality agreement]]. | For example: publish the components of a basic [[confidentiality agreement]]. | ||
===Phase (a): publish=== | ===Phase (a): publish=== | ||
| Line 20: | Line 19: | ||
Phased approach with a series of successive goals, which depend on the last one being achieved. | Phased approach with a series of successive goals, which depend on the last one being achieved. | ||
{{sa}} | |||
*[[ClauseHub: theory]] | |||
*[[Legal services delivery]] | |||
Revision as of 13:28, 21 November 2020
|
|
Bringing GitHub to the legal eagles. Credit to Graeme Johnston of https://www.juralio.com for the nub of this idea. See: ClauseHub: theory
So the idea is very very formative, but in a nutshell it is like an open-source GitHub, only for legal code — that is, legal text. Words. The challenge is to keep the simplicity but not throw away the opportunities provided by the network and the digital.
- STP, authentication, workflow
- Validation/authentication of text (i.e. if text is downloaded can it be corrupted??) — the code is law
For example: publish the components of a basic confidentiality agreement.
Phase (a): publish
- Establish platform
- Publish in downloadable templates in word or PDF format and say to everyone "have at it. help yourself." Sponsor then as XYZ content, open source. Standard agreements — NDAs etc.
- Grant pre-approved users (with low threshold) ability to do likewise
- Develop navigation methodology - metadata tags, Boolean search etc.
- Reputation management for templates
Phase (b): modularise
- Strip back and break out all the boilerplate - governing law, reps and warranties etc.
basically make an online, simple, doc assembly tool - free for anyone to use and play around with as they wish.
Phased approach with a series of successive goals, which depend on the last one being achieved.