Mahesh Khatri - Founding of New Cloud Cities and Countries
Foundherit - A mix of the founding & an inheriting approach
(For mobile devices, suggest viewing in landscape mode)
Balaji Srinivasan wrote about founding versus inheriting approaches with several examples during the current Covid-19 pandemic.
The choice can be considered similar to the classic 'Exploration versus Exploitation' choices in Reinforcement Learning.
Founders explore. Inheritors exploit.
Inheritors work with known offerings in known environments - The 'Known knowns'.
Whereas founders move from the Known knowns to the Unknown unknowns.
Inheritors have enjoyed a 'Top Down' approach parachuting them immediately to the peak of their institution's Mount Everest without having struggled to the top. They get a great view standing from their vantage point at the top. But they may not have the strength to withstand the storms there. On the contrary, most founders would have climbed their way to the top via a bottoms up approach with their basics & foundations right.
You an found an institution and can also inherit it - This an example where a mix of an inheriting and founding approach has worked. So, it need not be an 'Either / Or ' problem for inheritors and founders. One can be both an inheritor of existing values & best practices for exploitation plus a founder to explore new approaches.
Read-Write Culture instead of Read-Only - Similar to the way object oriented design works, the founder / inventor can design a new class features with it's attributes and actions as well as improve on an existing class. A protocol interaction between the two can be designed. So, both are essential. The founder and the inheritor.
Foundherit - This approach combining the two can be explained in a single combined word - 'foundherit'. This 'foundherit' way could be an approach for the creation of new blockchain based cloud resources. So, how would it look like ?
What can we store on the blockchain besides money information ?
In our cloud city, in addition to money being stored in today's key blockchains, we also store extensive information on our other assets - men / women (people) resources, material (inventory), mortar brick (physical infrastructure), machines, methods, messages (communication), markets & more.
This blockchain data across the three axes - Functional area, Industry vertical / Business Domain Type & Technologies is then abstracted to a generic knowledge repository using a consensus driven taxanomy community based approach for all software deliverables - code & specs.
Another view is shown below. Software deliverables will be contributed to the knowledge repository in a layered fashion by different entities. As an example, my organization has a three decades plus experience in delivering software projects in different technologies, verticals / domains or functions. This organizational knowledge can be contributed to the repository.
The Foundherit approach then extracts knowledge from the generic knowledge repository in terms of the six aspects of knowledge.
What problem is it solving ? Example - The inability to inaccurately measure the value of intangible assets in today's world. As our physical world is getting virtualized rapidly, value is shifting from tangible to intangible assets.
A more detailed view is shown below.
A more detailed view of the intangible assets along with external boundaries is shown below.
Foundherit Summary - A cloud based blockchain knowledge repository created with the software assets contributed by it's constituents (both developers and users). The knowledge extraction would be done using both exploration & exploitation approaches. Benefits such as easy intangible asset measurements can be visualized.
Created on 13th May 2021.
Updated on 23rd June 2021.