@arcgis/ai-components 5.1.0-next.60 → 5.1.0-next.61

package/dist/cdn/{VDUOWASW.js → 344C2EEF.js}

@@ -27,11 +27,15 @@ Validator: Before producing output, verify every field used exists in the listed
 
 ## Input
 
-Use the most recent relevant user question from the chat history. The question will **not** be restated again here. Start with a fresh WHERE clause for each question - do not inherit filters from previous questions unless user explicitly asks to combine them.
+Use the most recent relevant user question from the chat history.
 
-### Rules for generating where clause SQL expressions:
+### Fresh WHERE clause rule
 
-- Use only the field\u2019s **\`name\`** in the output expression.
+Start with a fresh WHERE clause for each new question. Do not inherit filters from previous questions UNLESS the user explicitly references previous results (see "Referencing Previously Identified Features" below).
+
+### Rules for generating WHERE clause SQL expressions:
+
+- Use only the field's **\`name\`** in the output expression.
 - Use metadata (\`alias\`, \`description\`, \`statistics\`) only to help understand the user's meaning \u2014 not in the syntax.
 - Use field \`type\` to choose appropriate operators:
   - **String** \u2192 \`LIKE '%value%'\`, \`=\`, \`IN (...)\` (prefer \`LIKE\` over \`=\`)
@@ -43,6 +47,16 @@ Use the most recent relevant user question from the chat history. The question w
 - **Range domain fields** \u2192 Use the listed min/max as valid bounds for comparisons.
 - If no meaningful layer filter can be generated, do not call a tool.
 
+## Referencing Previously Identified Features
+
+This is an exception to the "fresh WHERE clause" rule above.
+
+When the user uses words like "these", "those", "them", "the same ones" referring to features from a previous turn:
+
+- If the previous query used useCurrentExtent: true \u2192 use useCurrentExtent: true with where: "1=1"
+- If the previous assistant response mentions specific objectIds or feature IDs \u2192 use {{objectIdField}} IN (id1, id2, ...) to scope to those features
+- If neither is available, use the same WHERE clause and layer from the previous query turn to re-select the same features
+
 ### Mixed Questions
 
 If a question has both aggregate and display components (e.g., "How many wells have depth > 100? Show them"):