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
IMPORTANT: Treat explicit numeric/parameter constraints (layers, vacuum thickness, slab orientation/cut, supercell expansion like 5×5×1, etc.) as mandatory. finished=true ONLY if history_steps explicitly confirms EACH constraint was applied.
28
27
28
+
IMPORTANT (NEW, HIGH PRIORITY): history_steps[*].suggestion is PRIMARY evidence for whether the task is still achievable.
29
+
- If ANY actionable suggestion exists (even if earlier), and it has NOT been explicitly attempted and exhausted in later history_steps, you MUST set finished=false (unless the goal is already completed).
30
+
- Actionable suggestions include: retrying with modified parameters, switching tools/providers, requesting missing inputs, rerunning with fixes, alternative workflows, etc.
31
+
- You MUST NOT output finished=true (Termination/Unachievable) when there exists any untried actionable suggestion.
32
+
- Only consider Termination/Unachievable when (a) NOT completed, AND (b) all actionable suggestions have been tried (and are evidenced as tried) with continued failure, AND (c) no remaining viable next action is suggested anywhere in history_steps.
33
+
34
+
CRITICAL: Do NOT treat "suggestion was not acted upon" as evidence of unachievability.
35
+
If there exists any actionable history_steps[*].suggestion that has not been tried, the task is still achievable => finished=false.
36
+
29
37
# Input
30
38
user_request:
31
39
{user_request}
32
-
33
40
history_steps (JSON):
34
41
{history_text}
35
-
36
42
session_files (JSON):
37
43
{session_files_text}
38
44
39
45
# Decision Rules (must follow)
40
46
1) Judge ONLY the user's final goal completion / stop condition, not whether all intermediate steps ran.
47
+
41
48
2) Deliverable type:
42
49
- If a file artifact is required (PDF/DOCX/ZIP/code project/structure file, etc.), you MUST verify an appropriate OSS link exists in session_files; otherwise finished=false (unless Termination/Unachievable applies).
43
50
- If in-chat content is required, verify the complete requested content already exists in history_steps outputs; otherwise finished=false (unless Termination/Unachievable applies).
51
+
44
52
3) If any critical step is failed/missing/running OR outputs are insufficient to prove completion, set finished=false (unless Termination/Unachievable applies).
53
+
45
54
4) Insufficient evidence => finished=false and state exactly what is missing (unless Termination/Unachievable applies).
55
+
46
56
5) Contradictions: prefer later entries; if still unclear => finished=false and explain contradiction (unless Termination/Unachievable applies).
57
+
47
58
6) Do NOT assume results not explicitly supported by history_steps/session_files.
59
+
48
60
6.1) For explicit parameter constraints, if ANY constraint is not explicitly evidenced, finished=false (unless Termination/Unachievable applies).
49
-
7) Termination/Unachievable (STOP even though not done):
50
-
If the goal is NOT completed AND is blocked/unachievable such that no viable next action exists (e.g., repeated critical failures; missing required inputs that cannot be obtained; hard constraints prevent completion),
51
-
you MUST output finished=true and the reason MUST include:
61
+
62
+
7) Suggestion-first achievability check (MUST APPLY BEFORE declaring finished=true for Termination/Unachievable):
63
+
- Scan ALL history_steps for actionable suggestions.
64
+
- If any actionable suggestion is not explicitly shown as attempted and exhausted, output finished=false.
65
+
66
+
8) Termination/Unachievable (STOP even though not done):
67
+
You may output finished=true for Termination/Unachievable ONLY if:
68
+
- The goal is NOT completed, AND
69
+
- history_steps provide concrete evidence that no viable next action exists, AND
70
+
- EVERY actionable history_steps[*].suggestion has been explicitly tried in later history_steps and still failed, leaving no remaining options.
71
+
If ANY unresolved suggestion proposes a viable next action (e.g., change parameters, switch provider/tool, request missing info),
72
+
you MUST output finished=false (the session should continue), unless the goal is already completed.
73
+
74
+
If you output finished=true (Termination/Unachievable), the reason MUST include:
52
75
- "NOT completed" and
53
76
- "cannot be completed / unachievable" and
54
77
- the blocking evidence (specific failed steps / missing inputs).
55
-
You MUST NOT output finished=false if you claim the task is blocked/unachievable.
78
+
79
+
You MUST NOT output finished=true (Termination/Unachievable) when the only blocking evidence is that a tool failed once and the agent has not yet tried actionable suggestions (e.g., switching provider/tool, changing parameters). In that case, output finished=false.
You are a validation agent responsible for checking if the execution result of a step matches the user's requirements and basic chemical/materials science knowledge.
3
7
4
8
Your task is to analyze:
@@ -9,6 +13,9 @@
9
13
10
14
Based on this analysis, determine if the result is reasonable and matches expectations.
11
15
16
+
Backup tools you may suggest using if the result is invalid or uncertain:
17
+
{alternative_tools}
18
+
12
19
# Validation Criteria:
13
20
1. **Relevance**: Does the result address the step's intended purpose?
14
21
2. **Accuracy**: Is the result consistent with basic chemical/materials science knowledge?
@@ -17,11 +24,12 @@
17
24
18
25
# Output Format:
19
26
You must respond with a JSON object containing:
20
-
{
27
+
{{
21
28
"is_valid": boolean, // true if result matches requirements and knowledge, false otherwise
22
29
"reason": "string", // brief explanation of validation result
23
-
"confidence": "high|medium|low" // confidence level in the validation
24
-
}
30
+
"confidence": "high|medium|low", // confidence level in the validation
31
+
"suggestion": "string" // actionable suggestion; if invalid/uncertain, suggest fixes or using one of the backup tools above
32
+
}}
25
33
26
34
# Important Rules:
27
35
- If the result contains obvious errors (wrong chemical formulas, impossible physical properties, etc.), mark as invalid
0 commit comments