@salesforce/afv-skills 1.7.2 → 1.7.4

package/skills/developing-agentforce/assets/patterns/open-gate-routing.agent

@@ -1,26 +1,26 @@
 # Open Gate Routing Pattern
-# 3-variable state machine for auth-gated topic routing with LLM bypass
+# 3-variable state machine for auth-gated subagent routing with LLM bypass
 #
 # ★ When To Use This Pattern:
-#   - Multiple protected topics require authentication before access
-#   - You want to bypass the LLM topic selector when a gate topic holds focus
+#   - Multiple protected subagents require authentication before access
+#   - You want to bypass the LLM subagent selector when a gate subagent holds focus
 #   - Users should be redirected to auth, then automatically returned to their
-#     original intended topic after authentication completes
+#     original intended subagent after authentication completes
 #   - You need an EXIT_PROTOCOL to reset state when users change intent
 #
 # ★ Key Insight (Zero Credit Bypass):
-#   When open_gate is set, before_reasoning in the topic_selector
+#   When open_gate is set, before_reasoning in the agent_router
 #   deterministically routes via "transition to" — the LLM never reasons.
 #   This saves credits on every turn the gate holds focus.
 #
 # ★ The 3 Variables:
-#   open_gate    — Which topic currently holds focus ("null" = none)
-#   next_topic   — Deferred destination after auth completes
+#   open_gate    — Which subagent currently holds focus ("null" = none)
+#   next_subagent   — Deferred destination after auth completes
 #   authenticated — Whether the user has passed authentication
 #
 # ★ EXIT_PROTOCOL:
-#   Any topic can reset open_gate to "null" when the user changes intent.
-#   This releases the gate lock and returns control to the LLM topic selector.
+#   Any subagent can reset open_gate to "null" when the user changes intent.
+#   This releases the gate lock and returns control to the LLM subagent router.
 #
 # ★ Related Patterns:
 #   - Latch Variable (SKILL.md) — simpler 1-variable version, no auth gate
@@ -34,55 +34,56 @@
 variables:
 	# ... standard linked variables ...
 	open_gate: mutable string = "null"
-		description: "Which topic currently holds focus (null = LLM decides)"
-	next_topic: mutable string = ""
+		description: "Which subagent currently holds focus (null = LLM decides)"
+	next_subagent: mutable string = ""
 		description: "Deferred destination after authentication completes"
 	authenticated: mutable boolean = False
 		description: "Whether the user has passed authentication"
 
 # ─────────────────────────────────────────────────────────────────────
-# TOPIC SELECTOR (Entry Point)
+# SUBAGENT ROUTER (Entry Point)
 # When open_gate is set, bypasses LLM entirely (zero credit cost)
 # ─────────────────────────────────────────────────────────────────────
-start_agent topic_selector:
-	description: "Routes to topics — deterministic bypass when open_gate is set"
+start_agent agent_router:
+	label: "Subagent Router"
+	description: "Routes to subagents — deterministic bypass when open_gate is set"
 
 	before_reasoning:
-		# ★ GATE CHECK: If a topic holds focus, bypass LLM entirely
+		# ★ GATE CHECK: If a subagent holds focus, bypass LLM entirely
 		if @variables.open_gate == "protected_workflow":
-			transition to @topic.protected_workflow
+			transition to @subagent.protected_workflow
 		if @variables.open_gate == "account_management":
-			transition to @topic.account_management
+			transition to @subagent.account_management
 		if @variables.open_gate == "authentication_gate":
-			transition to @topic.authentication_gate
+			transition to @subagent.authentication_gate
 
 	reasoning:
 		instructions: ->
 			| You are a customer service agent.
-			| Route the customer to the appropriate topic:
+			| Route the customer to the appropriate subagent:
 			| - Order status, returns, or shipping → protected workflow
 			| - Account settings or profile changes → account management
 			| - General questions → general inquiry
 		actions:
