Source views: Source JSON(ish) on GitHub (VSCode)   Doc views: Document (&k=r00t): Visual Print Technical: OpenParameters Xray
  1. CommonAccord allows more efficient document handling than conventional systems. It expresses documents as leafs on a tree, attached to twigs on branches that trace back to trunks of legal code, rooted in legal practice and experience. ("Block that metaphor.") The innovation is a uniquely simple approach to text "objects." By simplifying programming, both law and IT are demystified.
  2. Documents in CommonAccord's "Cmacc" format enable:
    1. Legal actors to get on the same page. Via model document projects and contributions from interested parties, it is possible to codify areas of law in the same iterative way that software is developed.
    2. Parties to negotiate from public models.
    3. Efficient management of the legal function. Creation of new documents is a matter of adding leafs on existing branches or twigs. This makes it easy to supervise, to prepare reports, to identify trends and anomalies.
    4. Efficient operation of marketplaces. An ideal market allows participants to transact by negotiating only deal points. "Objects" allow any transaction to serve as a precedent for others. By eliminating the cost of reproducing a precedent, patterns of use can sharpen and become quasi-standards.
    5. Decentralization of decision-making. Reducing the opacity of regulations, law, and IT reduces "transaction costs" (Coase) and the advantages of centralization.
  3. The CommonAccord document model is compatible with new peer-based transacting platforms such as blockchain, and perhaps necessary for their extension to the full range of relationships. When combined with access systems such as UMA (user-managed-access), it provides a complete, simple, open source system of automation. Because these systems are built with strong encryption and open source scrutiny they can be more secure than legacy infrastructure.