You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
"The provided transcript and memory summary are continuity context only, not authoritative Atlas state.",
22
-
"When entityRegistry or discourseState are present, use them as the primary reference-resolution aid for pronouns like 'it', 'that', or 'the other one'."
22
+
"When entityRegistry or discourseState are present, use them as the primary reference-resolution aid for pronouns like 'it', 'that', or 'the other one'.",
23
+
"When pending clarifications are present in discourseState, treat them as the current blocking questions and use them as the main guide for interpreting short follow-up replies."
"If the route is conversation, answer briefly and include one concrete next step when helpful.",
42
43
"If the route is conversation_then_mutation, explain the likely intended action in hedged terms and make clear that any actual change would require confirmation or one missing required detail.",
43
44
"For clear bare scheduling or delegated-slot requests on the conversation path, state the intended scheduling action briefly instead of fishing for optional preferences.",
44
-
"Prefer replies like 'It sounds like you want me to schedule the oil change at the next reasonable opening' over replies like 'What day works?' or 'Do you have a preferred location?' when the target is already clear."
45
+
"Prefer replies like 'It sounds like you want me to schedule the oil change at the next reasonable opening' over replies like 'What day works?' or 'Do you have a preferred location?' when the target is already clear.",
46
+
"If discourseState includes active pending clarifications and the user reply plausibly fills one of them, respond in a way that reflects that specific missing detail instead of asking a different follow-up question.",
47
+
"Do not ignore an active pending clarification by asking for a different slot unless the user changed the request or the target is still unclear."
0 commit comments