anchor
stringlengths
723
2.15k
positive
stringlengths
153
8.2k
Given only 2 steps left and 4 unresolved requirements, should I verify the retrieved evidence is sufficient or gather more? Decision: route Plan: {"active": true, "operation": "join"} Agent State: {"phase": "retrieval", "question_length_band": "long", "state_name": "retrieval"} Source State: {"available_modalities": ["...
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...
The last attempt was incomplete; what should I do next to finalize the join across sources? Decision: route History: [{"action_family": "tool_use", "result": "weak", "step": 0}] Plan: {"active": false, "operation": "join"} Agent State: {"phase": "source_discovery", "question_length_band": "short", "state_name": "source...
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 no remaining steps and partial progress, what is the best way to gather the missing entity details? Decision: route Plan: {"active": true, "operation": "lookup_semantic"} Agent State: {"phase": "planning", "question_length_band": "long", "state_name": "initial"} Source State: {"available_modalities": ["text", "met...
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 I do next to compare the complementary evidence and manage the resource limits? 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",...
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 contradictory snippets, list all candidate content pieces that match the telemetry and trace requirements. 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"} ...
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...
What should be done next to find the exact token or code needed for the data transformation? 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": "to...
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...
Which sources should be inspected to obtain the resource metadata and filters for limits and lifecycle? 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:...
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 Excel file and partial state, enumerate the records and their fields to support the telemetry and trace requirements. Decision: route Plan: {"active": false, "operation": "enumerate_records"} Agent State: {"phase": "synthesis", "question_length_band": "long", "state_name": "contradiction"} Source State: {"ava...
Apply this capability when the next decision depends on fields, types, and structure.. Capabilities: inspect structured schema, discover fields. Accepts: csv, excel, sqlite. Returns: schema. Evidence role: structure discovery. Prerequisites: source selected. Constraints: structured source required. Side effects: read. ...
We need to resolve a contradiction between two records. Which records should be matched next, ensuring no side effects and only read operations? Decision: route History: [{"action_family": "tool_use", "result": "weak", "step": 0}, {"action_family": "tool_use", "result": "weak", "step": 1}] Plan: {"active": false, "oper...
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 checked the first few sections but still need to locate the remaining structural landmarks. What should we inspect next to validate the document's structure? Decision: route History: [{"action_family": "tool_use", "result": "weak", "step": 0}] Plan: {"active": false, "operation": "compatibility"} Agent State: {"p...
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 ...
We're about to pick a page range to examine, but we must avoid modifying any state. What is the correct next step to identify the relevant pages, as opposed to just listing all sources? Decision: route History: [{"action_family": "tool_use", "result": "weak", "step": 0}, {"action_family": "tool_use", "result": "weak", ...
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...
We have inspected multiple sources but need to verify the selected resource's version compatibility. What should we do next to confirm the evidence? Decision: route History: [{"action_family": "tool_use", "result": "weak", "step": 0}, {"action_family": "tool_use", "result": "weak", "step": 1}] Plan: {"active": false, "...
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...
With only 8 steps left and no prior search, which operation should I prioritize to validate symbols and definitions from the inspected code sources? Decision: route Plan: {"active": false, "operation": "enumerate_records"} Agent State: {"phase": "synthesis", "question_length_band": "long", "state_name": "contradiction"...
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 previous attempt was incomplete and ambiguous; which recovery operation should I run next to enumerate records and resolve schema ambiguity for event delivery? Decision: route History: [{"action_family": "tool_use", "result": "weak", "step": 0}, {"action_family": "tool_use", "result": "weak", "step": 1}, {"action_fa...
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...
What catalog or resource lookup should I perform next to find missing surrounding context for field definitions and compatibility? Decision: route History: [{"action_family": "tool_use", "result": "weak", "step": 0}] Plan: {"active": true, "operation": "compatibility"} Agent State: {"phase": "retrieval", "question_leng...
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 is the next action to check agreement or conflict between results from multiple passages? Decision: route History: [{"action_family": "tool_use", "result": "weak", "step": 0}, {"action_family": "tool_use", "result": "weak", "step": 1}] Plan: {"active": true, "operation": "lookup_semantic"} Agent State: {"phase": "...
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...
Compare the four evidence items to see if any field definitions conflict with the schema. 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 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...
Are the access rules in the evidence sufficient to determine the latest permission value? 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_selection"} Agent State: {"phase"...
Invoke the candidate to determine whether available information is sufficient from the available resources.. Capabilities: assess evidence, validate sufficiency. Accepts: evidence, governance state. Returns: assessment. Evidence role: governance assessment. Prerequisites: requirements updated. Constraints: canonical ev...
List all sources that contain validation rules for the data quality checks. 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": "planning", "quest...
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...
Given the partial inventory, which source should we inspect next to find telemetry traces? 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...
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...
Before we proceed, can you check what resources are available for inspecting field definitions and compatibility, without modifying anything? Decision: route Plan: {"active": false, "operation": "lookup_exact"} Agent State: {"phase": "governance", "question_length_band": "long", "state_name": "insufficient"} Source Sta...
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)
We've already searched once and found partial context. What should we inspect next to resolve the disputed workflow step, considering side effects? Decision: route History: [{"action_family": "tool_use", "result": "weak", "step": 0}] Plan: {"active": false, "operation": "compatibility"} Agent State: {"phase": "inspecti...
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...
We're ready to finish. Should we retrieve the exact access token from the code, or instead list all permission records? Decision: route Plan: {"active": false, "operation": "enumerate_records"} Agent State: {"phase": "terminal_readiness", "question_length_band": "long", "state_name": "fresh_sufficient"} Source State: {...
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 access rule by inspecting metadata and filters from the database, without causing side effects? Decision: route History: [{"action_family": "tool_use", "result": "weak", "step": 0}] Plan: {"active": true, "operation": "lookup_semantic"} Agent State: {"phase": "retrieval", "question_length_band": "...
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, which next operation should prioritize identifying fields, types, and structure from mixed sources? Decision: route History: [{"action_family": "tool_use", "result": "weak", "step": 0}] Plan: {"active": false, "operation": "latest_value_selection"} Agent State: {"phase": "source_discovery", "questi...
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 incomplete attempt, what next operation can recover and enumerate matching records from mixed 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": "long...
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...
What next operation should inspect sections and structural landmarks across the available documents? 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...
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 (...
What is the next operation to determine compatibility and identify relevant pages or ranges for the workflow? Decision: route Plan: {"active": false, "operation": "compatibility"} Agent State: {"phase": "terminal_readiness", "question_length_band": "long", "state_name": "fresh_sufficient"} Source State: {"available_mod...
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...
What should be done next with the selected resource to inspect its access rules and permissions? Decision: route Plan: {"active": false, "operation": "join"} Agent State: {"phase": "inspection", "question_length_band": "short", "state_name": "partial_evidence"} Source State: {"available_modalities": ["csv", "metadata"]...
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...
What is the next step to locate the relevant technical instruction, focusing on symbols and definitions? Decision: route Plan: {"active": false, "operation": "enumerate_sources"} Agent State: {"phase": "terminal_readiness", "question_length_band": "long", "state_name": "fresh_sufficient"} Source State: {"available_moda...
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...
How should we resolve the contradiction in the candidate result regarding validation and quality constraints? Decision: route History: [{"action_family": "tool_use", "result": "weak", "step": 0}] Plan: {"active": false, "operation": "contradiction_resolution"} Agent State: {"phase": "terminal_readiness", "question_leng...
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...
What should be done next to verify the absence of event delivery and retry behavior, given the missing surrounding context? Decision: route History: [{"action_family": "tool_use", "result": "weak", "step": 0}, {"action_family": "tool_use", "result": "weak", "step": 1}] Plan: {"active": false, "operation": "absence_veri...
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 conflicting results from the four inspected sources, what should the next step be to determine whether the event delivery and retry behavior meet the requirements? Decision: route History: [{"action_family": "tool_use", "result": "weak", "step": 0}, {"action_family": "tool_use", "result": "weak", "step": 1}, ...
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...
After checking snippets from the PDF, what remains to be verified about version compatibility coverage? 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 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...
Given the current evidence is fresh and the schema is ambiguous, should we proceed with a detailed schema analysis or is there a more direct lookup to determine access permissions? 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 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 selected result for access control given the contradictory evidence and schema ambiguity? 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 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 our limited remaining steps, which next move best verifies the absence of the specified identifier in the current evidence? Decision: route History: [{"action_family": "tool_use", "result": "weak", "step": 0}, {"action_family": "tool_use", "result": "weak", "step": 1}] Plan: {"active": true, "operation": "absence...
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 that incomplete attempt, what resources can we still use to resolve the join between the two identifiers? 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 catalog entry holds the relevant content for enumerating records matching this exact identifier, given our unknown inventory? Decision: route History: [{"action_family": "tool_use", "result": "weak", "step": 0}, {"action_family": "tool_use", "result": "weak", "step": 1}, {"action_family": "tool_use", "result": "w...
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 locate the exact name, code, or token that verifies its absence in the current source? 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"}...
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...
Find the schema metadata for the versioned source and list candidates that match the version compatibility filter. 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_selectio...
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)
Look up the exact identifier in the SQLite source and retrieve its schema and content for failure recovery. Decision: route History: [{"action_family": "tool_use", "result": "weak", "step": 0}] Plan: {"active": false, "operation": "lookup_semantic"} Agent State: {"phase": "governance", "question_length_band": "long", "...
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:...
Match records from the CSV and Excel sources by exact identifier to resolve the schema field definitions. Decision: route Plan: {"active": false, "operation": "join"} Agent State: {"phase": "governance", "question_length_band": "long", "state_name": "insufficient"} Source State: {"available_modalities": ["csv", "metada...
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...
In the PDF, verify the absence of the required data transformation section and identify structural landmarks for planning. Decision: route History: [{"action_family": "tool_use", "result": "weak", "step": 0}, {"action_family": "tool_use", "result": "weak", "step": 1}] Plan: {"active": true, "operation": "absence_verifi...
Apply this capability when the next decision depends on sections and structural landmarks.. Capabilities: inspect document structure, discover sections. Accepts: pdf. Returns: document structure. Evidence role: structure discovery. Prerequisites: source selected. Constraints: pdf source required. Side effects: read. Ar...
We've exhausted the evidence and have a stale assessment. Which operation should I run next to locate the relevant pages or ranges, ensuring it's read-only and handles mixed text/PDF sources? Decision: route History: [{"action_family": "tool_use", "result": "weak", "step": 0}, {"action_family": "tool_use", "result": "w...
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 checked the SQLite evidence but haven't assessed it. What should I do next to select the resource for event delivery, considering we've already done two searches and need to verify absence? Decision: route History: [{"action_family": "tool_use", "result": "weak", "step": 0}, {"action_family": "tool_use", "result"...
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 full context but need to resolve a dispute. Should I extract symbols and definitions from the single passage, or is there a better next step that avoids the tempting but wrong schema-only alternative? Decision: route History: [{"action_family": "tool_use", "result": "weak", "step": 0}] Plan: {"active": false, "...
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 a complete requirement and stale assessment. How can I verify the candidate result for field definitions and compatibility, ensuring the operation is read-only and avoids near-duplicate pitfalls? Decision: route History: [{"action_family": "tool_use", "result": "weak", "step": 0}] Plan: {"active": true, "operat...
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...
Given my remaining step budget is zero, which operation should I prioritize to obtain the missing surrounding context for the entity-bound lookup? Decision: route Plan: {"active": true, "operation": "lookup_exact"} Agent State: {"phase": "retrieval", "question_length_band": "long", "state_name": "retrieval"} Source Sta...
The operation produces a reliable result for missing surrounding context under current constraints.. Capabilities: expand context, resolve split context. Accepts: evidence candidates, evidence. Returns: evidence. Evidence role: context expansion. Prerequisites: evidence candidate selected. Constraints: incomplete conte...
My prior attempt was incomplete; how should I recover to compare the semantic lookup results for agreement or conflict, given only two steps remain? Decision: route History: [{"action_family": "tool_use", "result": "weak", "step": 0}] Plan: {"active": true, "operation": "lookup_semantic"} Agent State: {"phase": "planni...
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...
What catalog or resource operation should I use next to enumerate the available records and ensure task requirement coverage, without naming any specific tool? Decision: route Plan: {"active": false, "operation": "enumerate_records"} Agent State: {"phase": "terminal_readiness", "question_length_band": "long", "state_na...
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 action to verify whether the available information is sufficient, given the contradictory evidence and one step left? 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 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...
Based on the current access control evidence, what is the next action to retrieve the exact permission rule? Decision: route Plan: {"active": true, "operation": "lookup_exact"} Agent State: {"phase": "retrieval", "question_length_band": "long", "state_name": "retrieval"} Source State: {"available_modalities": ["excel",...
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 most appropriate next step to gather the latest technical instruction from the relevant documents? Decision: route Plan: {"active": true, "operation": "latest_value_selection"} Agent State: {"phase": "retrieval", "question_length_band": "long", "state_name": "retrieval"} Source State: {"available_modalities...
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 satisfy the telemetry and trace requirements, what resources are available for the next step? Decision: route History: [{"action_family": "tool_use", "result": "weak", "step": 0}, {"action_family": "tool_use", "result": "weak", "step": 1}] Plan: {"active": false, "operation": "lookup_exact"} Agent State: {"phase": "...
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)
What content should be selected next to determine resource limits and lifecycle, given the constraint of read-only operations? 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 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 telemetry trace requirements, I've inspected multiple sources but found identifier variations. What next operation should I perform to locate the exact name, code, or token, without modifying any local state? Decision: route History: [{"action_family": "tool_use", "result": "weak", "step": 0}] Plan: {"active"...
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 several sources and found near-duplicates. For the validation and quality constraints, what operation should I do next to select the latest value, considering that my previous assessments are stale? Decision: route History: [{"action_family": "tool_use", "result": "weak", "step": 0}, {"action_famil...
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've examined the full context but haven't seen any evidence yet. For schema management, what should I do next to compare field definitions and compatibility, as opposed to just listing all sources? Decision: route History: [{"action_family": "tool_use", "result": "weak", "step": 0}, {"action_family": "tool_use", "resu...
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...
For the required data transformation, I need to verify the matching records. What operation should I perform next to confirm the exact matches, given that I have not yet observed any evidence? Decision: route History: [{"action_family": "tool_use", "result": "weak", "step": 0}] Plan: {"active": false, "operation": "loo...
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 2 steps left and a disputed requirement, which inspection should I prioritize to compare complementary PDF sources by their section landmarks? Decision: route History: [{"action_family": "tool_use", "result": "weak", "step": 0}, {"action_family": "tool_use", "result": "weak", "step": 1}, {"action_family": "to...
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...
After a partial attempt with no steps left, how can I recover by enumerating all sources and locating the relevant pages across mixed formats? Decision: route Plan: {"active": true, "operation": "enumerate_sources"} Agent State: {"phase": "planning", "question_length_band": "long", "state_name": "initial"} Source 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...
For consistency checks across code sources, which resource should I select next to resolve contradictions using exact identifiers? Decision: route History: [{"action_family": "tool_use", "result": "weak", "step": 0}, {"action_family": "tool_use", "result": "weak", "step": 1}] Plan: {"active": false, "operation": "contr...
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...
With complete requirements but stale assessment, what next action should enumerate sources to verify 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": "terminal_readine...
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)...
Which candidate result should I inspect next to resolve the contradiction, given my current evidence and the resource limits? Decision: route Plan: {"active": false, "operation": "contradiction_resolution"} Agent State: {"phase": "terminal_readiness", "question_length_band": "long", "state_name": "fresh_sufficient"} So...
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: ...
What should I do to get the missing surrounding context for the latest value selection, given the long document issue? 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_sele...
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...
Which evidence comparison should I perform to determine if the two results agree or conflict, given the split context and 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",...
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 disputed requirements and the need for failure recovery, what plan should I form to ensure task coverage and handle the failure? Decision: route History: [{"action_family": "tool_use", "result": "weak", "step": 0}, {"action_family": "tool_use", "result": "weak", "step": 1}, {"action_family": "tool_use", "resu...
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...
We have CSV records but need to know if we have enough evidence to decide on retry behavior. Should we proceed with assessment or gather more? 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 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...
Given we've already checked some sources and have partial context, what should we do next to get the exact event delivery details? Decision: route History: [{"action_family": "tool_use", "result": "weak", "step": 0}, {"action_family": "tool_use", "result": "weak", "step": 1}] Plan: {"active": false, "operation": "looku...
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 need to resolve a contradiction about event handling. Should we inspect the codebase for the exact identifier, or would searching the evidence candidates be more appropriate? Decision: route History: [{"action_family": "tool_use", "result": "weak", "step": 0}] Plan: {"active": true, "operation": "contradiction_resol...
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 opt...
We need to verify version compatibility. What resources are available to confirm the correct event version? Decision: route History: [{"action_family": "tool_use", "result": "weak", "step": 0}] Plan: {"active": true, "operation": "compare"} Agent State: {"phase": "retrieval", "question_length_band": "long", "state_name...
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 partial context and only 8 steps left, which content should I prioritize to resolve the remaining requirements? Decision: route History: [{"action_family": "tool_use", "result": "weak", "step": 0}] Plan: {"active": true, "operation": "lookup_semantic"} Agent State: {"phase": "planning", "question_length_band"...
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; how should I proceed to verify the exact token across contradictory sources? Decision: route History: [{"action_family": "tool_use", "result": "weak", "step": 0}, {"action_family": "tool_use", "result": "weak", "step": 1}] Plan: {"active": false, "operation": "compare"} Agent State: ...
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 should I use to locate the latest version of the needed data? Decision: route History: [{"action_family": "tool_use", "result": "weak", "step": 0}] Plan: {"active": false, "operation": "latest_value_selection"} Agent State: {"phase": "synthesis", "question_length_band": "short", "sta...
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 fields, types, and structure should I inspect next to resolve the identifier variation? Decision: route History: [{"action_family": "tool_use", "result": "weak", "step": 0}, {"action_family": "tool_use", "result": "weak", "step": 1}] Plan: {"active": true, "operation": "lookup_exact"} Agent State: {"phase": "retri...
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...
Find the matching records for the entity in the schema definitions. 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": "weak"...
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...
What are the structural sections in the document for event handling? 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": "planning", "question_len...
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 the exact pages covering failure recovery procedures. Decision: route Plan: {"active": true, "operation": "lookup_exact"} Agent State: {"phase": "planning", "question_length_band": "short", "state_name": "initial"} Source State: {"available_modalities": ["pdf", "metadata"], "evidence_topology_observed": "none_ob...
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 conflicting evidence, what is the next step in the workflow? 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", "q...
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 planning phase and complete requirements, what next operation should resolve the contradiction between code symbols and definitions without side effects beyond reading? Decision: route History: [{"action_family": "tool_use", "result": "weak", "step": 0}, {"action_family": "tool_use", "result": "weak", "step":...
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 (...
We've already checked 8 evidence snippets and have one unresolved requirement; what remains to be done to resolve the paraphrase obstacle and ensure consistency across sources? Decision: route History: [{"action_family": "tool_use", "result": "weak", "step": 0}] Plan: {"active": true, "operation": "contradiction_resolu...
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...
Instead of searching for more sources, what should we do next to find the missing context around the exact identifier, given the stale assessment and known inventory? Decision: route History: [{"action_family": "tool_use", "result": "weak", "step": 0}, {"action_family": "tool_use", "result": "weak", "step": 1}] Plan: {...
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 should we verify the agreement or conflict between the results from multiple sources, given the contradictory evidence and disputed requirements? Decision: route History: [{"action_family": "tool_use", "result": "weak", "step": 0}, {"action_family": "tool_use", "result": "weak", "step": 1}] Plan: {"active": false, ...
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 2 steps left and 4 requirements unresolved, which next operation should I prioritize to cover the most missing 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"...
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...
After inspecting multiple sources but still lacking a clear comparison, what should I do next to determine if I have enough information for the required transformation? Decision: route Plan: {"active": false, "operation": "compare"} Agent State: {"phase": "synthesis", "question_length_band": "long", "state_name": "cont...
Apply this capability when the next decision depends on 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 ...
Since requirements are complete but I need to verify absence, what next operation should I perform to select the appropriate 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", "res...
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 ...
With partial progress and limited steps, what is the best next information-gathering operation to advance my planning? Decision: route Plan: {"active": true, "operation": "compare"} Agent State: {"phase": "planning", "question_length_band": "long", "state_name": "initial"} Source State: {"available_modalities": ["text"...
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...
Which available resource best matches the access rules and permissions we need to compare? Decision: route History: [{"action_family": "tool_use", "result": "weak", "step": 0}, {"action_family": "tool_use", "result": "weak", "step": 1}] Plan: {"active": false, "operation": "compare"} Agent State: {"phase": "governance"...
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)
What should we look at to see if the technical instruction fits 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, "operation": "compatibility"} Agent State: {"phase": "synthesis", "...
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 find the exact code or token that appears consistently across the sources. Which one should I check? Decision: route History: [{"action_family": "tool_use", "result": "weak", "step": 0}] Plan: {"active": false, "operation": "join"} Agent State: {"phase": "inspection", "question_length_band": "long", "state_na...
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...
Given the partial progress and unresolved requirements, which resource's metadata and filters should we use to proceed with the next workflow step? Decision: route History: [{"action_family": "tool_use", "result": "weak", "step": 0}] Plan: {"active": false, "operation": "enumerate_sources"} Agent State: {"phase": "term...
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...
List all source files that contain fields for the exact identifier, but only from read-only CSV or SQLite sources, without modifying anything. Decision: route Plan: {"active": true, "operation": "enumerate_sources"} Agent State: {"phase": "retrieval", "question_length_band": "long", "state_name": "retrieval"} Source St...
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...
Given that I've already inspected two complementary sources, what remains to match the schema-bound records in the CSV, considering the split context? Decision: route History: [{"action_family": "tool_use", "result": "weak", "step": 0}] Plan: {"active": false, "operation": "contradiction_resolution"} Agent State: {"pha...
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 ...
Instead of extracting all content, what sections or structural landmarks should I enumerate next to compare field definitions across the mixed sources? Decision: route History: [{"action_family": "tool_use", "result": "weak", "step": 0}, {"action_family": "tool_use", "result": "weak", "step": 1}] Plan: {"active": true,...
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...
How can I verify the resource limits and lifecycle by inspecting the relevant pages in the PDF, given the version noise? 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 St...
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 (...
With only 4 steps left, which candidate should I prioritize to compare evidence across sources? 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": "plannin...
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...
My last attempt was incomplete; can you help me find the exact field definitions and check compatibility? Decision: route Plan: {"active": false, "operation": "lookup_exact"} Agent State: {"phase": "source_discovery", "question_length_band": "long", "state_name": "source_discovery"} Source State: {"available_modalities...
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...
I need to enumerate records from a catalog, but the schema is ambiguous. What should I do 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_records"} Agent State: {"phase...
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...
What is the next action to resolve the contradiction and validate the quality constraints? 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...
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...