-			go_protected: @utils.transition to @topic.protected_workflow
-			go_account: @utils.transition to @topic.account_management
-			go_general: @utils.transition to @topic.general_inquiry
+			go_protected: @utils.transition to @subagent.protected_workflow
+			go_account: @utils.transition to @subagent.account_management
+			go_general: @utils.transition to @subagent.general_inquiry
 
 # ─────────────────────────────────────────────────────────────────────
 # PROTECTED WORKFLOW (Requires Authentication)
 # Checks auth state, redirects to auth gate if needed, locks focus if authed
 # ─────────────────────────────────────────────────────────────────────
-topic protected_workflow:
+subagent protected_workflow:
 	description: "Handles order status, returns, and shipping (requires authentication)"
 
 	before_reasoning:
 		# ★ AUTH CHECK: Redirect unauthenticated users to auth gate
 		if @variables.authenticated == False:
-			set @variables.next_topic = "protected_workflow"
+			set @variables.next_subagent = "protected_workflow"
 			set @variables.open_gate = "authentication_gate"
-			transition to @topic.authentication_gate
+			transition to @subagent.authentication_gate
 
-		# ★ FOCUS LOCK: Keep gate open so topic selector bypasses LLM
+		# ★ FOCUS LOCK: Keep gate open so subagent router bypasses LLM
 		set @variables.open_gate = "protected_workflow"
 
 	reasoning:
@@ -98,25 +99,25 @@ topic protected_workflow:
 				set @variables.order_result = @outputs.status
 
 			# ★ EXIT_PROTOCOL: User changed intent — release gate
-			exit_to_menu: @utils.transition to @topic.exit_protocol
+			exit_to_menu: @utils.transition to @subagent.exit_protocol
 
 	after_reasoning:
 		# Logging or cleanup after each turn (optional)
-		set @variables.last_topic = "protected_workflow"
+		set @variables.last_subagent = "protected_workflow"
 
 # ─────────────────────────────────────────────────────────────────────
-# ACCOUNT MANAGEMENT (Second Protected Topic)
-# Demonstrates the pattern scales to N protected topics
+# ACCOUNT MANAGEMENT (Second Protected Subagent)
+# Demonstrates the pattern scales to N protected subagents
 # ─────────────────────────────────────────────────────────────────────
-topic account_management:
+subagent account_management:
 	description: "Handles account settings and profile changes (requires authentication)"
 
 	before_reasoning:
 		# ★ AUTH CHECK: Same pattern as protected_workflow
 		if @variables.authenticated == False:
-			set @variables.next_topic = "account_management"
+			set @variables.next_subagent = "account_management"
 			set @variables.open_gate = "authentication_gate"
-			transition to @topic.authentication_gate
+			transition to @subagent.authentication_gate
 
 		# ★ FOCUS LOCK
 		set @variables.open_gate = "account_management"
@@ -135,14 +136,14 @@ topic account_management:
 				set @variables.update_result = @outputs.success
 
 			# ★ EXIT_PROTOCOL: User changed intent — release gate
-			exit_to_menu: @utils.transition to @topic.exit_protocol
+			exit_to_menu: @utils.transition to @subagent.exit_protocol
 
 # ─────────────────────────────────────────────────────────────────────
 # AUTHENTICATION GATE
-# Handles auth flow, then routes back via next_topic
+# Handles auth flow, then routes back via next_subagent
 # ─────────────────────────────────────────────────────────────────────
-topic authentication_gate:
-	description: "Verifies customer identity before allowing access to protected topics"
+subagent authentication_gate:
+	description: "Verifies customer identity before allowing access to protected subagents"
 
 	before_reasoning:
 		# ★ FOCUS LOCK: Hold gate open during auth flow
@@ -165,54 +166,54 @@ topic authentication_gate:
 	after_reasoning:
 		# ★ POST-AUTH ROUTING: If authenticated, route to deferred destination
 		if @variables.authenticated == True:
-			if @variables.next_topic == "protected_workflow":
+			if @variables.next_subagent == "protected_workflow":
 				set @variables.open_gate = "protected_workflow"
