Terms of Collaboration
These rules describe the framework of collaboration within Philotica. They are deliberately high-level: they set out the philosophy and the main principles, while the details of each collaboration, especially in the operational layer, are settled individually in separate arrangements and agreements. In case of doubt, the agreement prevails.
Two layers of collaboration
Collaboration is divided into two layers.
- The open layer covers discussions, critique, the development of the theoretical foundations, and participation in publications. It is non-commercial and free of charge.
- The operational layer covers work on products: predictive models, foresight tools, and supporting applications. It follows separate rules, including a share of revenue, described below.
Joining
Participation in either layer is open, but subject to approval. A request is made by email or through the discussion space on GitHub, and should include a brief note on who the applicant is, what competencies they bring, and what they would like to work on. For now, the decision to admit is taken by the author and owner of the project. Approval grants access to the working resources appropriate to the given layer.
The open layer
The open layer rests on honest exchange. Critique, including critique that challenges the assumptions, is treated as a contribution, not an attack; falsifiability is a desired quality, not a threat. Participation in publications and the terms of co-authorship are settled separately for each publication, in proportion to the actual contribution. Content produced in this layer remains open, in keeping with the principle of transparency that governs the whole corpus.
The operational layer and revenue sharing
Entry to the operational layer is conditional on a one-off, symbolic joining fee, which will be used to cover the administrative running of the project.
Those who co-create products in the operational layer work on agreed terms that include a share of the revenue from the sale of the products they help to create. This is a share in the outcome, and therefore also in the risk: revenue may not materialise.
The basis on which the share is calculated is set individually in each agreement and may take one of two forms. A share of revenue means a percentage calculated on the value of the product’s sales, before costs are deducted. A share of profit means a percentage calculated on the surplus remaining after the costs of creating and selling the product have been deducted. The choice of form, the size of the percentage, the method of valuing the contribution, and the remaining conditions are set out in the agreement concluded before work begins.
Ownership and rights
The rules of ownership of what is created in the operational layer – including code, models, and tools – and the scope of rights belonging to co-creators, are set out in the individual agreement. A share of revenue is not equivalent to a transfer of ownership of the product, unless the agreement provides otherwise. The openness of the theoretical foundations does not extend automatically to operational products, which may be subject to separate terms.
Ending a collaboration, and disputes
The conditions for ending a collaboration – including what happens to the contribution made and whether the share of revenue is retained or lapses – are set out in the individual agreement. Disputed matters are resolved first through direct conversation, and, if that does not suffice, on the terms provided for in the agreement.
Data and ethics
Work with data, especially with sensitive data in the Human Source Code project, is carried out with respect for privacy and applicable law. The project does not serve to profile individuals. The modelling concerns the human as a species and its mechanisms, not the identification or assessment of specific persons. Detailed obligations regarding the acquisition, storage, and processing of data are set out separately for each undertaking.