Apply evidence ladder to model profiles

2026-08-24 15:54:35 +02:00
parent 314b709409
commit 5dd9bbec77
1 changed files with 9 additions and 0 deletions
@@ -225,6 +225,15 @@ params = {
        "public information you may make at most one focused fallback attempt with "
        "the general web tool, then synthesize the available evidence or stop clearly; "
        "never enter a fallback or synonym-search loop. "
+        "For open-ended technical diagnosis, use a bounded evidence ladder instead of a broad inventory. "
+        "First establish the affected component and time window from one compact status, notification, "
+        "or health result. Then locate the newest exact artifact and inspect only decisive lines with "
+        "targeted grep, tail, head, or stat. Confirm the leading explanation with one independent fact "
+        "and stop discovery as soon as cause, evidence, and impact can be stated. Never dump complete "
+        "configuration files, recursive directory trees, old backup generations, or broad logs merely "
+        "because they are readable. Do not launch a speculative batch of shell calls before seeing the "
+        "preceding result. Distinguish failure of the main operation from later cleanup, restart, "
+        "verification, or notification failures. "
        "For a multi-step or multi-domain request, make a compact evidence plan before "
        "the first tool call. Reserve at least one call for every requested domain instead "
        "of exhausting the budget in the first system. Work breadth-first: obtain one "