Source views: Source JSON(ish) Document views: Document Xray Visual Cicero Print OpenParameters (focus on a Key)   On GitHub: File ~PageRank
Model.Root.NoteThis page presents the key=value pairs, (aka properties) in the order that they are used in rendering. Normally, they are presented in the order of most recent to oldest, as new is usually added at the top. But for a first-time reading, it is helpful to see how the page is built.


CommonAccord is proud of its work with:

Assas Legal Innovation (Paris II)

Some Links:
Ask to join our Discord server email commonaccord@gmail.com.

Latest Activity on GitHub



  • {SSRN.sec}
  • Prose Objects (our most recent work) Prose Objects in /G/
  • {Blog.sec}
  • {CmAbqc.sec}
  • {Codification.sec}
  • {Code-ification.sec}
CmAQuick.secCommonAccord is an initiative to create global codes of legal transacting by codifying and automating legal documents, including contracts, permits, organizational documents, and consents. We anticipate that there will be codes for each jurisdiction, in each language. For international dealings and coordination, there will be at least one "global" code.

CmAbqc.secOne proposed implementation of CommonAccord is a universal bank account that would allow people to manage in a portable account all types of transactions rather than just payments. Examples of how it would look like can be found here: {Bqc.Link}. An interview explaining the concept can be found here (in French - minute 24.21): {BfmPodcast.Link}.
Conference.secWe are co-organizing a conference at MIT Media Lab - May 23-24: Conference Program
SSRN.secWise Contracts: Smart Contracts that Work for People and Machines
Slack.secJoin our Slack group!
Codification.secCodification of legal form documents makes them transparent and continuously improving. It is part of the tradition of legal codification - from Hammurabi through Napoleon, the UCC, the ALI, and Creative Commons. Codification demystifies law and encourages transparency and autonomy.
  • {PDS.sec}
  • {Synchronization.sec}
  • {OnGitHub.sec}
  • {InfoLinks.sec}
  • {CDL.sec}
  • Code-ify.secWe "code-ify" them by treating them like software source code - files in folders shared on GitHub. Code-ifying is neither hard nor complicated. The infrastructure is robust, widely-used, and free. The form documents will converge into legal codes of transacting.
    PDS.secThe legal code is part of a "distributed data model" for transacting. Each participant has their own files stating their legal relationships and transaction histories with each of their partners. The files are private, under their control, shared and handled exactly as they want. In this respect, it is like conventional, custom legal documents done in word-processing by lawyers.
    Synchronization.secParticipants transact by synchronizing files with partners. Synchronization can be done by git, blockchain, or any other method that the parties find satisfactory (even email). Blockchain is a particularly important fit. Blockchain "smart contracts" can automate routine transaction functions while the legal text provides a frame for legal enforceability.
    OnGitHub.secAll of the text, and the little bit of code that brings it together, is on GitHub.
    InfoLinks.sec{ParserByPrimavera.sec} {Peer2Peer.sec} {XrayView.sec} {Slashdot.sec} {Technical.sec}
    ParserByPrimavera.secThis website uses a parser done by Primavera De Filippi of Harvard's Berkman Center.
    Peer2Peer.secIt supports a "DRY," peer-to-peer transaction model, including with blockchain and UMA (pdf). There can be close coupling of "smart contracts" and contract text, enabling "Ricardian" contracts.
    XrayView.secA taste of the "experience" can be seen in this YouTube video.
    Slashdot.secThe vision was articulated in an OSCON interview with Slashdot.
    CDL.secWe are working toward a "{CDL.Link}," a trustee for global legal code. The project is open source. You can contribute: as a lawyer to legal documents, as a coder to our software, as a platform by interfacing with our materials, as a business by using the system, as a benefactor by supporting the effort. Contribute on GitHub or email commonaccord@gmail.com.
    Technical.secThe files can also be expressed as JSON/IPLD.
    SiteLinks.SecSite links:
    • {DocumentsFolder.sec}
    • {Views.List.sec}
    • {PageSource.sec}
    • {MITConference.sec}
    Views.List.secEach file on the site has six "views": Source. E.g., click on "Document".
    PageSource.secThis page is made using the tool ("dog fooding" in tech parlance): Landing Page Source.
    DocumentsFolder.secTop level folder of files.
    SubjectIndex.SecSubject Index of (some) materials.