LegalHub: Difference between revisions

Jump to navigation Jump to search
1,271 bytes added ,  25 November 2020
no edit summary
No edit summary
No edit summary
Line 15: Line 15:
For the underlying economic/systems rationale, see: [[ClauseHub: theory]]
For the underlying economic/systems rationale, see: [[ClauseHub: theory]]
==Overview==
==Overview==
*'''A centralised hub''' with free, unlimited access for everyone whether as a user or a contributor.  
===What===
*'''A centralised hub''' with free, unlimited access for everyone whether as a user or a contributor. At first a "legal code" repository that would function as a free open-source template/contract library. So
:*'''Bilateral agreement forms''': confis, engagements, terms of business, etc
:*Legal agreement components: components of the boilerplate, standard forms
:*Market standard utilities: LMA forms, ISDA forms, ICMA, TBMA etc.
:*Legal opinions and advice. Seems controversial, but those who do will get follow on instructions. The first in gets a jump on the rest! NETTING OPINIONS!
===Design principles===
*'''Transparent''': Fully version-controlled, transparent — allow people to take, adapt, copy any iteration.  
*'''Transparent''': Fully version-controlled, transparent — allow people to take, adapt, copy any iteration.  
*'''Permissive, open-architecture''': ''We are hopeless at predicting the future''. Design the architecture to be permissive, developable according to evolving need and use, rather designing for an expected future structure from the outset.  
*'''Don’t be a futurologist''': Design it to solve problems we have ''now'': don’t try to anticipate use cases/design models of the future. We can only get to a design model through evolution: iterative development that meets ''prevailing'' fitness criteria.
*'''Permissive, open-architecture''': Corollary of the above: ''We are hopeless at predicting the future''. Design with a permissive, open architecture. Expect users to develop it as they see fit, according to their evolving need and use, rather designing for an expected future structure from the outset.  
*'''Design and user experience is vital''': Make it intuitively useful and easier than the alternative.
*'''Secure''': It should be fully secure, store no customer data etc. No central repository of sensitive data. Encourage APIs and peer to peer interaction with existing systems.
*'''Digital/creative commons'''. Release all code as open source. Allow/encourage people to use, develop code without limit.
*'''User content''': Permit users to store confidentially, but discourage it. Encourage people to make their content, models freely available. Encourage viewing code as a community resource. This is the [[digital commons]].
*'''Crowd source/reputationm management to surface the best bits''': Use reputation management techniques (use, frequency, user ratings etc) and the network effect to surface most popular forms, segments, components.
===Governance===
*'''Ownership model''': Charity-owned. Model: [https://wikimediafoundation.org/ Wikimedia Foundation].
*'''Ownership model''': Charity-owned. Model: [https://wikimediafoundation.org/ Wikimedia Foundation].
*'''A phased approach''': Recognise that development will be slow. Start with what we have: traditional text-based contracts — how folks do things ''now'', for better or worse — expect it to a fully digital, networked, authenticated smart contracts world if that is the best fit.
===Development model===
*'''Tokenised digital wallets''': No central repository of sensitive data. Allow peer to peer.
*'''Build for the long term''': Recognise that adoption and development will be slow at first. Stick with it.
*'''Direction''': Start with what we have: traditional text-based contracts — how folks do things ''now'', for better or worse — expect it to a fully digital, networked, authenticated smart contracts world if that is the best fit.
:*'''Day''' 1: Purely a text repository to enable people to do more easily what they already do today.  
:*'''Day''' 1: Purely a text repository to enable people to do more easily what they already do today.  
:*'''Day 2''': Online networked interaction: real-time contracting.  
:*'''Day 2''': Online networked interaction: real-time contracting.  
:*'''Day 100''': Expect usage to develop the system iteratively, like an adaptive Ouija board, according to demand.  
:*'''Day 100''': Expect usage to develop the system iteratively, like an adaptive Ouija board, according to demand.  
*'''Give content away'''. Freely. Allow people to use all of your stuff without limit. The more of your stuff is on there the greater the chance it will become a standard. Keep no rights. Claim no [[copyright]]. This is a community resource. This is the [[digital commons]].
*'''Be permissive''': Allow people to copy, derive, refine and improve without limit. Assuming it is version controlled you can keep your model. But allow the world to make it better.
*'''Be permissive''': Allow people to copy, derive, refine and improve without limit. Assuming it is version controlled you can keep your model. But allow the world to make it better.
*'''Get the oppo involved''': Find strategic partners. Especially firms who nominally have conflicting interests to yours. So: competitors; clients; small firms; individuals.
*'''Get the oppo involved''': Find strategic partners. Especially firms who nominally have conflicting interests to yours. So: competitors; clients; small firms; individuals.
*'''Pay for it'''. All of it. Pay a ''lot''. Consider this a down-payment on the savings you will make when you unwind the [[military-industrial complex]] that your outsourcing arrangements have become over 20 years.  
*'''Pay for it'''. All of it. Pay a ''lot''. Consider this a down-payment on the savings you will make when you unwind the [[military-industrial complex]] that your outsourcing arrangements have become over 20 years.  
*'''Look to split the bill, but don’t quibble''': Encourage other strategic partners to pay too, but no penalties if they don’t. The more you all pay, the better the product will be. Pay to make it easy for anyone to engage and use.  
*'''Look to split the bill, but don’t quibble''': Encourage other strategic partners to pay too, but no penalties if they don’t. The more you all pay, the better the product will be. Pay to make it easy for anyone to engage and use.  
*'''Crowd source to surface the best bits''': use reputation management techniques and the network effect to surface most popular forms, segments, components.
*'''A centralised hub''' with free, unlimited access for everyone whether as a user or a contributor.  
*'''A centralised hub''' with free, unlimited access for everyone whether as a user or a contributor.  
*'''Transparent''': Fully version-controlled, transparent — allow people to take, adapt, copy any iteration.  
*'''Transparent''': Fully version-controlled, transparent — allow people to take, adapt, copy any iteration.  

Navigation menu