refactor: Orientation and belt claim guidance

docs/Belt-Request.md

@@ -12,48 +12,63 @@ Congratulations on making it to the point where you are considering making a bel
 
 Sometimes in our excitement we may have missed some of the signals and cues along the way.
 
-## Immersive Learning Quality Check
+## Insightful Learning Quality Check
 
 Dialog is paramount to reinforce learning and is at the heart of the social connection of the Dojo Community.
 
-Before working through the logistics of the belt claim, please ensure that you have found a Dialog Partner and upacked the concepts thoroughly.  Through this give and take we are challenged to recall what we have learned, test and deepen understanding.  Additionally, we increase awareness to consider how what we learn applies personally and to our home groups.
+Before working through the logistics of the belt claim, please ensure that you have found a Dialog Partner and upacked the concepts thoroughly.  Through this give and take we are challenged to recall what we have learned, test and deepen understanding.  Additionally, we increase awareness to consider how what we learn applies personally and in our social circles.
 
-### Recap and Purposeful Reflection
+### Purposeful Reflection
 
-The pull request will need to include a ***Recap and Purposeful Reflection***.
+The pull request will need to include a ***Purposeful Reflection***.
 
 ***Purposeful reflection illustrates key points of resonation from the content and dialog sessions through the learning progression.***
 
+#### Guidance
+
+* Throw away or delete all of your stored notes
+* Take a moment and center on the *Mission* and *Principles* of the domain
+* Take a moment and center on the belt level competence guidance
+* Time box creating your reflection (at least the first draft) to 30 minutes
+* Describe:
+  * 3 points of resonation
+  * 3 points of struggle and how it was resolved
+  * Overall experience with dialog sessions
+  * Any story of how you have attempted to apply what has been learned
+* Once you have submitted your belt claim, bring it up at the next Dojo Circle to be tested 
+
 #### Belt Claim Review Criteria
 
 During the review of the ***Belt Claim Pull Request*** the following criteria will be considered and labeled accordingly:
 
 * Dialog
   * Sufficient: belt-claim-verified-dialog
     * ***For red and black level, belt claim must be unpacked during a Circle meetup with higher ranking senpai or sensei***
-  * Deficient: belt-claim-insufficient-dialog
-* Recap and Purposeful Reflection
+  * Deficient: belt-claim-repeat-dialog
+* Purposeful Reflection
   * Sufficient: belt-claim-verified-reflection
-  * Deficient: belt-claim-insufficient-reflection
-* YAML formatting:
-  * Sufficient: belt-claim-verified-yaml
-  * Deficient: belt-claim-incorrect-yaml-formatting
+  * Deficient: belt-claim-expand-reflection
+* Live Demo
+  * Sufficient: belt-claim-verified-demo
+  * Deficient: belt-claim-retest-demo 
+* Formatting:
+  * Sufficient: belt-claim-verified-formatting
+  * Deficient: belt-claim-correct-formatting
 
 If a Deficiency Flag (red label) appears, the request will have 30 days to be ironed out.  If that time has passed and the belt claim is not able to clear, it will be closed.  If at a later time the impediments have been cleared a fresh pull request can be submitted or the pull request can be re-opened.
 
 #### New Belt Claim
 
 1. Open a web browser to the Members area of the Dojo GitHub repository:
     * [{{site.repositoryUrl}}/tree/main/docs/_data/members]({{site.repositoryUrl}}/tree/main/docs/_data/members)
-1. Locate and open your file by your ID number
+1. Locate and open your file by your (hyphenated) name
 1. Verify all information is correct, select Edit (top right), and add the new domain level claim request:
 
 ```yaml
 ---
 name: Your Name
+url: LinkedIn Url
 inactive: false
-board-area: Product Engineering
-org-unit: Engineering Department
 belts:
   mindset: green
   agile: green
@@ -66,4 +81,3 @@ belts:
 1. Press "Create pull request"
 1. The pull request will be listed at [{{site.repositoryUrl}}/pulls]({{site.repositoryUrl}}/pulls)
 1. A Dojo Sensei will respond as soon as practicable via email commententary with the pull request
-

docs/Orientation-Request.md

@@ -29,7 +29,7 @@ We center from core principles:
 
 *What Learning and Development paths are available?*
 
-At the top of page, you will see a drop down for Domains. We recommend Mindset and Agile to everyone, however you will also see specific domains for topics like Kubernetes or Observability.
+At the top of page, you will see a drop down for Domains. We recommend Mindset to everyone.
 
 *How do you read the content?*
 
@@ -49,13 +49,32 @@ We want everyone to have access to move through each domain and the ability to e
   * If unsure, then choose Mindset
 * Make a white belt claim as detailed below
 
+### Purposeful Reflection
+
+The pull request will need to include a ***Purposeful Reflection***.
+
+***White level reflection illustrates the motivation for engaging this learning journey.***
+
+#### Guidance
+
+* Take a moment and center on the *Mission* and *Principles* of the domain
+* Take a moment and center on the belt level competence guidance
+* Time box creating your reflection to 30 minutes
+* Once you have submitted your belt claim, bring it up at the next Dojo Circle to introduce yourself 
+
 #### White Belt Claim Review Criteria
 
 During the review of the ***White Belt Pull Request*** the following criteria will be considered and labeled accordingly:
 
-* YAML formatting:
-  * Sufficient: belt-claim-verified-yaml
-  * Deficient: belt-claim-incorrect-yaml-formatting
+* Purposeful Reflection
+  * Sufficient: belt-claim-verified-reflection
+  * Deficient: belt-claim-expand-reflection
+* Live Demo
+  * Sufficient: belt-claim-verified-demo
+  * Deficient: belt-claim-retest-demo 
+* Formatting:
+  * Sufficient: belt-claim-verified-formatting
+  * Deficient: belt-claim-correct-formatting
 
 If a Deficiency Flag (red label) appears, the request will have 30 days to be ironed out. If that time has passed and the belt claim is not able to clear, it will be closed. If at a later time the impediments have been cleared a fresh pull request can be submitted or the pull request can be re-opened.
 
@@ -70,30 +89,28 @@ If a Deficiency Flag (red label) appears, the request will have 30 days to be ir
     * From the *docs* folder, navigate to the *_data* folder
     * From the *_data* folder, navigate to the *members* folder
 1. On the right side of the screen select "Create new file" from the "Add file" dropdown
-1. Name the file with your ID number in lowercase and with a yaml extension
+1. Name the file with your name (hyphenated) in lowercase and with a yaml extension
 1. Back in the GitHub tab, add the following template data in the "Edit new file" section
 
 ```yaml
 ---
 name: TODO-Name
+url: TODO-LinkedIn-Url
 inactive: false
-board-area: TODO-Board-Area
-org-unit: TODO-Organizational-Unit
 belts:
   TODO-domain: TODO-level
 ```
 
 1. Replace all of the TODO values appropriately
-    * name, board-area and org-unit should match what is in your People Profile from the opened tab
+    * name and url suggested to match LinkedIn
     * domain and level are the belt claim request you are making
 1. Verify things look correct, similar to the following for example:
 
 ```yaml
 ---
 name: Your Name
+url: TODO-LinkedIn-Url
 inactive: false
-board-area: Product Engineering
-org-unit: Engineering Department
 belts:
   mindset: white
 ```