anchor stringlengths 723 2.15k | positive stringlengths 153 8.2k |
|---|---|
Given the stale assessment and broad query, what structural landmarks should we enumerate next?
Decision: route
History: [{"action_family": "tool_use", "result": "weak", "step": 0}, {"action_family": "tool_use", "result": "weak", "step": 1}]
Plan: {"active": false, "operation": "enumerate_sources"}
Agent State: {"phase... | Use this candidate when the task requires sections and structural landmarks.. Capabilities: inspect document structure. Accepts: pdf. Returns: document structure. Evidence role: structure discovery. Prerequisites: source selected. Constraints: pdf source required. Side effects: read. Arguments: landmark (string optiona... |
Can you point me to the relevant pages or ranges for event delivery and retry behavior?
Decision: route
History: [{"action_family": "tool_use", "result": "weak", "step": 0}]
Plan: {"active": false, "operation": "enumerate_sources"}
Agent State: {"phase": "inspection", "question_length_band": "short", "state_name": "par... | This operation handles the relevant pages or ranges while preserving the current task state.. Capabilities: search document pages. Accepts: pdf. Returns: evidence candidates. Evidence role: candidate discovery. Prerequisites: source selected. Constraints: pdf source required. Side effects: read. Arguments: page range (... |
To compare sources, which resource should be examined to find the relevant technical instruction?
Decision: route
History: [{"action_family": "tool_use", "result": "weak", "step": 0}, {"action_family": "tool_use", "result": "weak", "step": 1}, {"action_family": "tool_use", "result": "weak", "step": 2}, {"action_family"... | The operation produces a reliable result for the selected resource under current constraints.. Capabilities: read content, inspect full source. Accepts: text, code. Returns: content. Evidence role: evidence inspection. Prerequisites: source selected. Constraints: local source required. Side effects: read. Arguments: of... |
Given the partial source inventory and exact identifier, which symbols or definitions should be checked for resource limits?
Decision: route
History: [{"action_family": "tool_use", "result": "weak", "step": 0}, {"action_family": "tool_use", "result": "weak", "step": 1}]
Plan: {"active": false, "operation": "latest_valu... | The operation produces a reliable result for symbols and definitions under current constraints.. Capabilities: inspect code structure. Accepts: code. Returns: content, code structure. Evidence role: evidence inspection. Prerequisites: source selected. Constraints: code source required. Side effects: read. Arguments: de... |
Given the stale assessment and partial progress, what safe next step can I take to find a candidate result without writing any state, given the mixed sources?
Decision: route
History: [{"action_family": "tool_use", "result": "weak", "step": 0}]
Plan: {"active": false, "operation": "lookup_semantic"}
Agent State: {"phas... | Apply this capability when the next decision depends on a candidate result.. Capabilities: inspect evidence. Accepts: evidence candidates. Returns: evidence. Evidence role: evidence inspection. Prerequisites: evidence candidate selected. Constraints: candidate evidence required. Side effects: read. Arguments: claim (st... |
I've already checked some complementary sources but haven't inspected the surrounding context. What should I do next to find the missing context for version compatibility, given that my previous searches were broad?
Decision: route
History: [{"action_family": "tool_use", "result": "weak", "step": 0}, {"action_family": ... | This candidate supports controlled inspection of missing surrounding context.. Capabilities: expand context. Accepts: evidence candidates, evidence. Returns: evidence. Evidence role: context expansion. Prerequisites: evidence candidate selected. Constraints: incomplete context required. Side effects: read. Arguments: r... |
Instead of just listing all candidates, what is the precise next move to resolve a contradiction between results from different sources, considering I've already inspected multiple sources and need to determine the next workflow step?
Decision: route
History: [{"action_family": "tool_use", "result": "weak", "step": 0}]... | Use this candidate when the task requires agreement or conflict between results.. Capabilities: compare evidence. Accepts: evidence. Returns: evidence comparison. Evidence role: evidence synthesis. Prerequisites: evidence inspected. Constraints: multiple evidence required. Side effects: none. Arguments: comparison (str... |
How can I verify that my current result covers all task requirements, given that I've only seen snippets and need to ensure failure recovery is complete?
Decision: route
Plan: {"active": false, "operation": "compare"}
Agent State: {"phase": "terminal_readiness", "question_length_band": "long", "state_name": "fresh_suff... | This operation handles task requirements and coverage while preserving the current task state.. Capabilities: update requirements. Accepts: evidence, agent state. Returns: governance state. Evidence role: governance update. Prerequisites: evidence inspected. Constraints: tracked requirements required. Side effects: loc... |
Given our remaining step budget, should we first check if the current evidence and metadata are enough to satisfy the telemetry requirements, or do we need more retrieval?
Decision: route
History: [{"action_family": "tool_use", "result": "weak", "step": 0}, {"action_family": "tool_use", "result": "weak", "step": 1}]
Pl... | Invoke the candidate to determine whether available information is sufficient from the available resources.. Capabilities: assess evidence. Accepts: evidence, governance state. Returns: assessment. Evidence role: governance assessment. Prerequisites: requirements updated. Constraints: canonical evidence set required. S... |
After the ambiguous attempt, what should we do next: pick the best candidate from the contradictory evidence or adjust our recovery plan?
Decision: route
History: [{"action_family": "tool_use", "result": "weak", "step": 0}, {"action_family": "tool_use", "result": "weak", "step": 1}]
Plan: {"active": false, "operation":... | The operation produces a reliable result for the selected result or next action under current constraints.. Capabilities: finalize selection. Accepts: assessment, governance state. Returns: terminal result. Evidence role: terminal decision. Prerequisites: requirements complete. Constraints: fresh sufficient assessment ... |
Which source should we consult next to gather more evidence for the consistency check across documents?
Decision: route
History: [{"action_family": "tool_use", "result": "weak", "step": 0}]
Plan: {"active": true, "operation": "enumerate_sources"}
Agent State: {"phase": "retrieval", "question_length_band": "long", "stat... | Apply this capability when the next decision depends on the best next information-gathering step.. Capabilities: plan retrieval. Accepts: agent state, text. Returns: plan. Evidence role: none. Prerequisites: objective available. Constraints: none. Side effects: local state write. Arguments: objective (string required),... |
What should we do next to locate the relevant technical instructions given the available resources?
Decision: route
History: [{"action_family": "tool_use", "result": "weak", "step": 0}, {"action_family": "tool_use", "result": "weak", "step": 1}, {"action_family": "tool_use", "result": "weak", "step": 2}, {"action_famil... | This candidate supports controlled inspection of the available resources.. Capabilities: list sources. Accepts: metadata. Returns: source list. Evidence role: source discovery. Prerequisites: none. Constraints: none. Side effects: read. Arguments: filters (object optional), scope (string required) |
Given the conflicting access rules, what should we inspect next to resolve the near-duplicate evidence?
Decision: route
History: [{"action_family": "tool_use", "result": "weak", "step": 0}]
Plan: {"active": false, "operation": "compatibility"}
Agent State: {"phase": "inspection", "question_length_band": "long", "state_... | Use this candidate when the task requires the relevant content.. Capabilities: search content. Accepts: text, pdf. Returns: evidence candidates. Evidence role: candidate discovery. Prerequisites: query available. Constraints: indexed sources required. Side effects: read. Arguments: limit (integer optional), query (stri... |
After reviewing several versions, which exact workflow step name should we adopt for the next action?
Decision: route
History: [{"action_family": "tool_use", "result": "weak", "step": 0}, {"action_family": "tool_use", "result": "weak", "step": 1}, {"action_family": "tool_use", "result": "weak", "step": 2}, {"action_fam... | Invoke the candidate to determine an exact name, code, or token from the available resources.. Capabilities: exact pattern search, identifier search. Accepts: text, code. Returns: evidence candidates. Evidence role: candidate discovery. Prerequisites: query available. Constraints: textual source required. Side effects:... |
We need to find the field definitions that are compatible with our schema. What metadata should we examine?
Decision: route
History: [{"action_family": "tool_use", "result": "weak", "step": 0}, {"action_family": "tool_use", "result": "weak", "step": 1}]
Plan: {"active": false, "operation": "compatibility"}
Agent State:... | Invoke the candidate to determine resource metadata and filters from the available resources.. Capabilities: search metadata. Accepts: metadata. Returns: source list. Evidence role: source discovery. Prerequisites: none. Constraints: metadata catalog required. Side effects: read. Arguments: filters (object required), s... |
Considering the split context and retry requirements, what structural details of the event should we compare to resolve the contradiction?
Decision: route
History: [{"action_family": "tool_use", "result": "weak", "step": 0}, {"action_family": "tool_use", "result": "weak", "step": 1}]
Plan: {"active": false, "operation"... | The operation produces a reliable result for fields, types, and structure under current constraints.. Capabilities: inspect structured schema. Accepts: csv, excel, sqlite. Returns: schema. Evidence role: structure discovery. Prerequisites: source selected. Constraints: structured source required. Side effects: read. Ar... |
I have a broad query and a partial inventory. Which action can match records in the SQLite source without writing anything?
Decision: route
History: [{"action_family": "tool_use", "result": "weak", "step": 0}]
Plan: {"active": true, "operation": "lookup_exact"}
Agent State: {"phase": "planning", "question_length_band":... | Apply this capability when the next decision depends on matching records.. Capabilities: search structured records. Accepts: csv, excel, sqlite. Returns: evidence candidates. Evidence role: candidate discovery. Prerequisites: schema known. Constraints: structured source required. Side effects: read. Arguments: limit (i... |
We've already checked two evidence candidates but haven't inspected the PDF. What should I do next to locate the exact section for the recovery plan?
Decision: route
History: [{"action_family": "tool_use", "result": "weak", "step": 0}, {"action_family": "tool_use", "result": "weak", "step": 1}, {"action_family": "tool_... | This candidate supports controlled inspection of sections and structural landmarks.. Capabilities: inspect document structure. Accepts: pdf. Returns: document structure. Evidence role: structure discovery. Prerequisites: source selected. Constraints: pdf source required. Side effects: read. Arguments: landmark (string ... |
Instead of re-reading the whole file, which operation should I run now to get only the relevant pages from the mixed sources?
Decision: route
History: [{"action_family": "tool_use", "result": "weak", "step": 0}]
Plan: {"active": false, "operation": "join"}
Agent State: {"phase": "inspection", "question_length_band": "l... | This operation handles the relevant pages or ranges while preserving the current task state.. Capabilities: search document pages, retrieve passages. Accepts: pdf. Returns: evidence candidates. Evidence role: candidate discovery. Prerequisites: source selected. Constraints: pdf source required. Side effects: read. Argu... |
How should I verify the access rule for the selected resource using the complementary evidence sources?
Decision: route
History: [{"action_family": "tool_use", "result": "weak", "step": 0}, {"action_family": "tool_use", "result": "weak", "step": 1}, {"action_family": "tool_use", "result": "weak", "step": 2}, {"action_f... | This operation handles the selected resource while preserving the current task state.. Capabilities: read content. Accepts: text, code. Returns: content. Evidence role: evidence inspection. Prerequisites: source selected. Constraints: local source required. Side effects: read. Arguments: offset (integer optional), reso... |
Given the remaining four steps, prioritize identifying the correct symbol definitions needed for the transformation.
Decision: route
History: [{"action_family": "tool_use", "result": "weak", "step": 0}, {"action_family": "tool_use", "result": "weak", "step": 1}]
Plan: {"active": false, "operation": "latest_value_select... | Invoke the candidate to determine symbols and definitions from the available resources.. Capabilities: inspect code structure. Accepts: code. Returns: content, code structure. Evidence role: evidence inspection. Prerequisites: source selected. Constraints: code source required. Side effects: read. Arguments: depth (int... |
The previous attempt was incomplete; what operation should we perform next to recover and compare the candidate results?
Decision: route
History: [{"action_family": "tool_use", "result": "weak", "step": 0}]
Plan: {"active": false, "operation": "compare"}
Agent State: {"phase": "inspection", "question_length_band": "lon... | The operation produces a reliable result for a candidate result under current constraints.. Capabilities: inspect evidence. Accepts: evidence candidates. Returns: evidence. Evidence role: evidence inspection. Prerequisites: evidence candidate selected. Constraints: candidate evidence required. Side effects: read. Argum... |
Which resource or catalog operation should we use next to find the missing context for the next workflow step?
Decision: route
Plan: {"active": true, "operation": "contradiction_resolution"}
Agent State: {"phase": "planning", "question_length_band": "long", "state_name": "initial"}
Source State: {"available_modalities"... | Apply this capability when the next decision depends on missing surrounding context.. Capabilities: expand context. Accepts: evidence candidates, evidence. Returns: evidence. Evidence role: context expansion. Prerequisites: evidence candidate selected. Constraints: incomplete context required. Side effects: read. Argum... |
What next action should we take to join the contradictory evidence and assess agreement between the access rules?
Decision: route
History: [{"action_family": "tool_use", "result": "weak", "step": 0}, {"action_family": "tool_use", "result": "weak", "step": 1}, {"action_family": "tool_use", "result": "weak", "step": 2}, ... | This candidate supports controlled inspection of agreement or conflict between results.. Capabilities: compare evidence. Accepts: evidence. Returns: evidence comparison. Evidence role: evidence synthesis. Prerequisites: evidence inspected. Constraints: multiple evidence required. Side effects: none. Arguments: comparis... |
Given the contradictory evidence and stale assessment, what should be done next to resolve the access control requirement?
Decision: route
Plan: {"active": false, "operation": "contradiction_resolution"}
Agent State: {"phase": "synthesis", "question_length_band": "long", "state_name": "contradiction"}
Source State: {"a... | Use this candidate when the task requires task requirements and coverage.. Capabilities: update requirements. Accepts: evidence, agent state. Returns: governance state. Evidence role: governance update. Prerequisites: evidence inspected. Constraints: tracked requirements required. Side effects: local state write. Argum... |
Is the available evidence sufficient to determine the latest telemetry value, or is more information needed?
Decision: route
History: [{"action_family": "tool_use", "result": "weak", "step": 0}]
Plan: {"active": false, "operation": "latest_value_selection"}
Agent State: {"phase": "source_discovery", "question_length_ba... | This operation handles whether available information is sufficient while preserving the current task state.. Capabilities: assess evidence. Accepts: evidence, governance state. Returns: assessment. Evidence role: governance assessment. Prerequisites: requirements updated. Constraints: canonical evidence set required. S... |
To ensure event delivery and retry behavior, what should be the next step in retrieving the relevant specification?
Decision: route
Plan: {"active": true, "operation": "latest_value_selection"}
Agent State: {"phase": "retrieval", "question_length_band": "long", "state_name": "retrieval"}
Source State: {"available_modal... | Invoke the candidate to determine the selected result or next action from the available resources.. Capabilities: finalize selection. Accepts: assessment, governance state. Returns: terminal result. Evidence role: terminal decision. Prerequisites: requirements complete. Constraints: fresh sufficient assessment required... |
Considering the need for consistency across sources and the long document, what is the best next information-gathering step?
Decision: route
History: [{"action_family": "tool_use", "result": "weak", "step": 0}]
Plan: {"active": true, "operation": "lookup_semantic"}
Agent State: {"phase": "retrieval", "question_length_b... | The operation produces a reliable result for the best next information-gathering step under current constraints.. Capabilities: plan retrieval. Accepts: agent state, text. Returns: plan. Evidence role: none. Prerequisites: objective available. Constraints: none. Side effects: local state write. Arguments: objective (st... |
Given the stale assessment and only snippets inspected, which operation should I run next to find the resources that match the telemetry and trace requirements, without modifying any state?
Decision: route
History: [{"action_family": "tool_use", "result": "weak", "step": 0}, {"action_family": "tool_use", "result": "wea... | Apply this capability when the next decision depends on the available resources.. Capabilities: list sources. Accepts: metadata. Returns: source list. Evidence role: source discovery. Prerequisites: none. Constraints: none. Side effects: read. Arguments: filters (object optional), scope (string required) |
Since I've already checked the current evidence and found it fresh, but the source inventory is unknown and there's an identifier variation, what should I do next to locate the relevant content for the validation and quality constraints?
Decision: route
History: [{"action_family": "tool_use", "result": "weak", "step": ... | This candidate supports controlled inspection of the relevant content.. Capabilities: search content. Accepts: text, pdf. Returns: evidence candidates. Evidence role: candidate discovery. Prerequisites: query available. Constraints: indexed sources required. Side effects: read. Arguments: limit (integer optional), quer... |
I've inspected multiple sources but haven't enumerated all available ones; what operation should I perform next to get the exact access rule token, rather than just listing the sources?
Decision: route
History: [{"action_family": "tool_use", "result": "weak", "step": 0}]
Plan: {"active": false, "operation": "enumerate_... | Use this candidate when the task requires an exact name, code, or token.. Capabilities: exact pattern search. Accepts: text, code. Returns: evidence candidates. Evidence role: candidate discovery. Prerequisites: query available. Constraints: textual source required. Side effects: read. Arguments: case sensitive (boolea... |
After inspecting multiple complementary sources, how can I verify the consistency across them by joining the relevant metadata and filters, given the long-document needle?
Decision: route
History: [{"action_family": "tool_use", "result": "weak", "step": 0}, {"action_family": "tool_use", "result": "weak", "step": 1}, {"... | This operation handles resource metadata and filters while preserving the current task state.. Capabilities: search metadata. Accepts: metadata. Returns: source list. Evidence role: source discovery. Prerequisites: none. Constraints: metadata catalog required. Side effects: read. Arguments: filters (object required), s... |
Given the remaining steps, prioritize enumerating the available sources to identify the fields, types, and structure needed for version compatibility.
Decision: route
History: [{"action_family": "tool_use", "result": "weak", "step": 0}]
Plan: {"active": false, "operation": "enumerate_sources"}
Agent State: {"phase": "t... | Invoke the candidate to determine fields, types, and structure from the available resources.. Capabilities: inspect structured schema. Accepts: csv, excel, sqlite. Returns: schema. Evidence role: structure discovery. Prerequisites: source selected. Constraints: structured source required. Side effects: read. Arguments:... |
After the ambiguous attempt, how should I enumerate records to match the required event delivery and retry behavior, given the schema ambiguity?
Decision: route
Plan: {"active": false, "operation": "enumerate_records"}
Agent State: {"phase": "inspection", "question_length_band": "long", "state_name": "partial_evidence"... | The operation produces a reliable result for matching records under current constraints.. Capabilities: search structured records. Accepts: csv, excel, sqlite. Returns: evidence candidates. Evidence role: candidate discovery. Prerequisites: schema known. Constraints: structured source required. Side effects: read. Argu... |
Which available resource should I inspect next to locate the sections and structural landmarks for field definitions and compatibility?
Decision: route
History: [{"action_family": "tool_use", "result": "weak", "step": 0}, {"action_family": "tool_use", "result": "weak", "step": 1}]
Plan: {"active": false, "operation": "... | Apply this capability when the next decision depends on sections and structural landmarks.. Capabilities: inspect document structure. Accepts: pdf. Returns: document structure. Evidence role: structure discovery. Prerequisites: source selected. Constraints: pdf source required. Side effects: read. Arguments: landmark (... |
Given the inspected evidence and broad query, what next operation should join the relevant pages or ranges for the required data transformation?
Decision: route
History: [{"action_family": "tool_use", "result": "weak", "step": 0}]
Plan: {"active": true, "operation": "join"}
Agent State: {"phase": "planning", "question_... | This candidate supports controlled inspection of the relevant pages or ranges.. Capabilities: search document pages. Accepts: pdf. Returns: evidence candidates. Evidence role: candidate discovery. Prerequisites: source selected. Constraints: pdf source required. Side effects: read. Arguments: page range (array required... |
Given the contradictory snippets and no prior search, what resource should I use next to resolve the conflict?
Decision: route
Plan: {"active": true, "operation": "contradiction_resolution"}
Agent State: {"phase": "planning", "question_length_band": "long", "state_name": "initial"}
Source State: {"available_modalities"... | Use this candidate when the task requires the selected resource.. Capabilities: read content. Accepts: text, code. Returns: content. Evidence role: evidence inspection. Prerequisites: source selected. Constraints: local source required. Side effects: read. Arguments: offset (integer optional), resource (string required... |
Since the exact identifier isn't matching, what should I consult to understand event delivery and retry behavior?
Decision: route
History: [{"action_family": "tool_use", "result": "weak", "step": 0}, {"action_family": "tool_use", "result": "weak", "step": 1}]
Plan: {"active": true, "operation": "contradiction_resolutio... | This operation handles symbols and definitions while preserving the current task state.. Capabilities: inspect code structure. Accepts: code. Returns: content, code structure. Evidence role: evidence inspection. Prerequisites: source selected. Constraints: code source required. Side effects: read. Arguments: depth (int... |
To finish the event handling task, which candidate result should I use as the final answer?
Decision: route
History: [{"action_family": "tool_use", "result": "weak", "step": 0}]
Plan: {"active": false, "operation": "lookup_semantic"}
Agent State: {"phase": "terminal_readiness", "question_length_band": "short", "state_n... | The operation produces a reliable result for a candidate result under current constraints.. Capabilities: inspect evidence, verify provenance. Accepts: evidence candidates. Returns: evidence. Evidence role: evidence inspection. Prerequisites: evidence candidate selected. Constraints: candidate evidence required. Side e... |
For the next workflow step, which source provides the missing context given the schema ambiguity?
Decision: route
History: [{"action_family": "tool_use", "result": "weak", "step": 0}, {"action_family": "tool_use", "result": "weak", "step": 1}]
Plan: {"active": false, "operation": "join"}
Agent State: {"phase": "source_... | The operation produces a reliable result for missing surrounding context under current constraints.. Capabilities: expand context. Accepts: evidence candidates, evidence. Returns: evidence. Evidence role: context expansion. Prerequisites: evidence candidate selected. Constraints: incomplete context required. Side effec... |
Given the disputed requirements and mixed evidence, which operation should I run next to check if the inspected passages agree, without modifying any state?
Decision: route
Plan: {"active": false, "operation": "lookup_exact"}
Agent State: {"phase": "governance", "question_length_band": "long", "state_name": "insufficie... | Apply this capability when the next decision depends on agreement or conflict between results.. Capabilities: compare evidence. Accepts: evidence. Returns: evidence comparison. Evidence role: evidence synthesis. Prerequisites: evidence inspected. Constraints: multiple evidence required. Side effects: none. Arguments: c... |
We've already checked the metadata and have one evidence item, but the plan is stale. What transformation should be applied next to cover the two unresolved requirements?
Decision: route
History: [{"action_family": "tool_use", "result": "weak", "step": 0}]
Plan: {"active": false, "operation": "latest_value_selection"}
... | This candidate supports controlled inspection of task requirements and coverage.. Capabilities: update requirements. Accepts: evidence, agent state. Returns: governance state. Evidence role: governance update. Prerequisites: evidence inspected. Constraints: tracked requirements required. Side effects: local state write... |
I've seen part of the context and have eight evidence candidates. Instead of searching broadly again, what should I do to decide if the current evidence is sufficient for the trace?
Decision: route
Plan: {"active": true, "operation": "lookup_semantic"}
Agent State: {"phase": "planning", "question_length_band": "long", ... | Use this candidate when the task requires whether available information is sufficient.. Capabilities: assess evidence. Accepts: evidence, governance state. Returns: assessment. Evidence role: governance assessment. Prerequisites: requirements updated. Constraints: canonical evidence set required. Side effects: local st... |
The assessment is fresh and I've inspected multiple sources. To verify the final result, which operation should I run to enumerate the sources and confirm the evidence supports the conclusion?
Decision: route
Plan: {"active": false, "operation": "enumerate_sources"}
Agent State: {"phase": "terminal_readiness", "questio... | Invoke the candidate to determine the selected result or next action from the available resources.. Capabilities: finalize selection, emit terminal result. Accepts: assessment, governance state. Returns: terminal result. Evidence role: terminal decision. Prerequisites: requirements complete. Constraints: fresh sufficie... |
Given my remaining step budget is zero, which information-gathering action should I prioritize to resolve the schema ambiguity?
Decision: route
History: [{"action_family": "tool_use", "result": "weak", "step": 0}]
Plan: {"active": true, "operation": "latest_value_selection"}
Agent State: {"phase": "retrieval", "questio... | Invoke the candidate to determine the best next information-gathering step from the available resources.. Capabilities: plan retrieval. Accepts: agent state, text. Returns: plan. Evidence role: none. Prerequisites: objective available. Constraints: none. Side effects: local state write. Arguments: objective (string req... |
Since my previous attempt was incomplete, what resources can I use to recover and resolve the disputed requirements?
Decision: route
History: [{"action_family": "tool_use", "result": "weak", "step": 0}, {"action_family": "tool_use", "result": "weak", "step": 1}, {"action_family": "tool_use", "result": "weak", "step": 2... | The operation produces a reliable result for the available resources under current constraints.. Capabilities: list sources. Accepts: metadata. Returns: source list. Evidence role: source discovery. Prerequisites: none. Constraints: none. Side effects: read. Arguments: filters (object optional), scope (string required) |
Which content sources should I enumerate to validate the data quality, given the version noise?
Decision: route
History: [{"action_family": "tool_use", "result": "weak", "step": 0}, {"action_family": "tool_use", "result": "weak", "step": 1}, {"action_family": "tool_use", "result": "weak", "step": 2}, {"action_family": ... | Apply this capability when the next decision depends on the relevant content.. Capabilities: search content. Accepts: text, pdf. Returns: evidence candidates. Evidence role: candidate discovery. Prerequisites: query available. Constraints: indexed sources required. Side effects: read. Arguments: limit (integer optional... |
What is the next action to find the exact token or code needed for the transformation?
Decision: route
History: [{"action_family": "tool_use", "result": "weak", "step": 0}]
Plan: {"active": false, "operation": "lookup_exact"}
Agent State: {"phase": "terminal_readiness", "question_length_band": "short", "state_name": "f... | This candidate supports controlled inspection of an exact name, code, or token.. Capabilities: exact pattern search. Accepts: text, code. Returns: evidence candidates. Evidence role: candidate discovery. Prerequisites: query available. Constraints: textual source required. Side effects: read. Arguments: case sensitive ... |
Given the stale assessment and schema ambiguity, what are the candidate field definitions and compatibility filters to enumerate next?
Decision: route
History: [{"action_family": "tool_use", "result": "weak", "step": 0}, {"action_family": "tool_use", "result": "weak", "step": 1}, {"action_family": "tool_use", "result":... | Use this candidate when the task requires resource metadata and filters.. Capabilities: search metadata. Accepts: metadata. Returns: source list. Evidence role: source discovery. Prerequisites: none. Constraints: metadata catalog required. Side effects: read. Arguments: filters (object required), sort (string optional) |
With only snippets and a split context, how should we determine the fields, types, and structure for the relevant technical instruction?
Decision: route
History: [{"action_family": "tool_use", "result": "weak", "step": 0}, {"action_family": "tool_use", "result": "weak", "step": 1}, {"action_family": "tool_use", "result... | This operation handles fields, types, and structure while preserving the current task state.. Capabilities: inspect structured schema. Accepts: csv, excel, sqlite. Returns: schema. Evidence role: structure discovery. Prerequisites: source selected. Constraints: structured source required. Side effects: read. Arguments:... |
To resolve version compatibility, which records should be joined based on entity-bound matching?
Decision: route
Plan: {"active": false, "operation": "join"}
Agent State: {"phase": "synthesis", "question_length_band": "short", "state_name": "contradiction"}
Source State: {"available_modalities": ["text", "pdf", "csv", ... | Invoke the candidate to determine matching records from the available resources.. Capabilities: search structured records. Accepts: csv, excel, sqlite. Returns: evidence candidates. Evidence role: candidate discovery. Prerequisites: schema known. Constraints: structured source required. Side effects: read. Arguments: l... |
Given contradictory evidence and identifier variation, what sections and structural landmarks should we inspect to plan the next workflow step?
Decision: route
History: [{"action_family": "tool_use", "result": "weak", "step": 0}, {"action_family": "tool_use", "result": "weak", "step": 1}, {"action_family": "tool_use", ... | The operation produces a reliable result for sections and structural landmarks under current constraints.. Capabilities: inspect document structure. Accepts: pdf. Returns: document structure. Evidence role: structure discovery. Prerequisites: source selected. Constraints: pdf source required. Side effects: read. Argume... |
We need to recover from a failure. We've only seen 2 evidence pieces and there are 7 candidates that differ only by schema. Please enumerate the records that match our metadata filter, but only read, no writes. Which pages or ranges are relevant?
Decision: route
Plan: {"active": false, "operation": "enumerate_records"}... | Apply this capability when the next decision depends on the relevant pages or ranges.. Capabilities: search document pages. Accepts: pdf. Returns: evidence candidates. Evidence role: candidate discovery. Prerequisites: source selected. Constraints: pdf source required. Side effects: read. Arguments: page range (array r... |
We already checked two complementary sources and found near-duplicates. Now we need to join with the exact identifier to select the resource. Since we have only one step left and the assessment is stale, what is the selected resource? Please write the result locally, but no other side effects.
Decision: route
History: ... | This candidate supports controlled inspection of the selected resource.. Capabilities: read content. Accepts: text, code. Returns: content. Evidence role: evidence inspection. Prerequisites: source selected. Constraints: local source required. Side effects: read. Arguments: offset (integer optional), resource (string r... |
We have contradictory evidence across formats. We need to resolve this by looking at symbols and definitions. Do not just do a lexical search; we need the precise schema and code structure. What is the next move?
Decision: route
History: [{"action_family": "tool_use", "result": "weak", "step": 0}]
Plan: {"active": true... | Use this candidate when the task requires symbols and definitions.. Capabilities: inspect code structure. Accepts: code. Returns: content, code structure. Evidence role: evidence inspection. Prerequisites: source selected. Constraints: code source required. Side effects: read. Arguments: depth (integer required), resou... |
We have 8 evidence pieces from complementary sources, but there are near-duplicates. We need to enumerate all sources and then verify a candidate result. How should we confirm the result without any side effects?
Decision: route
Plan: {"active": false, "operation": "enumerate_sources"}
Agent State: {"phase": "source_di... | This operation handles a candidate result while preserving the current task state.. Capabilities: inspect evidence. Accepts: evidence candidates. Returns: evidence. Evidence role: evidence inspection. Prerequisites: evidence candidate selected. Constraints: candidate evidence required. Side effects: read. Arguments: cl... |
With 8 steps left, prioritize locating the missing surrounding context for the identifier from the PDF passages.
Decision: route
History: [{"action_family": "tool_use", "result": "weak", "step": 0}]
Plan: {"active": false, "operation": "enumerate_records"}
Agent State: {"phase": "terminal_readiness", "question_length_b... | Invoke the candidate to determine missing surrounding context from the available resources.. Capabilities: expand context. Accepts: evidence candidates, evidence. Returns: evidence. Evidence role: context expansion. Prerequisites: evidence candidate selected. Constraints: incomplete context required. Side effects: read... |
We have conflicting results from the CSV and PDF; with 2 steps left, how do we resolve the near-duplicate discrepancy?
Decision: route
History: [{"action_family": "tool_use", "result": "weak", "step": 0}, {"action_family": "tool_use", "result": "weak", "step": 1}]
Plan: {"active": false, "operation": "contradiction_res... | The operation produces a reliable result for agreement or conflict between results under current constraints.. Capabilities: compare evidence. Accepts: evidence. Returns: evidence comparison. Evidence role: evidence synthesis. Prerequisites: evidence inspected. Constraints: multiple evidence required. Side effects: non... |
Enumerate available records to cover telemetry and trace requirements, given the split context in code.
Decision: route
Plan: {"active": true, "operation": "enumerate_records"}
Agent State: {"phase": "retrieval", "question_length_band": "long", "state_name": "retrieval"}
Source State: {"available_modalities": ["code", ... | Apply this capability when the next decision depends on task requirements and coverage.. Capabilities: update requirements. Accepts: evidence, agent state. Returns: governance state. Evidence role: governance update. Prerequisites: evidence inspected. Constraints: tracked requirements required. Side effects: local stat... |
Next, assess whether the current evidence from complementary sources is sufficient for consistency checking.
Decision: route
History: [{"action_family": "tool_use", "result": "weak", "step": 0}, {"action_family": "tool_use", "result": "weak", "step": 1}, {"action_family": "tool_use", "result": "weak", "step": 2}, {"act... | Use this candidate when the task requires whether available information is sufficient.. Capabilities: assess evidence, validate sufficiency. Accepts: evidence, governance state. Returns: assessment. Evidence role: governance assessment. Prerequisites: requirements updated. Constraints: canonical evidence set required. ... |
Given the current evidence, what should be the next action?
Decision: route
History: [{"action_family": "tool_use", "result": "weak", "step": 0}, {"action_family": "tool_use", "result": "weak", "step": 1}]
Plan: {"active": true, "operation": "enumerate_sources"}
Agent State: {"phase": "retrieval", "question_length_band... | Use this candidate when the task requires the selected result or next action.. Capabilities: finalize selection. Accepts: assessment, governance state. Returns: terminal result. Evidence role: terminal decision. Prerequisites: requirements complete. Constraints: fresh sufficient assessment required. Side effects: local... |
What would be the most useful next move for gathering information?
Decision: route
History: [{"action_family": "tool_use", "result": "weak", "step": 0}, {"action_family": "tool_use", "result": "weak", "step": 1}]
Plan: {"active": true, "operation": "compare"}
Agent State: {"phase": "retrieval", "question_length_band": ... | This operation handles the best next information-gathering step while preserving the current task state.. Capabilities: plan retrieval. Accepts: agent state, text. Returns: plan. Evidence role: none. Prerequisites: objective available. Constraints: none. Side effects: local state write. Arguments: objective (string req... |
What resources are available to resolve the contradiction?
Decision: route
History: [{"action_family": "tool_use", "result": "weak", "step": 0}, {"action_family": "tool_use", "result": "weak", "step": 1}]
Plan: {"active": false, "operation": "contradiction_resolution"}
Agent State: {"phase": "synthesis", "question_leng... | Invoke the candidate to determine the available resources from the available resources.. Capabilities: list sources. Accepts: metadata. Returns: source list. Evidence role: source discovery. Prerequisites: none. Constraints: none. Side effects: read. Arguments: filters (object optional), scope (string required) |
Which content is relevant given the contradictory evidence and schema focus?
Decision: route
History: [{"action_family": "tool_use", "result": "weak", "step": 0}]
Plan: {"active": true, "operation": "absence_verification"}
Agent State: {"phase": "retrieval", "question_length_band": "short", "state_name": "retrieval"}
S... | The operation produces a reliable result for the relevant content under current constraints.. Capabilities: search content. Accepts: text, pdf. Returns: evidence candidates. Evidence role: candidate discovery. Prerequisites: query available. Constraints: indexed sources required. Side effects: read. Arguments: limit (i... |
I need to find the exact access code for a specific permission rule. Which read-only operation should I use next?
Decision: route
History: [{"action_family": "tool_use", "result": "weak", "step": 0}, {"action_family": "tool_use", "result": "weak", "step": 1}, {"action_family": "tool_use", "result": "weak", "step": 2}, ... | Apply this capability when the next decision depends on an exact name, code, or token.. Capabilities: exact pattern search. Accepts: text, code. Returns: evidence candidates. Evidence role: candidate discovery. Prerequisites: query available. Constraints: textual source required. Side effects: read. Arguments: case sen... |
We've checked the data files but haven't confirmed the absence of the required metadata filter. What should we do now?
Decision: route
History: [{"action_family": "tool_use", "result": "weak", "step": 0}, {"action_family": "tool_use", "result": "weak", "step": 1}]
Plan: {"active": false, "operation": "absence_verificat... | This candidate supports controlled inspection of resource metadata and filters.. Capabilities: search metadata. Accepts: metadata. Returns: source list. Evidence role: source discovery. Prerequisites: none. Constraints: metadata catalog required. Side effects: read. Arguments: filters (object required), sort (string op... |
I need to list all available sources to understand the document structure. Should I use the enumeration tool or the schema tool?
Decision: route
History: [{"action_family": "tool_use", "result": "weak", "step": 0}]
Plan: {"active": false, "operation": "enumerate_sources"}
Agent State: {"phase": "inspection", "question_... | Use this candidate when the task requires fields, types, and structure.. Capabilities: inspect structured schema. Accepts: csv, excel, sqlite. Returns: schema. Evidence role: structure discovery. Prerequisites: source selected. Constraints: structured source required. Side effects: read. Arguments: include types (boole... |
How can I verify that the joined records from the telemetry data are correct? What read-only step should I take next?
Decision: route
History: [{"action_family": "tool_use", "result": "weak", "step": 0}, {"action_family": "tool_use", "result": "weak", "step": 1}, {"action_family": "tool_use", "result": "weak", "step": ... | This operation handles matching records while preserving the current task state.. Capabilities: search structured records. Accepts: csv, excel, sqlite. Returns: evidence candidates. Evidence role: candidate discovery. Prerequisites: schema known. Constraints: structured source required. Side effects: read. Arguments: l... |
With only 8 steps left, which next operation should I prioritize to verify the absence of a required section across the inspected PDFs?
Decision: route
Plan: {"active": false, "operation": "absence_verification"}
Agent State: {"phase": "terminal_readiness", "question_length_band": "long", "state_name": "fresh_sufficien... | Invoke the candidate to determine sections and structural landmarks from the available resources.. Capabilities: inspect document structure. Accepts: pdf. Returns: document structure. Evidence role: structure discovery. Prerequisites: source selected. Constraints: pdf source required. Side effects: read. Arguments: lan... |
My previous attempt was incomplete; with only 2 steps left, what should I do next to recover and locate the relevant pages for the telemetry requirements?
Decision: route
History: [{"action_family": "tool_use", "result": "weak", "step": 0}, {"action_family": "tool_use", "result": "weak", "step": 1}]
Plan: {"active": tr... | The operation produces a reliable result for the relevant pages or ranges under current constraints.. Capabilities: search document pages. Accepts: pdf. Returns: evidence candidates. Evidence role: candidate discovery. Prerequisites: source selected. Constraints: pdf source required. Side effects: read. Arguments: page... |
No steps remain; what catalog or resource should I consult to enumerate sources for event delivery and retry behavior, given the schema-only differences?
Decision: route
History: [{"action_family": "tool_use", "result": "weak", "step": 0}, {"action_family": "tool_use", "result": "weak", "step": 1}]
Plan: {"active": fal... | Apply this capability when the next decision depends on the selected resource.. Capabilities: read content. Accepts: text, code. Returns: content. Evidence role: evidence inspection. Prerequisites: source selected. Constraints: local source required. Side effects: read. Arguments: offset (integer optional), resource (s... |
What is the next action to find the symbols and definitions needed for the technical instruction, given the split context and semantic match?
Decision: route
History: [{"action_family": "tool_use", "result": "weak", "step": 0}, {"action_family": "tool_use", "result": "weak", "step": 1}]
Plan: {"active": true, "operatio... | This candidate supports controlled inspection of symbols and definitions.. Capabilities: inspect code structure. Accepts: code. Returns: content, code structure. Evidence role: evidence inspection. Prerequisites: source selected. Constraints: code source required. Side effects: read. Arguments: depth (integer required)... |
Given the event delivery context, which candidate result should be used to determine the retry behavior?
Decision: route
History: [{"action_family": "tool_use", "result": "weak", "step": 0}, {"action_family": "tool_use", "result": "weak", "step": 1}]
Plan: {"active": true, "operation": "latest_value_selection"}
Agent S... | Use this candidate when the task requires a candidate result.. Capabilities: inspect evidence. Accepts: evidence candidates. Returns: evidence. Evidence role: evidence inspection. Prerequisites: evidence candidate selected. Constraints: candidate evidence required. Side effects: read. Arguments: claim (string optional)... |
What should be done next to find the missing surrounding context for the workflow step?
Decision: route
History: [{"action_family": "tool_use", "result": "weak", "step": 0}, {"action_family": "tool_use", "result": "weak", "step": 1}]
Plan: {"active": true, "operation": "absence_verification"}
Agent State: {"phase": "pl... | This operation handles missing surrounding context while preserving the current task state.. Capabilities: expand context. Accepts: evidence candidates, evidence. Returns: evidence. Evidence role: context expansion. Prerequisites: evidence candidate selected. Constraints: incomplete context required. Side effects: read... |
For failure recovery, what operation would help determine if the results agree or conflict?
Decision: route
History: [{"action_family": "tool_use", "result": "weak", "step": 0}]
Plan: {"active": true, "operation": "compare"}
Agent State: {"phase": "retrieval", "question_length_band": "short", "state_name": "retrieval"}... | Invoke the candidate to determine agreement or conflict between results from the available resources.. Capabilities: compare evidence. Accepts: evidence. Returns: evidence comparison. Evidence role: evidence synthesis. Prerequisites: evidence inspected. Constraints: multiple evidence required. Side effects: none. Argum... |
What next step should be performed to verify task requirements coverage for the technical instruction?
Decision: route
History: [{"action_family": "tool_use", "result": "weak", "step": 0}]
Plan: {"active": true, "operation": "absence_verification"}
Agent State: {"phase": "planning", "question_length_band": "long", "sta... | The operation produces a reliable result for task requirements and coverage under current constraints.. Capabilities: update requirements. Accepts: evidence, agent state. Returns: governance state. Evidence role: governance update. Prerequisites: evidence inspected. Constraints: tracked requirements required. Side effe... |
Given the stale assessment and partial source inventory, should we compare the available evidence candidates or first check if we have enough information from the SQLite source to proceed?
Decision: route
Plan: {"active": true, "operation": "compare"}
Agent State: {"phase": "retrieval", "question_length_band": "long", ... | Apply this capability when the next decision depends on whether available information is sufficient.. Capabilities: assess evidence. Accepts: evidence, governance state. Returns: assessment. Evidence role: governance assessment. Prerequisites: requirements updated. Constraints: canonical evidence set required. Side eff... |
We've inspected multiple sources and have fresh evidence, but there are unresolved requirements. Should we now synthesize the final result or first enumerate all records from the code source to address the resource limits?
Decision: route
Plan: {"active": false, "operation": "enumerate_records"}
Agent State: {"phase": ... | This candidate supports controlled inspection of the selected result or next action.. Capabilities: finalize selection. Accepts: assessment, governance state. Returns: terminal result. Evidence role: terminal decision. Prerequisites: requirements complete. Constraints: fresh sufficient assessment required. Side effects... |
We've done several searches and have full context. Should we verify the absence of a record in the CSV source using metadata filters, or is it better to check for consistency across sources without further retrieval?
Decision: route
History: [{"action_family": "tool_use", "result": "weak", "step": 0}, {"action_family":... | Use this candidate when the task requires the best next information-gathering step.. Capabilities: plan retrieval. Accepts: agent state, text. Returns: plan. Evidence role: none. Prerequisites: objective available. Constraints: none. Side effects: local state write. Arguments: objective (string required), priority (str... |
We have snippets only and a partial source list. How should we enumerate the available sources to verify field definitions and compatibility across formats, ensuring no side effects?
Decision: route
Plan: {"active": false, "operation": "enumerate_sources"}
Agent State: {"phase": "inspection", "question_length_band": "l... | This operation handles the available resources while preserving the current task state.. Capabilities: list sources. Accepts: metadata. Returns: source list. Evidence role: source discovery. Prerequisites: none. Constraints: none. Side effects: read. Arguments: filters (object optional), scope (string required) |
Given limited steps, which candidate source should we inspect first to enumerate sources?
Decision: route
History: [{"action_family": "tool_use", "result": "weak", "step": 0}]
Plan: {"active": true, "operation": "enumerate_sources"}
Agent State: {"phase": "retrieval", "question_length_band": "short", "state_name": "ret... | The operation produces a reliable result for the relevant content under current constraints.. Capabilities: search content, retrieve passages. Accepts: text, pdf. Returns: evidence candidates. Evidence role: candidate discovery. Prerequisites: query available. Constraints: indexed sources required. Side effects: read. ... |
We got an ambiguous result; what's the exact token to pick for delivery?
Decision: route
History: [{"action_family": "tool_use", "result": "weak", "step": 0}]
Plan: {"active": false, "operation": "latest_value_selection"}
Agent State: {"phase": "inspection", "question_length_band": "short", "state_name": "partial_evide... | The operation produces a reliable result for an exact name, code, or token under current constraints.. Capabilities: exact pattern search. Accepts: text, code. Returns: evidence candidates. Evidence role: candidate discovery. Prerequisites: query available. Constraints: textual source required. Side effects: read. Argu... |
Which resource metadata and filters are needed to check version compatibility?
Decision: route
History: [{"action_family": "tool_use", "result": "weak", "step": 0}, {"action_family": "tool_use", "result": "weak", "step": 1}]
Plan: {"active": false, "operation": "lookup_semantic"}
Agent State: {"phase": "terminal_readin... | Apply this capability when the next decision depends on resource metadata and filters.. Capabilities: search metadata. Accepts: metadata. Returns: source list. Evidence role: source discovery. Prerequisites: none. Constraints: metadata catalog required. Side effects: read. Arguments: filters (object required), sort (st... |
What next action should we take to get the fields and structure?
Decision: route
History: [{"action_family": "tool_use", "result": "weak", "step": 0}]
Plan: {"active": true, "operation": "latest_value_selection"}
Agent State: {"phase": "planning", "question_length_band": "short", "state_name": "initial"}
Source State: ... | This candidate supports controlled inspection of fields, types, and structure.. Capabilities: inspect structured schema. Accepts: csv, excel, sqlite. Returns: schema. Evidence role: structure discovery. Prerequisites: source selected. Constraints: structured source required. Side effects: read. Arguments: include types... |
Check which entries match the delivery criteria, ignoring version differences, and show the matching records.
Decision: route
History: [{"action_family": "tool_use", "result": "weak", "step": 0}, {"action_family": "tool_use", "result": "weak", "step": 1}]
Plan: {"active": false, "operation": "absence_verification"}
Age... | Use this candidate when the task requires matching records.. Capabilities: search structured records. Accepts: csv, excel, sqlite. Returns: evidence candidates. Evidence role: candidate discovery. Prerequisites: schema known. Constraints: structured source required. Side effects: read. Arguments: limit (integer require... |
Find the sections and structural landmarks in the documents that relate to the required data transformation.
Decision: route
Plan: {"active": true, "operation": "join"}
Agent State: {"phase": "retrieval", "question_length_band": "long", "state_name": "retrieval"}
Source State: {"available_modalities": ["text", "pdf", "... | Invoke the candidate to determine sections and structural landmarks from the available resources.. Capabilities: inspect document structure, discover sections. Accepts: pdf. Returns: document structure. Evidence role: structure discovery. Prerequisites: source selected. Constraints: pdf source required. Side effects: r... |
Identify the pages or ranges in the PDFs that contain the latest values for the data transformation, given the acronym ambiguity.
Decision: route
History: [{"action_family": "tool_use", "result": "weak", "step": 0}, {"action_family": "tool_use", "result": "weak", "step": 1}]
Plan: {"active": false, "operation": "latest... | Invoke the candidate to determine the relevant pages or ranges from the available resources.. Capabilities: search document pages. Accepts: pdf. Returns: evidence candidates. Evidence role: candidate discovery. Prerequisites: source selected. Constraints: pdf source required. Side effects: read. Arguments: page range (... |
Given the disputed requirements and the need for validation, select the resource that best matches the entity and supports quality checks.
Decision: route
History: [{"action_family": "tool_use", "result": "weak", "step": 0}, {"action_family": "tool_use", "result": "weak", "step": 1}]
Plan: {"active": false, "operation"... | The operation produces a reliable result for the selected resource under current constraints.. Capabilities: read content. Accepts: text, code. Returns: content. Evidence role: evidence inspection. Prerequisites: source selected. Constraints: local source required. Side effects: read. Arguments: offset (integer optiona... |
Given the partial context and version noise, what safe next step should I take to resolve contradictions in symbols and definitions for telemetry and trace requirements?
Decision: route
History: [{"action_family": "tool_use", "result": "weak", "step": 0}, {"action_family": "tool_use", "result": "weak", "step": 1}, {"ac... | Apply this capability when the next decision depends on symbols and definitions.. Capabilities: inspect code structure. Accepts: code. Returns: content, code structure. Evidence role: evidence inspection. Prerequisites: source selected. Constraints: code source required. Side effects: read. Arguments: depth (integer re... |
After checking four candidates with only schema differences, what should I do next to find the exact workflow step from the PDFs, given the near-duplicate issue?
Decision: route
Plan: {"active": false, "operation": "lookup_exact"}
Agent State: {"phase": "source_discovery", "question_length_band": "long", "state_name": ... | This candidate supports controlled inspection of a candidate result.. Capabilities: inspect evidence. Accepts: evidence candidates. Returns: evidence. Evidence role: evidence inspection. Prerequisites: evidence candidate selected. Constraints: candidate evidence required. Side effects: read. Arguments: claim (string op... |
Since I've already inspected partial context and found multiple passages, what is the precise next move to verify absence of surrounding context for event delivery, rather than re-searching broadly?
Decision: route
History: [{"action_family": "tool_use", "result": "weak", "step": 0}, {"action_family": "tool_use", "resu... | This operation handles missing surrounding context while preserving the current task state.. Capabilities: expand context, resolve split context. Accepts: evidence candidates, evidence. Returns: evidence. Evidence role: context expansion. Prerequisites: evidence candidate selected. Constraints: incomplete context requi... |
How should I verify agreement or conflict between the inspected results for telemetry requirements, given the stale assessment and version noise?
Decision: route
Plan: {"active": false, "operation": "join"}
Agent State: {"phase": "inspection", "question_length_band": "long", "state_name": "partial_evidence"}
Source Sta... | This operation handles agreement or conflict between results while preserving the current task state.. Capabilities: compare evidence. Accepts: evidence. Returns: evidence comparison. Evidence role: evidence synthesis. Prerequisites: evidence inspected. Constraints: multiple evidence required. Side effects: none. Argum... |
Given only 4 steps left and 2 unresolved requirements, what should I prioritize to ensure full coverage?
Decision: route
History: [{"action_family": "tool_use", "result": "weak", "step": 0}]
Plan: {"active": false, "operation": "enumerate_records"}
Agent State: {"phase": "synthesis", "question_length_band": "long", "st... | Invoke the candidate to determine task requirements and coverage from the available resources.. Capabilities: update requirements. Accepts: evidence, agent state. Returns: governance state. Evidence role: governance update. Prerequisites: evidence inspected. Constraints: tracked requirements required. Side effects: loc... |
My last attempt was incomplete. What should I do next to determine if I have enough information?
Decision: route
History: [{"action_family": "tool_use", "result": "weak", "step": 0}, {"action_family": "tool_use", "result": "weak", "step": 1}, {"action_family": "tool_use", "result": "weak", "step": 2}, {"action_family":... | The operation produces a reliable result for whether available information is sufficient under current constraints.. Capabilities: assess evidence. Accepts: evidence, governance state. Returns: assessment. Evidence role: governance assessment. Prerequisites: requirements updated. Constraints: canonical evidence set req... |
I need to pick the right data source from the catalog. What should I do next?
Decision: route
History: [{"action_family": "tool_use", "result": "weak", "step": 0}, {"action_family": "tool_use", "result": "weak", "step": 1}, {"action_family": "tool_use", "result": "weak", "step": 2}, {"action_family": "tool_use", "resul... | Apply this capability when the next decision depends on the selected result or next action.. Capabilities: finalize selection. Accepts: assessment, governance state. Returns: terminal result. Evidence role: terminal decision. Prerequisites: requirements complete. Constraints: fresh sufficient assessment required. Side ... |
What is the next step to gather the most relevant information?
Decision: route
History: [{"action_family": "tool_use", "result": "weak", "step": 0}, {"action_family": "tool_use", "result": "weak", "step": 1}]
Plan: {"active": true, "operation": "latest_value_selection"}
Agent State: {"phase": "retrieval", "question_len... | This candidate supports controlled inspection of the best next information-gathering step.. Capabilities: plan retrieval. Accepts: agent state, text. Returns: plan. Evidence role: none. Prerequisites: objective available. Constraints: none. Side effects: local state write. Arguments: objective (string required), priori... |
What can I use next to verify the absence of evidence after my two searches?
Decision: route
History: [{"action_family": "tool_use", "result": "weak", "step": 0}, {"action_family": "tool_use", "result": "weak", "step": 1}]
Plan: {"active": false, "operation": "absence_verification"}
Agent State: {"phase": "governance",... | This operation handles the available resources while preserving the current task state.. Capabilities: list sources, discover sources. Accepts: metadata. Returns: source list. Evidence role: source discovery. Prerequisites: none. Constraints: none. Side effects: read. Arguments: filters (object required), scope (string... |
What should I look at to validate the data quality and ensure the identifier matches exactly?
Decision: route
History: [{"action_family": "tool_use", "result": "weak", "step": 0}]
Plan: {"active": false, "operation": "lookup_semantic"}
Agent State: {"phase": "terminal_readiness", "question_length_band": "short", "state... | This operation handles the relevant content while preserving the current task state.. Capabilities: search content. Accepts: text, pdf. Returns: evidence candidates. Evidence role: candidate discovery. Prerequisites: query available. Constraints: indexed sources required. Side effects: read. Arguments: limit (integer o... |
I need to resolve a contradiction between passages. What should I use to get the exact name or code?
Decision: route
History: [{"action_family": "tool_use", "result": "weak", "step": 0}, {"action_family": "tool_use", "result": "weak", "step": 1}]
Plan: {"active": false, "operation": "contradiction_resolution"}
Agent St... | Invoke the candidate to determine an exact name, code, or token from the available resources.. Capabilities: exact pattern search. Accepts: text, code. Returns: evidence candidates. Evidence role: candidate discovery. Prerequisites: query available. Constraints: textual source required. Side effects: read. Arguments: c... |
What resource metadata and filters should I use to define the fields and ensure compatibility given the schema constraints?
Decision: route
Plan: {"active": true, "operation": "absence_verification"}
Agent State: {"phase": "planning", "question_length_band": "long", "state_name": "initial"}
Source State: {"available_mo... | The operation produces a reliable result for resource metadata and filters under current constraints.. Capabilities: search metadata. Accepts: metadata. Returns: source list. Evidence role: source discovery. Prerequisites: none. Constraints: metadata catalog required. Side effects: read. Arguments: filters (object requ... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.