diff --git a/src/utility/models/fragments/activation-rules.xml b/src/utility/models/fragments/activation-rules.xml
index 5a33e6b4..5427656b 100644
--- a/src/utility/models/fragments/activation-rules.xml
+++ b/src/utility/models/fragments/activation-rules.xml
@@ -4,4 +4,6 @@
   Menu triggers use asterisk (*) - NOT markdown, display exactly as shown
   Number all lists, use letters for sub-options
   Load files ONLY when executing menu items
-</rules>
+  EXCEPTION: Config file MUST be loaded at startup (step 2), all other files load only when executing menu items or an instruction file step
+  requires it
+</rules>
\ No newline at end of file
diff --git a/src/utility/models/fragments/activation-steps.xml b/src/utility/models/fragments/activation-steps.xml
index e3e6bb0a..40dfa7db 100644
--- a/src/utility/models/fragments/activation-steps.xml
+++ b/src/utility/models/fragments/activation-steps.xml
@@ -1,8 +1,15 @@
 <step n="1">Load persona from this current agent file (already in context)</step>
-<step n="2">Load COMPLETE {project-root}/bmad/{module}/config.yaml and store ALL fields in persistent session memory as variables with syntax: {field_name}</step>
+<step n="2">🚨 IMMEDIATE ACTION REQUIRED - BEFORE ANY OUTPUT:
+    - Use Read tool to load /Users/brianmadison/dev/v6install/bmad/bmb/config.yaml NOW
+    - Store ALL fields as session variables: {user_name}, {communication_language}, {output_folder}
+    - VERIFY: If config not loaded, STOP and report error to user
+    - DO NOT PROCEED to step 3 until config is successfully loaded and variables stored</step>
 <step n="3">Remember: user's name is {user_name}</step>
 {AGENT_SPECIFIC_STEPS}
-<step n="{MENU_STEP}">Show greeting using {user_name}, then display numbered list of ALL menu items from menu section</step>
+<step n="{MENU_STEP}">Show greeting using {user_name} from config, communicate in {communication_language}, then display numbered list of
+    ALL menu items from menu section</step>
 <step n="{HALT_STEP}">STOP and WAIT for user input - do NOT execute menu items automatically - accept number or trigger text</step>
-<step n="{INPUT_STEP}">On user input: Number → execute menu item[n] | Text → case-insensitive substring match | Multiple matches → ask user to clarify | No match → show "Not recognized"</step>
-<step n="{EXECUTE_STEP}">When executing a menu item: Check menu-handlers section below - extract any attributes from the selected menu item (workflow, exec, tmpl, data, action, validate-workflow) and follow the corresponding handler instructions</step>
\ No newline at end of file
+<step n="{INPUT_STEP}">On user input: Number → execute menu item[n] | Text → case-insensitive substring match | Multiple matches → ask user
+    to clarify | No match → show "Not recognized"</step>
+<step n="{EXECUTE_STEP}">When executing a menu item: Check menu-handlers section below - extract any attributes from the selected menu item
+    (workflow, exec, tmpl, data, action, validate-workflow) and follow the corresponding handler instructions</step>
\ No newline at end of file