-				transition to @topic.protected_workflow
-			if @variables.next_topic == "account_management":
+				transition to @subagent.protected_workflow
+			if @variables.next_subagent == "account_management":
 				set @variables.open_gate = "account_management"
-				transition to @topic.account_management
+				transition to @subagent.account_management
 
 # ─────────────────────────────────────────────────────────────────────
 # EXIT PROTOCOL (Resets Gate State)
-# Clears open_gate so LLM topic selector regains control
+# Clears open_gate so LLM subagent router regains control
 # ─────────────────────────────────────────────────────────────────────
-topic exit_protocol:
-	description: "Resets gate state and returns to topic selector"
+subagent exit_protocol:
+	description: "Resets gate state and returns to subagent router"
 
 	before_reasoning:
 		# ★ RELEASE GATE: Clear all gate state
 		set @variables.open_gate = "null"
-		set @variables.next_topic = ""
-		transition to @topic.topic_selector
+		set @variables.next_subagent = ""
+		transition to @subagent.agent_router
 
 	reasoning:
 		instructions: ->
 			| Redirecting you to the main menu.
 
 # ─────────────────────────────────────────────────────────────────────
-# GENERAL INQUIRY (Unprotected Topic)
-# Demonstrates that not every topic needs gating
+# GENERAL INQUIRY (Unprotected Subagent)
+# Demonstrates that not every subagent needs gating
 # ─────────────────────────────────────────────────────────────────────
-topic general_inquiry:
+subagent general_inquiry:
 	description: "Handles general questions that do not require authentication"
 
 	reasoning:
 		instructions: ->
 			| Help the customer with general questions.
-			| No authentication is needed for this topic.
+			| No authentication is needed for this subagent.
 			|
 			| If the customer needs help with orders or account settings,
 			| let them know they will need to verify their identity first.
 		actions:
-			go_protected: @utils.transition to @topic.protected_workflow
-			go_account: @utils.transition to @topic.account_management
+			go_protected: @utils.transition to @subagent.protected_workflow
+			go_account: @utils.transition to @subagent.account_management
 
 # ═════════════════════════════════════════════════════════════════════
 # ARCHITECTURE DIAGRAM
 # ═════════════════════════════════════════════════════════════════════
 #
 #                       ┌─────────────────────┐
-#                       │   topic_selector    │
+#                       │   agent_router    │
 #                       │   (start_agent)     │
 #                       │                     │
 #                       │ before_reasoning:   │
@@ -237,7 +238,7 @@ topic general_inquiry:
 #   │ before_reasoning: lock gate          │
 #   │ reasoning: verify identity           │
 #   │ after_reasoning:                     │
-#   │   if auth → route via next_topic     │
+#   │   if auth → route via next_subagent     │
 #   └──────────────────────────────────────┘
 #
 # ═════════════════════════════════════════════════════════════════════
@@ -246,11 +247,11 @@ topic general_inquiry:
 #
 # User says: "I want to check my order status"
 #
-# Step 1: topic_selector
+# Step 1: agent_router
 #   open_gate = "null" → LLM reasons → routes to protected_workflow
 #
 # Step 2: protected_workflow.before_reasoning
-#   authenticated = False → set next_topic = "protected_workflow"
+#   authenticated = False → set next_subagent = "protected_workflow"
 #   → set open_gate = "authentication_gate"
 #   → transition to authentication_gate
 #
@@ -261,7 +262,7 @@ topic general_inquiry:
 #   authenticated = True
 #
 # Step 5: authentication_gate.after_reasoning
-#   authenticated = True, next_topic = "protected_workflow"
+#   authenticated = True, next_subagent = "protected_workflow"
 #   → set open_gate = "protected_workflow"
 #   → transition to protected_workflow
 #
@@ -272,7 +273,7 @@ topic general_inquiry:
 # Step 7: User says "actually, never mind"
 #   → LLM selects exit_to_menu action
 #   → exit_protocol.before_reasoning: open_gate = "null"
