Merge pull request #1230 from julian-molina/develop

Contribution: Governance Definitions
2021-06-26 17:19:51 +02:00
commit 9f362e89d6
@@ -1,13 +1,30 @@
 {
    "type": "Asset Class",
    "definition": {
-        "text": "This node acts as a folder helping organize the different assets of a certain Assets hierarchy. It can receive votes, and when it does, it distribute them among it's children.",
-        "updated": 1622986499181
+        "text": "The Asset Class node is an organizational device used to group Asset nodes in arbitrary arrangements. The node may receive Weight Votes. When it does, votes are evenly distributed among offspring nodes.",
+        "updated": 1624720632494
    },
    "paragraphs": [
+        {
+            "style": "Block",
+            "text": "Content",
+            "updated": 1624720655011
+        },
        {
            "style": "Text",
-            "text": "Right click and select the pencil button to enter edit mode."
+            "text": "You may direct Weight Votes to an Asset Class node when you intend to support the whole class, including all assets within."
+        },
+        {
+            "style": "Text",
+            "text": "Asset Class nodes may take incoming Weight Votes. When you cast Weight Votes on an Asset Class node, votes cascade evenly to all offspring nodes."
+        },
+        {
+            "style": "Block",
+            "text": "Configuration"
+        },
+        {
+            "style": "Title",
+            "text": "Configuration"
        }
    ]
 }
@@ -1,13 +1,35 @@
 {
    "type": "Asset",
    "definition": {
-        "text": "An Asset is any artifact that belongs to the project. It can be a piece of software, a configuration, a plugin, some marketing material, a social media account, etc. Users votes on assets to influence their relative weight between each other. Those weight will then influence how many token will be given to the contributors who built or mantain that asset.",
-        "updated": 1622986734958
+        "text": "An Asset is an artifact, mostly in a digital format, that belongs to a Project. It may be a code file, a documentation or tutorial page, an image, a video, a social media account or even a post, marketing collateral, and more. To incentivize the production and maintenance of Assets, the node may receive Weight Votes. It may also receive Contributor Claims from Contributors involved in their production and maintenance.",
+        "updated": 1624709807952
    },
    "paragraphs": [
+        {
+            "style": "Block",
+            "text": "Content",
+            "updated": 1624709759877
+        },
        {
            "style": "Text",
-            "text": "Right click and select the pencil button to enter edit mode."
+            "text": "You may cast Weight Votes on individual Asset nodes to incentivize the improvement, development, and maintenance of the said feature.",
+            "updated": 1624709824891
+        },
+        {
+            "style": "Text",
+            "text": "If you are involved in the development or maintenance of the said asset, you may place an Asset Contribution Claim and rally the Community to support your claim so that you may be compensated for your work."
+        },
+        {
+            "style": "Block",
+            "text": "Configuration"
+        },
+        {
+            "style": "Title",
+            "text": "Configuration"
+        },
+        {
+            "style": "Text",
+            "text": ""
        }
    ]
 }
@@ -1,13 +1,61 @@
 {
    "type": "Assets",
    "definition": {
-        "text": "These hierarchies define the different assets Superalgos as a project has accumulated over time. Assets could be anything tangible and not only software modules. ",
-        "updated": 1622986422593
+        "text": "The Assets hierarchy defines the structure of assets that a project is composed of. Any digital component of a Project may be characterised as an asset, including code files, stylesheets, images, documentation pages, tutorial pages, and so on. Assets, like Features, need to be created and maintained, thus their creation and maintenance must be incentivized. ",
+        "updated": 1624708951019
    },
    "paragraphs": [
+        {
+            "style": "Block",
+            "text": "Content",
+            "updated": 1624709007419
+        },
        {
            "style": "Text",
-            "text": "Right click and select the pencil button to enter edit mode."
+            "text": "Defining assets at the project level is an excellent way to atomize the description of a project. This level of granularity allows multiple groups of Contributors to take charge of clearly delimited components, which is crucial to developing, evolving, and maintaining a vast project through massive collaboration."
+        },
+        {
+            "style": "Text",
+            "text": "The hierarchy features Asset Class nodes, an organizational device, and Asset nodes, the representation of actual assets. Both types of nodes may accept incoming Weight Votes but only Asset nodes may accept Contributor Claims."
+        },
+        {
+            "style": "Success",
+            "text": "A crucial feature of this hierarchy is the Install Assets feature available both at the top-level of the hierarchy, and at the Asset Class node level.",
+            "updated": 1624709216096
+        },
+        {
+            "style": "Title",
+            "text": "Install Missing Assets",
+            "updated": 1624709536566
+        },
+        {
+            "style": "Text",
+            "text": "Both the Assets node and the Asset Class nodes support the Install Assets command available on the menu. Because Assets map digital files shipping with the system, the Install Assets feature is designed to map files on disk into a hierarchical structure of nodes below the node where the Install Assets command is run. In the resulting structure of nodes, Asset Class nodes represent folders, and Asset nodes represent files."
+        },
+        {
+            "style": "Text",
+            "text": "To run the command, you must configure the path you wish to map."
+        },
+        {
+            "style": "Text",
+            "text": "For example:"
+        },
+        {
+            "style": "Json",
+            "text": "{\n\"folderPath\": \"Root/UI\"\n}",
+            "updated": 1624709553788
+        },
+        {
+            "style": "Text",
+            "text": "Using the above configuration, the Install Assets command creates a Superalgos Asset Class node (the root of the Superalgos folder), and the UI Asset Class node as an offspring node. Then, the contents of the UI folder are mapped as offspring of the UI Asset Class node."
+        },
+        {
+            "style": "Block",
+            "text": "Configuration"
+        },
+        {
+            "style": "Title",
+            "text": "Configuration"
        }
    ]
 }
