How: To Separate Private from Public

The core of CommonAccord is shared materials. Much of legal boilerplate is public - proponents use it repeatedly and make neither proprietary nor confidentiality claim. By being shared and reused, it gets better, and better understood. That is the essence of law.

But of course, the fact that one person has an agreement with some other person, the deal points, particular provisions of the agreement and the volleys in the discussion, may be highly confidential. The line between private and public is complex, shifting and relative. How do we handle this in CommonAccord?

Git provides one solution, and probably provides it in a few different ways. One way is to have separate folders under "Doc/" - for the public stuff and for your private stuff. We show that in primitive form at https://github.com/HazardJ/zed. There we have a (tiny) doc that I sync to my instance, but is not synced to the CommonAccord/Org instance. This is done with a git function called gitignore. Even though I have a folder called /Doc/zed/, when syncing to the main repo, git will ignore it.

Of course, this means that I need a separate git sync profile for each slice of privileges I operate. Undoubted there is a better solution than this in git. LMK.

Beyond git - it is the domain of the OpenID Connect and other rights management systems. Of course, you could go back to email transfers, by pasting the text into the message. As clumsy and risky as that may be, it beats attaching an entire doc to an email, as many of us do now.