Co-founder at Citizen Code, noah@citizencode.io
Here is the early operating agreement draft for a lightweight legal entity to support an open innovation business model. It is intended to solve structural challenges faced by incubators, freelancer collaborators, investors, and open innovation contributors. It strives to be both innovative and legally compliant.
For maximum usability, these legal documents are hereby licensed under the Creative Commons CC0 public domain dedication: http://creativecommons.org/publicdomain/zero/1.0
The text in this README is licensed as a Creative Commons CC-BY 4.0 license. You may adapt and distribute it with attribution to the contributors listed in the Attribution section. https://creativecommons.org/licenses/by/4.0/
Opening a Github issue is a great way to give us feedback on your desires and concerns. We will be integrating this feedback into future revisions or variations of the contract. If Github issues are not your style you can send an email to noah@citizencode.io.
The Open Innovation Business Model
Open Innovation Business Model Benefits
The Dynamic Organization engages in a limited set of actions
The Dynamic Org never needs to deal directly with fiat currency and so no fiat bank account is needed. It only deals in the royalty tokens that it creates. Royalties can be distributed directly to royalty token holders via a smart contract using Bitcoin, Ethereum, or other payment software.
Contributions are filtered by a core team. The governance agreement defines how decision making authority and budgets are delegated to core members. It also defines iterative agreement amendment to adapt to the unknown.
The license dynamically allocates tokens backed by the value of royalty revenue. This is done without the necessity of debt, investment, or legal filings (looking into this). This provides resilience to entrepreneurs as well as those without access to capital in the developing world, collapsed economies, and recessions. These tokens can be issued and tracked transparently on a blockchain with a tool like Swarmbot.
Backed by the value of the IP and the IP Royalty stream.
Using open source software as an example, here's how royalties are distributed. Individuals or companies pay a royalty fee for revenue made by hosting, selling, or distributing licensed software. Open source contributors, product managers, designers, and marketers receive a percentage of royalties in proportion to the work they do. This work is tracked through the distribution of tokens on a ledger managed by the organization. The tokens are brought into existence by the contract in the repository.
Research by Swarm.fund on implementing Distributed Collaborative Organizations (DCOs) by using lightweight unincorporated associations as a basis for token issuance indicates a promising direction. Simply signing an agreement specified in the license brings an unincorporated association into existence without the requirement of filing paperwork with the government. The jurisdiction the association is formed in is of particular concern and is the subject of further investigation regarding limitation of liability, the holding of assets, and tax ramifications.
Although the license is targeted to be created simply by people signing an agreement (ie unincorporated assocation), the license should be suitable for conversion into an LLC operating agreement. This allows the agreement to function as a founders agreement if a different legal structure is required.
Ideally open source contributors would be free to trade tokens for money if they choose. This potentially enables compatibility with new SEC crowd funding rules that go into effect on January 29th, 2016. Relatedly, investors who want to further the development of software can pay contributors to make contributions in exchange for a portion of the contribution tokens that contributors earn. Although it does not bypass accredited investor rules, this avoids the need to pay money directly to the organization. Cash for royalty token negotiations can occur at the edge of the organization which may avoid the necessity of the organization opening a bank account.
The first version of the license is intended to be suitable for software development with just git repository tracking. However automated services can also track dynamic issuance such as Citizen Code's SwarmBot and Enspiral's CoBudget.
If you are committed to using this approach for your product, investment, or service offering let noah@citizencode.io know! Your early enthusiasm encourages us to continue iterating.
Many thanks (and no blame) for pioneering and helping develop the concepts explored here.
Attribution goes to:
This is an experimental license. This should not be construed as legal advice.