@@ -1,13 +1,30 @@
 {
    "type": "Feature Class",
    "definition": {
-        "text": "This node helps organize features in hierarchical way. This node my receive votes, and when it does, it will pass them to their children.",
-        "updated": 1622986135148
+        "text": "The Feature Class node is an organizational device used to group features in arbitrary arrangements. The node may receive Weight Votes. When it does, votes are evenly distributed among offspring nodes.",
+        "updated": 1624708539877
    },
    "paragraphs": [
+        {
+            "style": "Block",
+            "text": "Content",
+            "updated": 1624708560605
+        },
        {
            "style": "Text",
-            "text": "Right click and select the pencil button to enter edit mode."
+            "text": "You may direct Weight Votes to a Feature Class node when you intend to support the whole class, including all features within."
+        },
+        {
+            "style": "Block",
+            "text": "Configuration"
+        },
+        {
+            "style": "Title",
+            "text": "Configuration"
+        },
+        {
+            "style": "Text",
+            "text": ""
        }
    ]
 }
@@ -1,13 +1,31 @@
 {
    "type": "Feature",
    "definition": {
-        "text": "A Feature is a functionality of the Superalgos software that matches a single use case. Users can vote on features to increase their relative weight to other features. These weight will ultimatelly influence how many tokens are given to the people implementing or mantaining these features.",
-        "updated": 1622986275998
+        "text": "A Feature is the capacity of the software to perform tasks required by a specific use case. We describe features so that users may direct Weight Votes to express which of them are the most valuable. This is how users may decide which features to incentivize, both in terms of maintenance and development.",
+        "updated": 1624708747036
    },
    "paragraphs": [
+        {
+            "style": "Block",
+            "text": "Content",
+            "updated": 1624708766414
+        },
        {
            "style": "Text",
-            "text": "Right click and select the pencil button to enter edit mode."
+            "text": "You may cast Weight Votes on individual Feature nodes to incentivize the improvement, development, and maintenance of the said feature."
+        },
+        {
+            "style": "Text",
+            "text": "If you are involved in the development or maintenance of the said feature, you may place a Feature Contribution Claim and rally the Community to support your claim so that you may be compensated for your work.",
+            "updated": 1624708816194
+        },
+        {
+            "style": "Block",
+            "text": "Configuration"
+        },
+        {
+            "style": "Title",
+            "text": "Configuration"
        }
    ]
 }
@@ -1,13 +1,18 @@
 {
    "type": "Features",
    "definition": {
-        "text": "As a software, Superalgos has features. This type hierarchies is used to describe the software's features with the objective to allow users to vote on those features and by doing so influencing how many tokens will receive contributors that mantain those features or, if the feature is yet to be added, the token it will receive whoeven contribute it to the project.",
-        "updated": 1622986032804
+        "text": "The Features hierarchy defines existing software features, or features in the wish list, yet to be developed. When Weight Votes are directed at existing features, the tokens allocated to the said features are distributed among Contributors maintaining the code. When Weight Votes are directed at features that don’t yet exist, then the tokens incentivize the creation and contribution of the said features.",
+        "updated": 1624708469928
    },
    "paragraphs": [
+        {
+            "style": "Block",
+            "text": "Content",
+            "updated": 1624708488815
+        },
        {
            "style": "Text",
-            "text": "Right click and select the pencil button to enter edit mode."
+            "text": "Use your Weight Votes to influence the direction of development of specific Feature nodes, or sets of features represented by Feature Class nodes."
        }
    ]
 }
