Interlinking a couple of threads through this safe Collaborative commons/data marketplace (genetic therapy/algorithm) conversation path into an Integrated Summary & Logistical Integration Process flow …
1. CommunityLink Safenetwork Public Data Utility - Setting up a Commons dWeb Blog
As described in my response to David’s “true decentralised price network which enables automatic price seeking on a global flat playing field comment, the DWeb commons blog describes a possible safe.commons, CommunityLink data marketplace model as a starting point for further discussion to support this outcome. As we have agreed the dWeb blog article is about my experience in setting up the dweb commons blog site so others can learn from it.
2. What is it? My response to David’s “true decentralised price network vision/objective
Introduces Ocean protocol decentralised marketplace-exchange types/benchmarks which we can learn from for a safe data commons/marketplace level playing field/automatic pricing vision.
The objective (onboarding to an autonomous network) is to enable self-organising citizens, Community or industries to access, customise deploy their own “CDC QBOS” Data Council product (ultimately ISO quality approved). incorporating a across the safenetwork. The data council objective is to provide a level playing field/automatic pricing/model for community members to access their own Care Capacity system based on their own Council defined standards to support transition to the Rivkin post capitalism model.
The CDC QBOS system is being designed around an existing ISO Approved Quality management system and templated Data Council governance system which has already been implemented in a specific industry with a national mandate. The framework basically exists supported by a project office to sit behind the dweb/safe.commons to manage documentation and deployment, so business systems not a big step… just add the tech . Next step for me is the try and learn how to set up a dweb site which is pretty scary for a tech neanderthal 
and a better understanding of a true decentralised price network requirements
**3. Project Commonsense Commons central project office/knowledge repository/Meta index
What we are all doing is completely new so we all need to learn from each other and together as we go forward. Working on the complimentary documentation to commercialisation will enable us to understand each other’s requirements to focus/progress y/our deliverables.
It helps also if we have a common outcome to focus on to align our thinking, narrative and agree a common language/story, documentation, system /IT actions etc. This is where I think the safe://commons design path, which by necessity must incorporate safedrive as a decentralised file system, safegit/plume & dweb components as part of Quality Business Operating system (QBOS) to enable a mutual AGI strategy, could assist. This context could be the best way to define what I need to learn on the tech front and help you identify suitable tasks in the short term! I will need to PM my thoughts here due to confidentialities. Also happy to help with any opportunities you feel are key.
As we move forward we will need a way to share and manage safe://commons documentation. To assist this need I have established a Commons Central Library which will sit directly behind safe://commons(sense) with the following structure (which we can progressively improve)
i. Commons Central Directory - which is where we can place/manage our (commercial & technical) working docs and where they can be deployed as pre-defined product outcomes which are set up as a “Curated set of working docs & links that persist”. NB a “repeatable framework of terms and mechanism” is a key ODI definition of a data trust.
ii. Commons Central Binary Library – where we can put technical documentation associated with establishment and management of the binary library David has spoken of previously. If I understand correctly could this be a place where we provide a “permissioned centralised view/access” to a safegit (decentralised IP) library catalogue to assist overall network learning & ability for any Community to access improvements easily?
In the first instance we could use this to assist us and others who contribute.
In this 2nd version of your architecture diagram I have inserted the aligned UBER AI preso “Multidimensional Neural networks” slide and a number of smaller diagrams numbered 1-10 which flesh out existing or add key architecture components/requirements which as you say need to be evolved e.g. indexes to underpin a decentralised search app/ultimate path
See summary of diagrams 1-10 highlighted in the previous slide
5. Wealthcare Capacity Demand Management (WCCDM)
@Nadia Great description of the Maidsafe project methodology!
Your simplified “i.e. why did we over/underestimate” description is very similar to the “human resource allocation optimisation” or “care capacity ” methodology which I believe is key to achieving the path to the "true decentralised price network/global flat playing field” safe vision and in time underpin the design and use of genetic algorithms on safe.
I note the Marketing Update comment re the plan to steer in the direction of focus primarily on DApp developers. We are looking at a safe WCCDM dApp Epic, story & tasks design to leverage off this existing opportunity.
The objective is to create a generic WCCDM dApp template in context of the safe commons/data marketplace/public utility goal, broken down into chunks i.e. 3 project sections, with each section broken into smaller chunk projects or project workstreams and phases. So hopefully we can reach a point where we can simply compare our Epic Stories to implement.
6. Project Commonsense WCCDM Co Phase 0 method to bring the ULB/neuroevolutionary thinkers around safe to create our open AI community equivalent
ommonsense Project framework to meet this need requires 3 project sections ….
Project section 1 – Build the Foundations
Project section 2 – Commercial
Project section 3 – Community
each one an Epic story.
Some brief thoughts to give a little background to the core issues for each…