Fixed Codebase Risk

docs/practices/Planning-And-Management/Delegation.md

@@ -11,6 +11,7 @@ practice:
   aka: 
    - "Task Assignment"
    - "Empowerment"
+   - "Hierarchy"
    - "Authority Delegation"
    - "Responsibility Allocation"
   mitigates:

docs/risks/Complexity-Risk/Connectivity.md

@@ -80,7 +80,7 @@ Secondly, it's not apparent to **i** that **j** _even exists_: we have hidden th
 
 ![Modularisation and Hierarchy](/img/generated/risks/complexity/modularisation.svg)
 
-The trade-off of modularisation/hierarchy is shown in the above diagram, and it's our third tool for battling [Codebase Risk](/tags/Codebase-Risk).  
+The trade-off of modularisation/hierarchy is shown in the above diagram, and it's our third tool for battling [Complexity Risk](/tags/Complexity-Risk).  
 
 But we don't just see this in software, it's everywhere in our lives:  societies, business, and living organisms all use this technique.  For example in our bodies we have:
 

src/images/generated/estimating/planner/refactoring.adl

@@ -5,7 +5,7 @@
          xslt:template="/public/templates/risk-first/risk-first-template.xsl">
    <group id="4" style="--kite9-layout: down; ">
       <mitigated id="37">
-         <risk class="communication" />
+         <risk class="communication" id="communication" />
       </mitigated>
       <description id="4-1" style="text-align: center; ">50% Of Users Don't
 				Complete The Premium-Tier
@@ -20,12 +20,4 @@
       <risk class="goal">50K Subscribers By Q4
       </risk>
    </group>
-   <align id="5-0" style="--kite9-direction: right;">
-      <from id="5-0-0" reference="communication"/>
-      <to id="5-0-1" reference="3"/>
-   </align>
-   <align id="5-1" style="--kite9-direction: right;">
-      <from id="5-1-0" reference="3"/>
-      <to id="5-1-1" reference="2"/>
-   </align>
 </diagram>

src/images/generated/risks/complexity/modularisation.adl

@@ -13,17 +13,20 @@
          <risk class="complexity"/>
       </mitigated>
       <label id="id_16">
-        Internal Model
+        Systems in which there are multiple paths of
+        communication and control are often complex.
       </label>
    </container>
    <group style="--kite9-layout: down; --kite9-horizontal-align: left;">
-      <action id="a1">Modularisation, Hierarchy</action>
+      <action id="a1">Delegation, Hierarchy</action>
    </group>
    <group style="--kite9-layout: down;">
       <container id="d1" style="--kite9-layout: right; --kite9-sizing: maximize;">
          <risk class="communication" id="r1"/>
          <label id="id_16-ar">
-          Attendant Risks
+          Introducing hierarchical ownership simplifies the 
+          design, but introduces new opportunities for
+          Communication Risk.
         </label>
       </container>
    </group>