@@ -1,13 +1,30 @@
 {
    "type": "Pool Class",
    "definition": {
-        "text": "This node is like a folder. It facilitates the organization of the Pools structure. Votes received at this node will be split evenly on it's children.",
-        "updated": 1622985466839
+        "text": "The Pool Class node is an organizational device used to arrange Pool nodes in suitable hierarchical structures.",
+        "updated": 1624707077159
    },
    "paragraphs": [
+        {
+            "style": "Block",
+            "text": "Content",
+            "updated": 1624707110607
+        },
        {
            "style": "Text",
-            "text": "Right click and select the pencil button to enter edit mode."
+            "text": "Their main purpose is to help organize Pool nodes in the most appropriate manner."
+        },
+        {
+            "style": "Block",
+            "text": "Configuration"
+        },
+        {
+            "style": "Title",
+            "text": "Configuration"
+        },
+        {
+            "style": "Text",
+            "text": ""
        }
    ]
 }
@@ -1,13 +1,54 @@
 {
    "type": "Pool",
    "definition": {
-        "text": "A Pool represents the highest level container of tokens.  They are used to route tokens to specific hierarchies via references. Users votes on pools to influence how many tokens will be routed and then distributed at the referenced hierarchy.",
-        "updated": 1622985663794
+        "text": "A Pool represents a high-level container of Token Rewards. The node is used to receive Weight Votes and to route tokens to other hierarchies via references. Contributors may direct Weight Votes to Pool nodes to affect how many tokens will be routed to and distributed at the referenced hierarchy.",
+        "updated": 1624707171824
    },
    "paragraphs": [
+        {
+            "style": "Block",
+            "text": "Content",
+            "updated": 1624707200475
+        },
        {
            "style": "Text",
-            "text": "Right click and select the pencil button to enter edit mode."
+            "text": "Pool nodes may be nested in arbitrary levels and may be arranged under Pool Class nodes or directly under other Pool nodes. When they reference another hierarchy, the definition of the organization of the Project continues in the said hierarchy."
+        },
+        {
+            "style": "Text",
+            "text": "When you direct Weight Votes into a Pool node, you are effectively increasing the weight of the pool in the eventual distribution of tokens by the number of votes you are directing to it. The Pool will get a portion of the tokens assigned to the Pools hierarchy in proportion to the total number of incoming Weight Votes. If a Pool has no incoming Weight Votes, it gets zero tokens."
+        },
+        {
+            "style": "Text",
+            "text": "Pool nodes with incoming Weight Votes display the following pieces of information:"
+        },
+        {
+            "style": "List",
+            "text": "Number of Votes: the total number of Weight Votes directed at the node."
+        },
+        {
+            "style": "List",
+            "text": "Number of Tokens Awarded: the total number of tokens the Pool gets for the votes it has."
+        },
+        {
+            "style": "List",
+            "text": "Weight: The total weight of the Pool is expressed as a percentage of the total Weight Votes directed at the whole hierarchy."
+        },
+        {
+            "style": "Callout",
+            "text": "Notice that Pool nodes participate in the pool of tokens assigned to the Pools hierarchy it belongs to. The aforementioned Weight value is in relation to the said hierarchy, and not necessarily to the top-level Superalgos Pools hierarchy."
+        },
+        {
+            "style": "Text",
+            "text": "We mentioned that Pool nodes may pass on Token Rewards to other hierarchies which, in turn, further break up the definitions of where tokens go to. We’ll explore those hierarchies in the next few pages."
+        },
+        {
+            "style": "Block",
+            "text": "Configuration"
+        },
+        {
+            "style": "Title",
+            "text": "Configuration"
        }
    ]
 }