-#   → transition to topic_selector (LLM regains control)
+#   → transition to agent_router (subagent router regains control)
 #
 # ═════════════════════════════════════════════════════════════════════
 # PATTERN COMPARISON

package/skills/developing-agentforce/assets/patterns/procedural-instructions.agent

@@ -73,9 +73,9 @@ variables:
 language:
 	default_locale: "en_US"
 
-start_agent topic_selector:
-	label: "Topic Selector"
-	description: "Routes to topics with procedural data loading"
+start_agent agent_router:
+	label: "Subagent Router"
+	description: "Routes to subagents with procedural data loading"
 
 	actions:
 		# Data loading actions
@@ -147,11 +147,11 @@ start_agent topic_selector:
 			| - Account questions
 
 		actions:
-			go_orders: @utils.transition to @topic.order_status
-			go_cases: @utils.transition to @topic.support_cases
-			go_account: @utils.transition to @topic.account_help
+			go_orders: @utils.transition to @subagent.order_status
+			go_cases: @utils.transition to @subagent.support_cases
+			go_account: @utils.transition to @subagent.account_help
 
-topic order_status:
+subagent order_status:
 	label: "Order Status"
 	description: "Check order status with lazy loading"
 
@@ -172,7 +172,7 @@ topic order_status:
 
 	reasoning:
 		instructions: ->
-			# ★ LAZY LOADING: Only fetch orders when user enters this topic
+			# ★ LAZY LOADING: Only fetch orders when user enters this subagent
 			if @variables.orders_loaded == False:
 				run @actions.load_orders
 					with contact_id=@variables.ContactId
@@ -194,9 +194,9 @@ topic order_status:
 		actions:
 			get_details: @actions.get_tracking_details
 				with order_id=@variables.recent_order_id
-			back: @utils.transition to @topic.topic_selector
+			back: @utils.transition to @subagent.agent_router
 
-topic support_cases:
+subagent support_cases:
 	label: "Support Cases"
 	description: "Review support cases with lazy loading"
 
@@ -225,18 +225,18 @@ topic support_cases:
 				| - Return to the main menu
 
 		actions:
-			back: @utils.transition to @topic.topic_selector
+			back: @utils.transition to @subagent.agent_router
 			escalate: @utils.escalate
 				description: "Transfer to support specialist"
 
-topic account_help:
+subagent account_help:
 	label: "Account Help"
 	description: "Account questions - customer data already loaded"
 
 	reasoning:
 		instructions: ->
 			# ★ DATA ALREADY AVAILABLE - no loading needed
-			# Customer data was loaded in topic_selector
+			# Customer data was loaded in agent_router
 			| Account Information:
 			| Name: {!@variables.customer_name}
 			| Tier: {!@variables.customer_tier}
@@ -245,7 +245,7 @@ topic account_help:
 			| What would you like to know about your account?
 
 		actions:
-			back: @utils.transition to @topic.topic_selector
+			back: @utils.transition to @subagent.agent_router
 
 # ★ Insight: Procedural vs Declarative Actions
 #
@@ -267,7 +267,7 @@ topic account_help:
 #   - Result: Efficient, context-aware agents
 
 # ★ Performance Benefits:
-#   - Fetch only what's needed per topic
+#   - Fetch only what's needed per subagent
 #   - Avoid loading all data upfront
 #   - Reduce API calls for simple conversations
 #   - Better response times

package/skills/developing-agentforce/assets/patterns/prompt-template-action.agent

@@ -60,7 +60,7 @@ variables:
 language:
 	default_locale: "en_US"
 
-start_agent topic_selector:
+start_agent agent_router:
 	label: "Content Generator"
 	description: "Routes to content generation options"
 
@@ -70,12 +70,12 @@ start_agent topic_selector:
 			| 1. Personalized daily schedule
 			| 2. Professional email
 			|
-			| Route to the appropriate topic.
+			| Route to the appropriate subagent.
 		actions:
