anchor stringlengths 723 2.15k | positive stringlengths 153 8.2k |
|---|---|
Given the inspected multi-source evidence, which read-only action should enumerate all source candidates for the exact field identifier, without writing state?
Decision: route
History: [{"action_family": "tool_use", "result": "weak", "step": 0}, {"action_family": "tool_use", "result": "weak", "step": 1}, {"action_famil... | 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 ... |
We've checked some sources but not the code. What should we do next to find the latest value for the exact identifier, considering the side-effect constraint?
Decision: route
History: [{"action_family": "tool_use", "result": "weak", "step": 0}, {"action_family": "tool_use", "result": "weak", "step": 1}]
Plan: {"active"... | 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... |
Instead of comparing all evidence, what is the specific next step to gather available resources for event handling, given the schema ambiguity and no prior inspections?
Decision: route
History: [{"action_family": "tool_use", "result": "weak", "step": 0}]
Plan: {"active": true, "operation": "compare"}
Agent State: {"pha... | Use this candidate when the task requires 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) |
To verify the result, which read-only operation should enumerate sources for the entity-bound query, given the near-duplicate obstacle and multi-source inspection?
Decision: route
History: [{"action_family": "tool_use", "result": "weak", "step": 0}, {"action_family": "tool_use", "result": "weak", "step": 1}]
Plan: {"ac... | Invoke the candidate to determine the relevant content from the available resources.. 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. Argument... |
With 8 steps left and stale assessments, prioritize comparing field definitions across candidate sources to resolve the disputed requirement.
Decision: route
History: [{"action_family": "tool_use", "result": "weak", "step": 0}, {"action_family": "tool_use", "result": "weak", "step": 1}, {"action_family": "tool_use", "r... | 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... |
The prior attempt was incomplete; how should I recover by enumerating records from the PDF sources using exact identifiers to validate quality constraints?
Decision: route
History: [{"action_family": "tool_use", "result": "weak", "step": 0}]
Plan: {"active": false, "operation": "enumerate_records"}
Agent State: {"phase... | 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... |
I need to verify absence of access rules across Excel sources; what resource or catalog operation should I perform next to inspect fields and structure?
Decision: route
History: [{"action_family": "tool_use", "result": "weak", "step": 0}, {"action_family": "tool_use", "result": "weak", "step": 1}, {"action_family": "to... | Apply this capability when the next decision depends on 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: includ... |
What should I do next to enumerate matching records from CSV and other sources to compare evidence for telemetry requirements?
Decision: route
History: [{"action_family": "tool_use", "result": "weak", "step": 0}]
Plan: {"active": false, "operation": "enumerate_records"}
Agent State: {"phase": "synthesis", "question_len... | This candidate supports controlled inspection of 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 ... |
Find the section headings and structural landmarks in the documents that cover resource limits and lifecycle.
Decision: route
Plan: {"active": false, "operation": "lookup_exact"}
Agent State: {"phase": "synthesis", "question_length_band": "long", "state_name": "contradiction"}
Source State: {"available_modalities": ["t... | 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... |
I need to know which pages or ranges discuss version compatibility. Can you point me to them?
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": ... | 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 (... |
I'm looking for telemetry and trace requirements. Where can I find them in the codebase?
Decision: route
History: [{"action_family": "tool_use", "result": "weak", "step": 0}, {"action_family": "tool_use", "result": "weak", "step": 1}]
Plan: {"active": true, "operation": "enumerate_records"}
Agent State: {"phase": "retr... | Invoke the candidate to determine the selected resource from the available resources.. 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 stale assessment and the acronym issue, find the symbols and definitions related to failure handling and recovery in the code.
Decision: route
Plan: {"active": true, "operation": "lookup_semantic"}
Agent State: {"phase": "retrieval", "question_length_band": "long", "state_name": "retrieval"}
Source State: {"a... | 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 current synthesis state and the partial context inspected, which candidate result should be selected next while ensuring only read and local state write side effects?
Decision: route
History: [{"action_family": "tool_use", "result": "weak", "step": 0}, {"action_family": "tool_use", "result": "weak", "step": 1... | This candidate supports controlled inspection of a candidate result.. Capabilities: inspect evidence, verify provenance. Accepts: evidence candidates. Returns: evidence. Evidence role: evidence inspection. Prerequisites: evidence candidate selected. Constraints: candidate evidence required. Side effects: read. Argument... |
After checking the evidence and finding schema ambiguity, what remains to be examined to understand the resource limits and lifecycle, given the missing surrounding context?
Decision: route
History: [{"action_family": "tool_use", "result": "weak", "step": 0}]
Plan: {"active": false, "operation": "compare"}
Agent State:... | 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... |
Between comparing the results for agreement or conflict and simply assessing the current evidence, which is the precise next move given the compatibility check needed?
Decision: route
Plan: {"active": true, "operation": "compatibility"}
Agent State: {"phase": "planning", "question_length_band": "long", "state_name": "i... | 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 we verify that the required data transformation has been fully covered, given the partial context and the need for exact identifier lookup?
Decision: route
History: [{"action_family": "tool_use", "result": "weak", "step": 0}, {"action_family": "tool_use", "result": "weak", "step": 1}, {"action_family": "tool_us... | 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 my remaining step budget is zero, what should I prioritize to confirm whether the available information suffices for the disputed requirement on event delivery and retry behavior?
Decision: route
Plan: {"active": false, "operation": "absence_verification"}
Agent State: {"phase": "inspection", "question_length_ban... | 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... |
My previous attempt was incomplete; what should I do next to finalize the selected result for the event delivery and retry behavior, given I have inspected multiple sources but the source inventory is unknown?
Decision: route
History: [{"action_family": "tool_use", "result": "weak", "step": 0}]
Plan: {"active": true, "... | Apply this capability when the next decision depends on the selected result or next action.. Capabilities: finalize selection, emit terminal result. Accepts: assessment, governance state. Returns: terminal result. Evidence role: terminal decision. Prerequisites: requirements complete. Constraints: fresh sufficient asse... |
With only two steps remaining and a partial source inventory, what is the best next information-gathering step to verify absence for the validation and quality constraints, given the acronym obstacle?
Decision: route
History: [{"action_family": "tool_use", "result": "weak", "step": 0}, {"action_family": "tool_use", "re... | 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 optional), priori... |
What should I do next to gather the available resources needed for the required data transformation, given the split context and that I have partial evidence?
Decision: route
History: [{"action_family": "tool_use", "result": "weak", "step": 0}]
Plan: {"active": false, "operation": "contradiction_resolution"}
Agent Stat... | 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) |
I need to verify the absence of a required item in the evidence I have. What should I do next?
Decision: route
History: [{"action_family": "tool_use", "result": "weak", "step": 0}]
Plan: {"active": false, "operation": "absence_verification"}
Agent State: {"phase": "inspection", "question_length_band": "short", "state_n... | 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... |
How can I resolve the contradictions among the passages I've inspected to identify the exact token?
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 Sta... | This operation handles an exact name, code, or token while preserving the current task state.. 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 should I do to list all available resources that match my criteria?
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", "result": "... | 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... |
Given the split context, what operation can I use to confirm the absence of a required field in 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}, ... | 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... |
Given the inspected complementary sources, which operation should I run next to find the exact matching records without modifying anything?
Decision: route
Plan: {"active": true, "operation": "lookup_exact"}
Agent State: {"phase": "planning", "question_length_band": "long", "state_name": "initial"}
Source State: {"avai... | 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 the first passage; what should we do next to compare the remaining sections across the documents, given the schema differences?
Decision: route
Plan: {"active": true, "operation": "compare"}
Agent State: {"phase": "retrieval", "question_length_band": "long", "state_name": "retrieval"}
Source State... | 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 ... |
Should we finalize the output now, or is there a join operation needed first to reconcile the contradictory field definitions across the relevant pages?
Decision: route
History: [{"action_family": "tool_use", "result": "weak", "step": 0}, {"action_family": "tool_use", "result": "weak", "step": 1}]
Plan: {"active": fals... | Use this candidate when the task requires 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), quer... |
How can I verify the selected resource against the stale assessment, using a semantic lookup that only reads data, to confirm its quality constraints?
Decision: route
History: [{"action_family": "tool_use", "result": "weak", "step": 0}]
Plan: {"active": false, "operation": "lookup_semantic"}
Agent State: {"phase": "gov... | 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 stale assessment and only one step left, which candidate should I prioritize to resolve the unresolved requirement about resource limits?
Decision: route
History: [{"action_family": "tool_use", "result": "weak", "step": 0}, {"action_family": "tool_use", "result": "weak", "step": 1}, {"action_family": "tool_us... | The operation produces a reliable result for symbols and definitions under current constraints.. Capabilities: inspect code structure, resolve symbols. Accepts: code. Returns: content, code structure. Evidence role: evidence inspection. Prerequisites: source selected. Constraints: code source required. Side effects: re... |
My last attempt didn't find the right identifier. What should I do next to recover and compare the candidate results?
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": ... | 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... |
I need to verify the absence of some context around the required transformation. What resource should I check 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 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... |
I've inspected multiple sources but need to check for agreement or conflict between the results. 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"... | 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... |
What should we do next to cover the two unresolved resource limits and lifecycle 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}, {"action_family": "... | 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... |
Do we have enough to confirm the relevant technical instruction?
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: {"phase": "inspection", "question_length_b... | 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... |
What is the next step to complete the required data transformation despite the schema ambiguity?
Decision: route
Plan: {"active": false, "operation": "absence_verification"}
Agent State: {"phase": "governance", "question_length_band": "short", "state_name": "insufficient"}
Source State: {"available_modalities": ["code"... | 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... |
What is the best next information-gathering step to resolve the acronym and define field compatibility?
Decision: route
History: [{"action_family": "tool_use", "result": "weak", "step": 0}]
Plan: {"active": true, "operation": "contradiction_resolution"}
Agent State: {"phase": "planning", "question_length_band": "long",... | 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 partial context and semantic match, enumerate candidate records from available sources, but only use read operations and avoid any local state writes.
Decision: route
History: [{"action_family": "tool_use", "result": "weak", "step": 0}, {"action_family": "tool_use", "result": "weak", "step": 1}]
Plan: {"activ... | 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 we've already checked the relevant content and only schema differences remain, verify the absence of any additional evidence by inspecting the available sources without writing local state.
Decision: route
History: [{"action_family": "tool_use", "result": "weak", "step": 0}, {"action_family": "tool_use", "result"... | 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... |
For the exact identifier we need, should we inspect the schema and field definitions from the source, rather than just retrieving the raw content?
Decision: route
History: [{"action_family": "tool_use", "result": "weak", "step": 0}]
Plan: {"active": true, "operation": "compatibility"}
Agent State: {"phase": "planning",... | 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... |
How can we verify the event delivery and retry behavior by examining the resource metadata and filters from the available 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": "we... | Invoke the candidate to determine resource metadata and filters from the available resources.. Capabilities: search metadata, filter sources. Accepts: metadata. Returns: source list. Evidence role: source discovery. Prerequisites: none. Constraints: metadata catalog required. Side effects: read. Arguments: filters (obj... |
Given limited steps, prioritize inspecting the schema of the SQLite source to resolve the identifier mismatch.
Decision: route
Plan: {"active": false, "operation": "lookup_exact"}
Agent State: {"phase": "inspection", "question_length_band": "long", "state_name": "partial_evidence"}
Source State: {"available_modalities"... | 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 an ambiguous attempt, recover by comparing candidate records from the Excel source to select the latest value.
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 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... |
Enumerate available PDF sources to locate sections and structural landmarks for the technical instruction.
Decision: route
Plan: {"active": false, "operation": "enumerate_sources"}
Agent State: {"phase": "synthesis", "question_length_band": "long", "state_name": "contradiction"}
Source State: {"available_modalities": [... | 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 (... |
Next, retrieve the relevant pages or ranges from the PDF source to support the join operation.
Decision: route
History: [{"action_family": "tool_use", "result": "weak", "step": 0}, {"action_family": "tool_use", "result": "weak", "step": 1}]
Plan: {"active": true, "operation": "join"}
Agent State: {"phase": "retrieval",... | 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... |
We have two candidate sources inspected but no matches yet. What should we do next to verify the absence?
Decision: route
Plan: {"active": false, "operation": "absence_verification"}
Agent State: {"phase": "terminal_readiness", "question_length_band": "long", "state_name": "fresh_sufficient"}
Source State: {"available_... | 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... |
We need to check version compatibility. What's the next step to find the exact symbol definitions?
Decision: route
History: [{"action_family": "tool_use", "result": "weak", "step": 0}]
Plan: {"active": false, "operation": "lookup_exact"}
Agent State: {"phase": "inspection", "question_length_band": "short", "state_name"... | 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... |
Given the acronym ambiguity, which candidate should we validate first to ensure data quality?
Decision: route
History: [{"action_family": "tool_use", "result": "weak", "step": 0}]
Plan: {"active": false, "operation": "lookup_semantic"}
Agent State: {"phase": "source_discovery", "question_length_band": "short", "state_n... | Invoke the candidate to determine a candidate result from the available resources.. 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... |
After exhaustive search, we lack surrounding context. What operation should we perform next to verify absence, given the long document?
Decision: route
History: [{"action_family": "tool_use", "result": "weak", "step": 0}, {"action_family": "tool_use", "result": "weak", "step": 1}, {"action_family": "tool_use", "result"... | 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 stale assessment and the need to compare field definitions, what is the next safe operation that only reads evidence and avoids side effects?
Decision: route
History: [{"action_family": "tool_use", "result": "weak", "step": 0}, {"action_family": "tool_use", "result": "weak", "step": 1}]
Plan: {"active": true,... | 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 some sources but haven't inspected any evidence. For failure recovery, what remains to be enumerated to ensure task coverage, without writing state?
Decision: route
Plan: {"active": false, "operation": "enumerate_records"}
Agent State: {"phase": "governance", "question_length_band": "long", "state... | Use this candidate when the task requires task requirements and coverage.. Capabilities: update requirements, track coverage. Accepts: evidence, agent state. Returns: governance state. Evidence role: governance update. Prerequisites: evidence inspected. Constraints: tracked requirements required. Side effects: local st... |
We have full context but exhausted evidence and need to resolve a contradiction. Should we search for more evidence or finalize with what we have?
Decision: route
History: [{"action_family": "tool_use", "result": "weak", "step": 0}, {"action_family": "tool_use", "result": "weak", "step": 1}]
Plan: {"active": false, "op... | 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... |
How should we verify the compatibility of resource limits and lifecycle using the complementary evidence we've inspected?
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", "ste... | This operation handles the selected result or next action while preserving the current task state.. Capabilities: finalize selection. Accepts: assessment, governance state. Returns: terminal result. Evidence role: terminal decision. Prerequisites: requirements complete. Constraints: fresh sufficient assessment required... |
Given the disputed requirements and limited steps, what is the highest-priority next action to gather missing source information?
Decision: route
History: [{"action_family": "tool_use", "result": "weak", "step": 0}, {"action_family": "tool_use", "result": "weak", "step": 1}]
Plan: {"active": true, "operation": "enumera... | 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... |
After an incomplete attempt, what resources are available to help compare version compatibility?
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 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 available content is most relevant for checking consistency across the sources?
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": "synthesi... | 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 should be the next step to find the exact version token?
Decision: route
Plan: {"active": true, "operation": "enumerate_sources"}
Agent State: {"phase": "planning", "question_length_band": "short", "state_name": "initial"}
Source State: {"available_modalities": ["code", "metadata"], "evidence_topology_observed": "... | Use this candidate when the task requires an exact name, code, or token.. 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: read. Arguments: cas... |
Given the partial context and the exact identifier, what should I do next to find the matching resource metadata and filters?
Decision: route
History: [{"action_family": "tool_use", "result": "weak", "step": 0}]
Plan: {"active": false, "operation": "lookup_exact"}
Agent State: {"phase": "terminal_readiness", "question_... | 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) |
Considering the entity-bound query and schema ambiguity, what operation should I perform to get the fields, types, and structure for telemetry and trace requirements?
Decision: route
History: [{"action_family": "tool_use", "result": "weak", "step": 0}, {"action_family": "tool_use", "result": "weak", "step": 1}, {"actio... | 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 the contradiction between sources, what should I do next to match records for access rules and permissions?
Decision: route
Plan: {"active": false, "operation": "contradiction_resolution"}
Agent State: {"phase": "source_discovery", "question_length_band": "long", "state_name": "source_discovery"}
Source Stat... | 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 the long document and need for structural landmarks, what operation should I use to enumerate sections for access rules, while respecting the side-effect constraint?
Decision: route
History: [{"action_family": "tool_use", "result": "weak", "step": 0}, {"action_family": "tool_use", "result": "weak", "step": 1}, {"... | 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... |
Given the partial context and near-duplicate rows, which pages or ranges should I inspect next to confirm field definitions and compatibility, without writing any state?
Decision: route
Plan: {"active": false, "operation": "lookup_semantic"}
Agent State: {"phase": "inspection", "question_length_band": "long", "state_na... | 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've already checked one source and found identifier variations. For the selected resource, what remains to enumerate regarding limits and lifecycle, using only metadata filters?
Decision: route
History: [{"action_family": "tool_use", "result": "weak", "step": 0}]
Plan: {"active": false, "operation": "enumerate_record... | 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... |
Although the technical instruction seems to be about symbols, should I extract the full passage or just the definitions? What is the precise next move to get the relevant instruction?
Decision: route
History: [{"action_family": "tool_use", "result": "weak", "step": 0}, {"action_family": "tool_use", "result": "weak", "s... | 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... |
To verify the candidate result for resource limits, which evidence should we retrieve from the Excel sources to confirm the latest value, given schema ambiguity?
Decision: route
History: [{"action_family": "tool_use", "result": "weak", "step": 0}, {"action_family": "tool_use", "result": "weak", "step": 1}]
Plan: {"acti... | 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... |
We have limited steps left. Which operation should we prioritize to resolve the conflicting evidence and missing context?
Decision: route
History: [{"action_family": "tool_use", "result": "weak", "step": 0}]
Plan: {"active": false, "operation": "lookup_exact"}
Agent State: {"phase": "governance", "question_length_band"... | 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... |
The previous attempt was incomplete. What should we do next to reconcile the mismatched results from the inspected sources?
Decision: route
History: [{"action_family": "tool_use", "result": "weak", "step": 0}]
Plan: {"active": false, "operation": "join"}
Agent State: {"phase": "inspection", "question_length_band": "lon... | 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... |
Given the known sources and remaining budget, what operation should we perform to cover the task requirements?
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: {"pha... | 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... |
What is the next operation to determine if we have enough information for the required transformation?
Decision: route
Plan: {"active": false, "operation": "enumerate_records"}
Agent State: {"phase": "synthesis", "question_length_band": "long", "state_name": "contradiction"}
Source State: {"available_modalities": ["cod... | This candidate supports controlled inspection of 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: l... |
Given the verified consistency checks, what should the next action be to confirm the absence of a specific version across all sources?
Decision: route
History: [{"action_family": "tool_use", "result": "weak", "step": 0}, {"action_family": "tool_use", "result": "weak", "step": 1}]
Plan: {"active": false, "operation": "a... | 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 is the best next step to gather information for validating the disputed requirement?
Decision: route
Plan: {"active": true, "operation": "enumerate_records"}
Agent State: {"phase": "planning", "question_length_band": "short", "state_name": "initial"}
Source State: {"available_modalities": ["text", "metadata"], "ev... | 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... |
To select the latest technical instruction from the available documents, which resources should we use?
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... | 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) |
Considering the failure recovery and the need for the latest value, what content should we retrieve 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... | 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... |
Given the trace requirements and code evidence, what read-only operation should I perform next to verify the absence of the exact token, without writing any state?
Decision: route
History: [{"action_family": "tool_use", "result": "weak", "step": 0}, {"action_family": "tool_use", "result": "weak", "step": 1}]
Plan: {"ac... | 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... |
I've already checked two sources for the entity but found only one match. Given the stale assessment and partial inventory, what remaining step should I take to join the missing resource metadata without side effects?
Decision: route
History: [{"action_family": "tool_use", "result": "weak", "step": 0}, {"action_family"... | 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... |
Instead of reading the full CSV contents again, what specific operation should I run to verify the absence of the required fields, given the structural match and stale assessment?
Decision: route
History: [{"action_family": "tool_use", "result": "weak", "step": 0}, {"action_family": "tool_use", "result": "weak", "step"... | 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... |
To verify the join result across mixed sources, what read-only operation should I execute next that compares matching records without altering local state?
Decision: route
History: [{"action_family": "tool_use", "result": "weak", "step": 0}]
Plan: {"active": false, "operation": "join"}
Agent State: {"phase": "governanc... | Invoke the candidate to determine matching records from the available resources.. Capabilities: search structured records, filter records. Accepts: csv, excel, sqlite. Returns: evidence candidates. Evidence role: candidate discovery. Prerequisites: schema known. Constraints: structured source required. Side effects: re... |
With only two steps left, what should I prioritize to identify the sections and structural landmarks in the PDF?
Decision: route
Plan: {"active": false, "operation": "enumerate_sources"}
Agent State: {"phase": "terminal_readiness", "question_length_band": "long", "state_name": "fresh_sufficient"}
Source State: {"availa... | 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... |
The last attempt was incomplete. How can I recover to find the relevant pages or ranges for access rules?
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: {... | 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... |
Which resource should I select next to check consistency across sources, given the catalog?
Decision: route
History: [{"action_family": "tool_use", "result": "weak", "step": 0}, {"action_family": "tool_use", "result": "weak", "step": 1}]
Plan: {"active": false, "operation": "enumerate_records"}
Agent State: {"phase": "... | 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 should I do next to examine symbols and definitions in the code?
Decision: route
Plan: {"active": false, "operation": "compatibility"}
Agent State: {"phase": "inspection", "question_length_band": "short", "state_name": "partial_evidence"}
Source State: {"available_modalities": ["code", "metadata"], "evidence_topol... | 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 stale assessment and the broad query, which of the seven candidate results best satisfies the data quality validation requirement, considering the full context and the CSV source?
Decision: route
History: [{"action_family": "tool_use", "result": "weak", "step": 0}, {"action_family": "tool_use", "result": "wea... | This operation handles a candidate result while preserving the current task state.. Capabilities: inspect evidence, verify provenance. Accepts: evidence candidates. Returns: evidence. Evidence role: evidence inspection. Prerequisites: evidence candidate selected. Constraints: candidate evidence required. Side effects: ... |
Can you show me the surrounding context for the candidate that matches the schema field, given the snippet-only view and the identifier variation issue?
Decision: route
History: [{"action_family": "tool_use", "result": "weak", "step": 0}, {"action_family": "tool_use", "result": "weak", "step": 1}]
Plan: {"active": fals... | 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... |
Do the results from the two complementary sources agree or conflict, and what does that imply for the recovery plan?
Decision: route
History: [{"action_family": "tool_use", "result": "weak", "step": 0}]
Plan: {"active": true, "operation": "join"}
Agent State: {"phase": "planning", "question_length_band": "long", "state... | 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... |
Given the contradictory evidence and the entity-bound query, which candidate covers all the event delivery and retry requirements without side effects, given the code source and partial context?
Decision: route
History: [{"action_family": "tool_use", "result": "weak", "step": 0}, {"action_family": "tool_use", "result":... | 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 contradictory evidence, should I proceed with the final transformation or gather more data? Consider that the operation must not have side effects beyond local state and must output a plan or assessment.
Decision: route
History: [{"action_family": "tool_use", "result": "weak", "step": 0}]... | 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 already checked the identifier-based matches and have partial source inventory. For the remaining schema fields, should I now join the CSV and SQLite sources to produce the terminal result, or is there a need to inspect more evidence first?
Decision: route
History: [{"action_family": "tool_use", "result": "weak",... | 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 inspected multiple sources and exhausted evidence, but the transformation requirements are still partial. Should I plan to gather more information by searching for split contexts, or instead directly assess compatibility and create a schema? The latter seems tempting but may miss needed details.
Decision: route
H... | 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... |
With no evidence observed yet and a complete requirement set, what resources are available to verify the event delivery and retry behavior? I need to know which files or databases to read for evidence, without any side effects.
Decision: route
History: [{"action_family": "tool_use", "result": "weak", "step": 0}, {"acti... | 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 the remaining step budget, what should I prioritize next to select the latest relevant content from the inspected 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... | Invoke the candidate to determine the relevant content from the available resources.. 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... |
My previous attempt was incomplete; what should I do now to recover the exact identifier from the available evidence despite version noise?
Decision: route
Plan: {"active": true, "operation": "lookup_exact"}
Agent State: {"phase": "retrieval", "question_length_band": "long", "state_name": "retrieval"}
Source State: {"a... | 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 catalog operation should I use to fetch the resource metadata and filters needed for the technical instruction, given stale assessments?
Decision: route
History: [{"action_family": "tool_use", "result": "weak", "step": 0}, {"action_family": "tool_use", "result": "weak", "step": 1}]
Plan: {"active": false, "operat... | 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 should I do next to determine the fields, types, and structure from the inspected spreadsheets for failure recovery?
Decision: route
Plan: {"active": false, "operation": "latest_value_selection"}
Agent State: {"phase": "terminal_readiness", "question_length_band": "long", "state_name": "fresh_sufficient"}
Source S... | 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... |
We need to verify the absence of a matching record for the resource limits. Please check the available sources and identify the right next step.
Decision: route
History: [{"action_family": "tool_use", "result": "weak", "step": 0}, {"action_family": "tool_use", "result": "weak", "step": 1}]
Plan: {"active": true, "opera... | 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... |
Given the event delivery and retry behavior, what should we do next to locate the relevant sections?
Decision: route
History: [{"action_family": "tool_use", "result": "weak", "step": 0}]
Plan: {"active": false, "operation": "join"}
Agent State: {"phase": "governance", "question_length_band": "long", "state_name": "insu... | This operation handles sections and structural landmarks while preserving the current task state.. 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... |
I need to transform the data, but the identifier varies. Which operation should we perform next to find the right pages?
Decision: route
History: [{"action_family": "tool_use", "result": "weak", "step": 0}, {"action_family": "tool_use", "result": "weak", "step": 1}]
Plan: {"active": true, "operation": "compatibility"}
... | 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 (... |
We're discovering sources for resource limits, but we have a long document and need to enumerate records. What's the next step?
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"... | 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 current evidence, what should I do next to clarify the symbols and definitions, without modifying any local state?
Decision: route
History: [{"action_family": "tool_use", "result": "weak", "step": 0}, {"action_family": "tool_use", "result": "weak", "step": 1}]
Plan: {"active": true, "operation": "lookup_seman... | This candidate supports controlled inspection of symbols and definitions.. Capabilities: inspect code structure, resolve symbols. Accepts: code. Returns: content, code structure. Evidence role: evidence inspection. Prerequisites: source selected. Constraints: code source required. Side effects: read. Arguments: depth (... |
I've already checked several sources but found only one passage. What remains to be done to validate the candidate result, considering the stale assessment and lexical matching?
Decision: route
History: [{"action_family": "tool_use", "result": "weak", "step": 0}, {"action_family": "tool_use", "result": "weak", "step": ... | 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... |
Should I now retrieve the missing surrounding context to verify absence, or would it be better to finalize the assessment immediately? What's the precise next move?
Decision: route
Plan: {"active": false, "operation": "absence_verification"}
Agent State: {"phase": "synthesis", "question_length_band": "long", "state_nam... | Use this candidate when the task requires 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: result i... |
How can I verify that the selected latest value is correct across all sources, given the version noise and stale assessments?
Decision: route
History: [{"action_family": "tool_use", "result": "weak", "step": 0}]
Plan: {"active": false, "operation": "latest_value_selection"}
Agent State: {"phase": "source_discovery", "q... | 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... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.