@@ -1,13 +1,85 @@
 {
    "type": "Pools",
    "definition": {
-        "text": "At this hierarchy is where Token distribution starts. All the tokens to be distributed at the next release start flowing from here down this hierarchy, until they reach individual pools. Nodes will received tokens acording to the votes / weight each one of them have.",
-        "updated": 1622985349549
+        "text": "This hierarchy breaks up the definition of a Project in specific areas. Each area is a Pool that may be incentivized by the Community. Users collectively decide how many tokens will be allocated to each Pool using Weight Votes. The sum of Weight Votes in each Pool determines the proportion of tokens each pool gets from the total of tokens allocated to the release.",
+        "updated": 1624706823509
    },
    "paragraphs": [
+        {
+            "style": "Block",
+            "text": "Content",
+            "updated": 1624706897078
+        },
        {
            "style": "Text",
-            "text": "Right click and select the pencil button to enter edit mode."
+            "text": "In essence, this hierarchy is used to determine how the tokens allocated to each release will be distributed.",
+            "updated": 1624706911544
+        },
+        {
+            "style": "Text",
+            "text": "To produce unequivocal definitions, the hierarchy uses two specific resources:"
+        },
+        {
+            "style": "List",
+            "text": "On one hand, the data structure represented by the hierarchy itself describes the organization of the Project, fragmenting specific incumbencies into specific distribution pools. This allows the granular allocation of tokens."
+        },
+        {
+            "style": "List",
+            "text": "On the other hand, each Pool may accept Weight Votes from User Profiles. This is how the Community determines how many tokens will go to each distribution pool."
+        },
+        {
+            "style": "Callout",
+            "text": "At the same time, a Pool may reference other types of hierarchies, namely Positions, Assets, and Features. These hierarchies take the granularity of the definition to a whole new level! But we’ll go into those later on!"
+        },
+        {
+            "style": "Text",
+            "text": "In addition, there is a third resource characteristic to the Pool Hierarchy. Each Pool may reference a separate Pools hierarchy so that the definitions may continue on a separate hierarchy, which may be included as a plugin in the same or in a separate Plugin Workspace."
+        },
+        {
+            "style": "Text",
+            "text": "This resource allows fragmenting the definitions of how the project is organized, for readability, organizational, and logistical reasons:"
+        },
+        {
+            "style": "List",
+            "text": "a single hierarchy describing the whole Superalgos Project and every other project within would grow too big and be cumbersome to deal with;"
+        },
+        {
+            "style": "List",
+            "text": "each hierarchy may be defined and maintained by different people or teams;"
+        },
+        {
+            "style": "List",
+            "text": "each hierarchy may be better visualized in different workspaces in which they may interact with other definitions; etc."
+        },
+        {
+            "style": "Subtitle",
+            "text": "Superalgos Pools"
+        },
+        {
+            "style": "Text",
+            "text": "The Superalgos Pools hierarchy is where everything starts, meaning that it is the top-level hierarchy kickstarting the definition of the whole Project."
+        },
+        {
+            "style": "Text",
+            "text": "Many of the Pool nodes defined in this hierarchy link to further definitions on other hierarchies. "
+        },
+        {
+            "style": "Text",
+            "text": "The configuration of the top-level node in the hierarchy determines how many tokens will be distributed in the release."
+        },
+        {
+            "style": "Block",
+            "text": "Configuration",
+            "updated": 1624706986873
+        },
+        {
+            "style": "Title",
+            "text": "Configuration",
+            "updated": 1624706995696
+        },
+        {
+            "style": "List",
+            "text": "tokens: the total number of tokens to be distributed in the next Distribution Event. Only the top-level Superalgos Pools hierarchy requires this configuration."
        }
    ]
 }
@@ -1,13 +1,26 @@
 {
    "type": "Position Class",
    "definition": {
-        "text": "This node is like a folder that helps organize the Positions hierarchies. It can receive votes, and when it does, it distribute them among it's children.",
-        "updated": 1622987556789
+        "text": "The Position Class node is an organizational device used to group positions in arbitrary arrangements. The node may receive Weight Votes. When it does, votes are evenly distributed among offspring nodes.",
+        "updated": 1624707573898
    },
    "paragraphs": [
+        {
+            "style": "Block",
+            "text": "Content",
+            "updated": 1624707587709
+        },
        {
            "style": "Text",
-            "text": "Right click and select the pencil button to enter edit mode."
+            "text": "You may direct Weight Votes to a Position Class node when you intend to support the whole class, including all positions within."
+        },
+        {
+            "style": "Block",
+            "text": "Configuration"
+        },
+        {
+            "style": "Title",
+            "text": "Configuration"
        }
    ]
 }
