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
5) If there are contradictions in history_steps, prefer the later entries. If you still cannot decide, return finished=false
51
55
and explain the contradiction in reason.
52
56
6) Do NOT assume results that are not explicitly supported by history_steps or session_files. Judge only from verifiable evidence.
57
+
6.1) When user_request includes explicit numeric/parameter constraints (e.g., "cut 5 layers", "vacuum = 1 layer",
58
+
"supercell/expand = 5×5×1"), you MUST verify history_steps explicitly confirms each constraint was applied
59
+
(e.g., args/output mentions 5 layers + vacuum + 5×5×1). If any one is not explicitly evidenced, set finished=false.
53
60
7) Termination/Unachievable rule: If the goal is clearly unachievable given the current context (e.g., repeated critical failures with no viable next action, missing required inputs that cannot be obtained from history_steps/session_files, or hard constraints prevent completion), you MUST return finished=true to terminate, and set reason to explicitly state that the task is not completed but cannot be completed (include the key blocking evidence).
54
61
# Output Format (very important)
55
62
You must output ONLY ONE JSON object that strictly matches this schema:
0 commit comments