-			go_schedule: @utils.transition to @topic.schedule_generation
-			go_email: @utils.transition to @topic.email_generation
+			go_schedule: @utils.transition to @subagent.schedule_generation
+			go_email: @utils.transition to @subagent.email_generation
 
-topic schedule_generation:
+subagent schedule_generation:
 	label: "Schedule Generation"
 	description: "Generate personalized daily schedules"
 
@@ -123,9 +123,9 @@ topic schedule_generation:
 				with "Input:timezone"=@variables.user_timezone
 				set @variables.generated_schedule = @outputs.promptResponse
 
-			back: @utils.transition to @topic.topic_selector
+			back: @utils.transition to @subagent.agent_router
 
-topic email_generation:
+subagent email_generation:
 	label: "Email Generation"
 	description: "Generate professional emails"
 
@@ -168,7 +168,7 @@ topic email_generation:
 				with "Input:tone"=...
 				set @variables.generated_email = @outputs.promptResponse
 
-			back: @utils.transition to @topic.topic_selector
+			back: @utils.transition to @subagent.agent_router
 
 # ★ Insight: Prompt Template Integration Checklist
 #

package/skills/developing-agentforce/assets/patterns/system-instruction-overrides.agent

@@ -9,13 +9,13 @@
 #
 # ★ Key Insight:
 #   - System block defines BASE behavior (always applies)
-#   - Topic instructions can OVERRIDE or EXTEND system behavior
+#   - Subagent instructions can OVERRIDE or EXTEND system behavior
 #   - Use conditionals in reasoning to dynamically adjust tone
 #   - Variables can control instruction branches
 #
 # ★ Important Limitation:
 #   - The system: block itself cannot use conditionals or variables
-#   - Dynamic behavior must be implemented in topic reasoning
+#   - Dynamic behavior must be implemented in subagent reasoning
 #
 # This is a COMPLETE template - customize for your use case
 
@@ -59,9 +59,9 @@ language:
 	additional_locales: ""
 	all_additional_locales: False
 
-start_agent topic_selector:
-	label: "Topic Selector"
-	description: "Routes to appropriate topic based on user tier"
+start_agent agent_router:
+	label: "Subagent Router"
+	description: "Routes to appropriate subagent based on user tier"
 
 	# ★ Use before_reasoning to set up context-based variables
 	before_reasoning:
@@ -108,12 +108,12 @@ start_agent topic_selector:
 			if @variables.agent_mode == "formal":
 				| Use formal language. Address customer as Sir/Madam.
 
-			| Route the customer to the appropriate topic.
+			| Route the customer to the appropriate subagent.
 
 		actions:
-			go_orders: @utils.transition to @topic.orders
-			go_billing: @utils.transition to @topic.billing
-			go_support: @utils.transition to @topic.support
+			go_orders: @utils.transition to @subagent.orders
+			go_billing: @utils.transition to @subagent.billing
+			go_support: @utils.transition to @subagent.support
 				available when @variables.business_hours == True
 
 	actions:
@@ -134,13 +134,13 @@ start_agent topic_selector:
 					description: "True if in business hours"
 			target: "flow://Check_Business_Hours"
 
-topic orders:
+subagent orders:
 	label: "Order Management"
 	description: "Handle order inquiries with tier-appropriate service"
 
 	reasoning:
 		instructions: ->
-			# ★ Tier-specific instructions carry through to subtopics
+			# ★ Tier-specific instructions carry through to subagents
 			if @variables.customer_tier == "vip":
 				| This is a VIP customer. Expedite all order requests.
 				| Offer free shipping upgrades proactively.
@@ -149,9 +149,9 @@ topic orders:
 			| Look up order status, process changes, or handle returns.
 
 		actions:
-			back: @utils.transition to @topic.topic_selector
+			back: @utils.transition to @subagent.agent_router
 
-topic billing:
+subagent billing:
 	label: "Billing Support"
 	description: "Handle billing with appropriate authority levels"
 
@@ -171,12 +171,12 @@ topic billing:
 			| Help the customer understand their bill and resolve issues.
 
 		actions:
-			back: @utils.transition to @topic.topic_selector
+			back: @utils.transition to @subagent.agent_router
 			escalate: @utils.escalate
 				description: "Transfer to billing specialist"
 				available when @variables.customer_tier == "standard"
 
-topic support:
+subagent support:
 	label: "Technical Support"
 	description: "Technical support with business hours awareness"
 
@@ -192,20 +192,20 @@ topic support:
 			| Help resolve the customer's technical issue.
 
 		actions:
-			back: @utils.transition to @topic.topic_selector
+			back: @utils.transition to @subagent.agent_router
 
 # ═══════════════════════════════════════════════════════════════════════════
-# ★ TOPIC-LEVEL SYSTEM OVERRIDES (NEW PATTERN)
-# These topics demonstrate complete persona switching using topic-level
+# ★ SUBAGENT-LEVEL SYSTEM OVERRIDES (NEW PATTERN)
+# These subagents demonstrate complete persona switching using subagent-level
 # system: blocks that OVERRIDE the global system instructions.
 # ═══════════════════════════════════════════════════════════════════════════
 
-topic formal_mode:
+subagent formal_mode:
 	label: "Formal Communication"
 	description: "Professional business communication mode"
 
-	# ★ TOPIC-LEVEL SYSTEM OVERRIDE
-	# This completely replaces global system instructions for this topic
+	# ★ SUBAGENT-LEVEL SYSTEM OVERRIDE
+	# This completely replaces global system instructions for this subagent
 	system:
 		instructions: "You are a formal business professional. Use professional language at all times. Address users as Sir or Madam. Avoid contractions, slang, and casual expressions. Focus on efficiency and clarity. Maintain a respectful, corporate tone."
 
@@ -217,13 +217,13 @@ topic formal_mode:
 			| I am prepared to address your inquiry with the utmost professionalism.
 
 		actions:
-			back: @utils.transition to @topic.topic_selector
+			back: @utils.transition to @subagent.agent_router
 
-topic creative_mode:
+subagent creative_mode:
 	label: "Creative Assistant"
 	description: "Creative and imaginative communication mode"
 
-	# ★ TOPIC-LEVEL SYSTEM OVERRIDE
+	# ★ SUBAGENT-LEVEL SYSTEM OVERRIDE
 	# Different persona entirely
 	system:
 		instructions: "You are a creative and imaginative assistant. Be playful, use metaphors and analogies. Think outside the box. Encourage brainstorming and wild ideas. Use emojis sparingly but effectively. Make conversations engaging and fun while still being helpful."
@@ -238,13 +238,13 @@ topic creative_mode:
 			| What shall we dream up today?
 
 		actions:
-			back: @utils.transition to @topic.topic_selector
+			back: @utils.transition to @subagent.agent_router
 
-topic technical_expert:
+subagent technical_expert:
 	label: "Technical Expert"
 	description: "Deep technical expertise mode"
 
-	# ★ TOPIC-LEVEL SYSTEM OVERRIDE
+	# ★ SUBAGENT-LEVEL SYSTEM OVERRIDE
 	# Specialist persona
 	system:
 		instructions: "You are a technical expert with deep knowledge. Use precise technical terminology. Provide detailed explanations with examples. Reference documentation when helpful. Assume the user has technical background. Be thorough but avoid unnecessary verbosity."
@@ -259,35 +259,35 @@ topic technical_expert:
 			| What technical challenge are we solving?
 
 		actions:
-			back: @utils.transition to @topic.topic_selector
+			back: @utils.transition to @subagent.agent_router
 
 # ★ Insight: Three Levels of Instruction Control
 #
 # LEVEL 1: GLOBAL SYSTEM BLOCK
 #   - Static text only (no variables, no conditionals)
-#   - Applies to ALL topics as baseline
+#   - Applies to ALL subagents as baseline
 #   - Good for: Guardrails, base personality, universal rules
 #   - Example: "Never share confidential information"
 #
-# LEVEL 2: TOPIC-LEVEL SYSTEM BLOCK (NEW!)
-#   - Placed inside topic definition
-#   - COMPLETELY OVERRIDES global system for that topic
+# LEVEL 2: SUBAGENT-LEVEL SYSTEM BLOCK (NEW!)
+#   - Placed inside subagent definition
+#   - COMPLETELY OVERRIDES global system for that subagent
 #   - Good for: Persona switching, mode changes, specialist behavior
-#   - Example: topic formal_mode: system: instructions: "Be professional..."
+#   - Example: subagent formal_mode: system: instructions: "Be professional..."
 #
-# LEVEL 3: TOPIC REASONING INSTRUCTIONS
+# LEVEL 3: SUBAGENT REASONING INSTRUCTIONS
 #   - Dynamic (variables, conditionals, template expressions)
-#   - Extends/adjusts behavior within topic
+#   - Extends/adjusts behavior within subagent
 #   - Good for: Context-aware responses, personalization
 #   - Example: if @variables.is_vip: | Provide priority service
 #
 # OVERRIDE HIERARCHY:
-#   Topic system: > Global system: > Default behavior
+#   Subagent system: > Global system: > Default behavior
 #
 # COMBINING APPROACHES:
 #   - Use GLOBAL system for universal guardrails
-#   - Use TOPIC system: for complete persona changes
-#   - Use TOPIC reasoning for dynamic conditional behavior
+#   - Use SUBAGENT system: for complete persona changes
+#   - Use SUBAGENT reasoning for dynamic conditional behavior
 #
-# Best Practice: Put guardrails in global system, personas in topic system,
-# and context-aware personalization in topic reasoning instructions.
+# Best Practice: Put guardrails in global system, personas in subagent system,
+# and context-aware personalization in subagent reasoning instructions.

package/skills/developing-agentforce/assets/prompt-rag-search.agent

@@ -10,7 +10,7 @@
 # CREDIT CONSUMPTION:
 # - Prompt Templates: 2-16 credits per invocation
 # - Retriever actions: 20 credits per search
-# - TIP: Cache retriever results in variables, reuse across topics
+# - TIP: Cache retriever results in variables, reuse across subagents
 
 system:
    messages:
@@ -43,14 +43,14 @@ start_agent entry:
       instructions: |
          Welcome the user and offer to help with questions.
       actions:
-         go_search: @utils.transition to @topic.knowledge_search
+         go_search: @utils.transition to @subagent.knowledge_search
             description: "Start knowledge search"
 
 # ============================================================
-# KNOWLEDGE SEARCH TOPIC (RAG Pattern)
+# KNOWLEDGE SEARCH SUBAGENT (RAG Pattern)
 # ============================================================
 
-topic knowledge_search:
+subagent knowledge_search:
    description: "Search knowledge base and generate grounded responses"
    reasoning:
       instructions: ->
@@ -64,7 +64,7 @@ topic knowledge_search:
 
          # NO RESULTS: Escalate or try different search
          if @variables.has_results == False and @variables.search_query != "":
-            | I couldn't find information about that topic.
+            | I couldn't find information about that subject.
             | Would you like to try a different search, or speak with a human agent?
 
          # INITIAL STATE: Ask for question
@@ -110,10 +110,10 @@ topic knowledge_search:
             description: "Transfer to human agent"
 
 # ============================================================
-# FOLLOW-UP QUESTIONS TOPIC
+# FOLLOW-UP QUESTIONS SUBAGENT
 # ============================================================
 
-topic follow_up:
+subagent follow_up:
    description: "Handle follow-up questions using cached context"
    reasoning:
       instructions: ->
@@ -124,8 +124,8 @@ topic follow_up:
                with query = ...  # Follow-up question extracted by LLM
                with context = @variables.search_results  # Reuse cached results!
          else:
-            transition to @topic.knowledge_search
+            transition to @subagent.knowledge_search
 
       actions:
-         back_to_search: @utils.transition to @topic.knowledge_search
+         back_to_search: @utils.transition to @subagent.knowledge_search
             description: "Start a new search"