@@ -1,13 +1,26 @@
 {
    "type": "Position",
    "definition": {
-        "text": "A position is a role a user can play within the project. Noone holds a position. Users can make claims that they spent time performing a role and they need community confirmation via getting votes at their claims, in order for them to receive tokens for playing that role. The amount of tokens to receive is also influenced by how the community voted the position itself and how much weight that position acquired relative to others.",
-        "updated": 1622987462908
+        "text": "A Position node represents a role within the project’s organization. However, unlike traditional organizations, positions within Superalgos are open, in the sense that any Contributor may assume any position at any point. If you spend time working in a position, you may produce a Position Claim and rally the Community to support your claim so that you may earn tokens allocated to the said position.",
+        "updated": 1624707652230
    },
    "paragraphs": [
+        {
+            "style": "Block",
+            "text": "Content",
+            "updated": 1624707677299
+        },
        {
            "style": "Text",
-            "text": "Right click and select the pencil button to enter edit mode."
+            "text": "You may direct Weight Votes to a Position node to support the particular position."
+        },
+        {
+            "style": "Block",
+            "text": "Configuration"
+        },
+        {
+            "style": "Title",
+            "text": "Configuration"
        }
    ]
 }
@@ -1,13 +1,22 @@
 {
    "type": "Positions",
    "definition": {
-        "text": "These hierarchies are used to define different position or roles contributors can take at the project organization chart. Once defined, users can claim having spent time at an specific position or role and when those claims are supported by votes, they receive  tokens according to the position relative weight.",
-        "updated": 1622987207926
+        "text": "The Positions hierarchy is used to define different positions or roles that Contributors may assume in the project’s organization chart. Contributors may claim to have worked in a specific position or role. When a Position Contribution Claim is supported by a Position Claim Vote, the Contributor receives tokens according to the position’s relative weight.",
+        "updated": 1624707433425
    },
    "paragraphs": [
+        {
+            "style": "Block",
+            "text": "Content",
+            "updated": 1624707461136
+        },
        {
            "style": "Text",
-            "text": "Right click and select the pencil button to enter edit mode."
+            "text": "Positions hierarchies acquire Token Rewards from Pool nodes referencing the said hierarchy. These are the tokens available for distribution among the different positions in the hierarchy. "
+        },
+        {
+            "style": "Text",
+            "text": "Any Position and Position Class node within the hierarchy may receive Weight Votes to determine how the Token Rewards in the hierarchy is distributed. How many tokens each Position is awarded depends on the relative weight of the position determined by the number of Weight Votes each position receives from Contributors."
        }
    ]
 }
