Eve Maler (@xmlgrrl) contemplating enterprise engagement with prose objects, wrote:

I would guess that making sure this system works would be a combination of a) suitably sophisticated and complex parameterization that meets real-world use cases and b) a “stack” of base prose that does right by individuals before it ever gets to organizations, but then (c) is still appealing to orgs and the corporate contract-editing tools they use.
That thought meets mine in the middle.
(c) Integration with Contract Management Systems:
The one thing the entire community (global, business, govt, advocacy, everybody) is missing is a way to codify legal.  So the clear win for all end-users (from Adrian’s autonomous patients to GE) is “prose objects” hosted and improved by collaboration on Github (and also published by IPFS or equivalent).  Use of publicly-available prose objects with clear “provenance” (@findthomas) will:
  1. accelerate negotiation via common starting points (see the purpose of IACCM Contract Principles introduction);
  2. give the clarity benefits of stable legal provisions (the basic function of legal “codification” and the great advantage of codified legal domains over uncodified domains);
  3. allows weaker, busier, less diligent parties to benefit from the sophistication and even the leverage of experts and peers.

Even sophisticated contract management systems (CRM) don’t cause general legal codification.  For organizations that are happy with their CRM, they might use prose objects “merely” as sources for legal text.  They might use them as legal forms, or might interface to them for more functionality.   Enterprises might find that they want to contribute to prose objects in order to influence the direction of legal standards.  They might do that by publishing prose objects on their own sites, or (better) by forking on Github, or (even better) through organizations such as the IACCM and legal groups.

(b) Individual Perspective:

While it is possible to address the problem of legal standards from the perspective of the individual, and ultimately a major impact will be (and should be) to empower the smaller actor (individual, company, country – almost all of us are small sometimes) it seems likely to me that the legal materials will originate from the more systemic partner.  For instance, the UMA Legal materials, the IACCM Contract Principles or the Y Combinator SAFE Notes.  It will be found that legal documents are not terribly complicated – despite the apparent endless variations and length.  The issues recur and improve with recursion.  The purpose of legal terms is to facilitate good behavior by both parties, to enable the relationship, to reduce the cost of inter-personal collaboration (Coase).  The smaller party will no longer be alone.

(a) Parameters
The choice of parameters is very important.  The easiest way to be sure to select parameters that cover the critical issues is to use existing forms – forms that persons (organizations) actually use.  “Accordifying” an existing form immediately pops-out the terms that the actors thought important.  Iteration will validate (or invalidate) their choices and find others.  The type-less model of CommonAccord, where all elements are parameters, means that we don’t get stuck with early choices.  Iteration will reveal the truth of what actors actually need.
For those organizations that directly use the prose object format for negotiation and signature, adoption leads to a true P2P data model, compatible with access-based approaches such as UMA and with GDPR and PSD2.
Eve adds: