ProseObject version of the delegation_letter. #2
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Should have been more careful and done a .gitignore.
…ty.Xnum} to delegation_letter.md
… Term/0.md to all diff on future work.
…subheadings, more time-based organization. The text remains exactly the same as 2021-08-25.md.
…wn the base so git will show the differences.)
…nding "Counterparts and Notices" to separate sections for the two. Moving the Demo doc example to the aerated version.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
ProseObjects are a more git-appropriate way to open source legal documents and components. They are also a nice Ricardian fit with Code. This pull-request puts the delegation_letter.md into ProseObject format. It also provides a Demo example and an exploded variant on "Term" provision (with subheadings and some reorganization, but the same text PO/Sec/Term/0.md). It also has a free-standing version of the Notice provision, which probably should not be grouped with Counterparts. (/PO/Sec/Notice/0.md). "Notice" should be better structured and also should include blockchain-native infrastructures for notices. (Digitally-efficient notice provisions would be a game changer in much of contracting.). Demos at http://www.commonaccord.org/index.php?action=list&file=G/crypto-governance/PO/