Ti | = | Planning - Making "Yes" Better |
1.sec | = | Planning happens differently depending on the circumstances, but let's schematize. Let's presume the parties have found one another and now want to increment their relationship by, for instance, agreeing to keep one another's confidences, lend some money, benefit from some service. |
2.0.sec | = | They need to decide on documents - to "self-legislate" the "law of the parties": |
2.1.sec | = | Find a range of paradigms, practically speaking some documents, set of documents or precedent transactions |
2.2.sec | = | Evaluate separately and collectively adopt |
2.3.sec | = | Bridge differences |
2.4.sec | = | Sign |
2.5.sec | = | Launch performance |
2. | = | [G/Z/ol/s5] |
2.secs | = | {2.secs;and} |
3.sec | = | The law of the parties is the focus of CommonAccord. This is based on text and collaboratively developed by lawyers. For parties, selecting the right one mostly depends on social knowledge, following their lawyer's recommendation, or that of reputed experts or their peers. The coding community shows how to collaborate on text efficiently. That can be combined with traditional legal methods of model docs, codification and commentary. Big data methods can also help. |
4.sec | = | Sign and Perform are the domain of the blockchain and other methods. |
= | [G/Z/ol/s4] |