@@ -0,0 +1,24 @@
+{
+    "topic": "Governance Definitions",
+    "pageNumber": "1",
+    "type": "Introduction to Governance Definitions",
+    "definition": {
+        "text": "For Contributors to participate in governance, the project must be thoroughly defined, as it is these definitions that may accept votes and claims from Contributors.",
+        "updated": 1624706736435
+    },
+    "paragraphs": [
+        {
+            "style": "Text",
+            "text": "The Governance Project is designed in a way that allows describing the project in a highly granular fashion. This is one of the features that enable a massive collaboration, as it allows different people to get involved with very specific areas of the project.",
+            "updated": 1624706744817
+        },
+        {
+            "style": "Text",
+            "text": "Usually, governance definitions are produced by top contributors leading significant areas of the project. They are best suited to define the areas they lead, as they have profound knowledge of the existing infrastructure and the development roadmap."
+        },
+        {
+            "style": "Text",
+            "text": "Regular contributors tend to interact with these definitions to cast their votes and raise their claims."
+        }
+    ]
+}
@@ -0,0 +1,54 @@
+{
+    "topic": "Governance Definitions",
+    "pageNumber": "2",
+    "type": "Pools Hierarchy",
+    "definition": {
+        "text": "The top-level definitions involve the definition of pools that intervene in the distribution of tokens.",
+        "updated": 1624720022127
+    },
+    "paragraphs": [
+        {
+            "style": "Include",
+            "text": "Governance->Node->Pools->Definition",
+            "updated": 1624719914461
+        },
+        {
+            "style": "Include",
+            "text": "Governance->Node->Pools->Content"
+        },
+        {
+            "style": "Include",
+            "text": "Governance->Node->Pools->Configuration",
+            "updated": 1624710324091
+        },
+        {
+            "style": "Title",
+            "text": "Pool Classes Nodes",
+            "updated": 1624710545392
+        },
+        {
+            "style": "Include",
+            "text": "Governance->Node->Pool Class->Definition"
+        },
+        {
+            "style": "Include",
+            "text": "Governance->Node->Pool Class->Content",
+            "updated": 1624710496543
+        },
+        {
+            "style": "Title",
+            "text": "Pool Nodes",
+            "updated": 1624710516456
+        },
+        {
+            "style": "Include",
+            "text": "Governance->Node->Pool->Definition",
+            "updated": 1624710569674
+        },
+        {
+            "style": "Include",
+            "text": "Governance->Node->Pool->Content",
+            "updated": 1624710576964
+        }
+    ]
+}
@@ -0,0 +1,53 @@
+{
+    "topic": "Governance Definitions",
+    "pageNumber": "3",
+    "type": "Positions Hierarchy",
+    "definition": {
+        "text": "Projects may define positions that people may assume while contributing to the project.",
+        "updated": 1624719589021
+    },
+    "paragraphs": [
+        {
+            "style": "Include",
+            "text": "Governance->Node->Positions->Definition",
+            "updated": 1624719628603
+        },
+        {
+            "style": "Include",
+            "text": "Governance->Node->Positions->Content"
+        },
+        {
+            "style": "Title",
+            "text": "Position Class Nodes",
+            "updated": 1624719765396
+        },
+        {
+            "style": "Include",
+            "text": "Governance->Node->Position Class->Definition",
+            "updated": 1624719782927
+        },
+        {
+            "style": "Include",
+            "text": "Governance->Node->Position Class->Content",
+            "updated": 1624719787155
+        },
+        {
+            "style": "Title",
+            "text": "Position Nodes"
+        },
+        {
+            "style": "Include",
+            "text": "Governance->Node->Position->Definition",
+            "updated": 1624719793612
+        },
+        {
+            "style": "Include",
+            "text": "Governance->Node->Position->Content",
+            "updated": 1624719798497
+        },
+        {
+            "style": "Text",
+            "text": ""
+        }
+    ]
+}
@@ -0,0 +1,44 @@
+{
+    "topic": "Governance Definitions",
+    "pageNumber": "4",
+    "type": "Features Hierarchy",
+    "definition": {
+        "text": "Each project may define Features, so that the Community may incentivize desired directions of development.",
+        "updated": 1624720133681
+    },
+    "paragraphs": [
+        {
+            "style": "Include",
+            "text": "Governance->Node->Features->Definition",
+            "updated": 1624720223930
+        },
+        {
+            "style": "Include",
+            "text": "Governance->Node->Features->Content"
+        },
+        {
+            "style": "Title",
+            "text": "Feature Class Nodes"
+        },
+        {
+            "style": "Include",
+            "text": "Governance->Node->Feature Class->Definition"
+        },
+        {
+            "style": "Include",
+            "text": "Governance->Node->Feature Class->Content"
+        },
+        {
+            "style": "Title",
+            "text": "Feature Nodes"
+        },
+        {
+            "style": "Include",
+            "text": "Governance->Node->Feature->Definition"
+        },
+        {
+            "style": "Include",
+            "text": "Governance->Node->Feature->Content"
+        }
+    ]
+}
@@ -0,0 +1,44 @@
+{
+    "topic": "Governance Definitions",
+    "pageNumber": "5",
+    "type": "Assets Hierarchy",
+    "definition": {
+        "text": "Projects may produce definitions at the atomic level, specifying each asset that is or needs to be created and maintained.",
+        "updated": 1624720456614
+    },
+    "paragraphs": [
+        {
+            "style": "Include",
+            "text": "Governance->Node->Assets->Definition",
+            "updated": 1624720546750
+        },
+        {
+            "style": "Include",
+            "text": "Governance->Node->Assets->Content"
+        },
+        {
+            "style": "Title",
+            "text": "Asset Class Nodes"
+        },
+        {
+            "style": "Include",
+            "text": "Governance->Node->Asset Class->Definition"
+        },
+        {
+            "style": "Include",
+            "text": "Governance->Node->Asset Class->Content"
+        },
+        {
+            "style": "Title",
+            "text": "Asset Nodes"
+        },
+        {
+            "style": "Include",
+            "text": "Governance->Node->Asset->Definition"
+        },
+        {
+            "style": "Include",
+            "text": "Governance->Node->Asset->Content"
+        }
+    ]
+}