![[an-asian-woman-scientist-sits-at-table-in-a-chemistry-lab-writing-a-note.png]] #devnote might be a good hashtag for notes related to cooperative development of stuff and services. Members of WikiWe have been discussing development of information and agreement infrastructure for autonomous self-organizing ethical communities since 2021. Out of the chaos, solutions emerge. This year, we have converged around a clearer direction, including adopting Obsidian as a user interface and application-sharing community for the distributed, interlocked networks of markdown documents we envision. Our key project is to apply our ideas and code for the information and governance backbone of the communities we will support. It’s time to work more publicly and collaborate on standards with like-minded people. We are working on a system of policies for handling notes. The system will make documenting and securing productive activity under distributed autonomous control easy, publicly or privately, alone or in cooperation with others. Standards for these policies will make exponential growth possible and eventually generate new forms of durable wealth, fairly distributed without political intervention among those who create and sustain it. That’s the goal. Notes are markdown document objects handled based on their properties. Take #devnotes for example. They can have one or more contributors, are created as #publishable drafts, under a fair share #license. Devnotes can’t be adopted as a binding statement (are not “#signable”), have no #version, allow their #hash to be published in a registry, and so forth. Our document system should work in the background. The details are for developers to work out. We are committed to making social.wikiwe.org a place where users can enjoy the social and business benefits of these systems without having to worry about the details. There will be many more such places, we hope. Such growth can only happen if our document policy system is open source, and so it is. An open-source document policy system is not by itself a money-making project. If someone had already built it, we wouldn’t need to. Luckily, large chunks of the functions we need can be done by existing open source applications. We need only configure the applications and piece them together, ever more effortlessly and usefully. A functioning system is in reach. We could arrive more quickly with more help. Although our standards must be open source, our toolchains, instances and other ethical secrets are trade secrets of license pools under fair share mutual cross-licenses. There are both benefits and costs for insiders. Everyone must contribute something, and everyone gets to decide what they will contribute. Our annual shareholder meeting is January 23rd, and I’m grabbing every share I can. 🗄️ Licensed under [CC BY-SA 4.0](https://creativecommons.org/licenses/by-sa/4.0/) by [WikiWe™](https://wikiwe.org/) Commons • Updated on 2024-02-17