anchor
stringlengths
723
2.15k
positive
stringlengths
153
8.2k
With zero steps left and four requirements unresolved, which pages or ranges should I prioritize to resolve 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": "we...
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 (...
My earlier attempt was incomplete; which resource should I inspect next to join and verify consistency across sources? Decision: route Plan: {"active": true, "operation": "join"} Agent State: {"phase": "retrieval", "question_length_band": "long", "state_name": "retrieval"} Source State: {"available_modalities": ["text"...
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...
Which source holds the symbols and definitions needed to resolve the contradiction before finishing? Decision: route Plan: {"active": false, "operation": "contradiction_resolution"} Agent State: {"phase": "terminal_readiness", "question_length_band": "long", "state_name": "fresh_sufficient"} Source State: {"available_m...
Apply this capability when the next decision depends on symbols and definitions.. Capabilities: inspect code structure. Accepts: code. Returns: content, code structure. Evidence role: evidence inspection. Prerequisites: source selected. Constraints: code source required. Side effects: read. Arguments: depth (integer re...
What should I do next to join the evidence and produce a candidate result for field definitions? Decision: route Plan: {"active": false, "operation": "join"} Agent State: {"phase": "synthesis", "question_length_band": "short", "state_name": "contradiction"} Source State: {"available_modalities": ["code", "metadata"], "...
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...
Find the passages that give the surrounding context for the entity we're tracking. Decision: route Plan: {"active": false, "operation": "enumerate_records"} Agent State: {"phase": "terminal_readiness", "question_length_band": "short", "state_name": "fresh_sufficient"} Source State: {"available_modalities": ["text", "me...
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...
Check if the two sources agree on the value we need. Decision: route History: [{"action_family": "tool_use", "result": "weak", "step": 0}] Plan: {"active": false, "operation": "lookup_exact"} Agent State: {"phase": "source_discovery", "question_length_band": "short", "state_name": "source_discovery"} Source State: {"av...
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...
List all the sources that could cover the remaining requirement. Decision: route History: [{"action_family": "tool_use", "result": "weak", "step": 0}] Plan: {"active": true, "operation": "enumerate_sources"} Agent State: {"phase": "planning", "question_length_band": "short", "state_name": "initial"} Source State: {"ava...
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...
Do we have enough evidence to settle the disputed requirement? Decision: route History: [{"action_family": "tool_use", "result": "weak", "step": 0}, {"action_family": "tool_use", "result": "weak", "step": 1}] Plan: {"active": false, "operation": "enumerate_sources"} Agent State: {"phase": "inspection", "question_length...
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 ...
Given the current evidence, what should the next action be to select the latest value while avoiding side effects? 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...
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 have checked the schema; what remains to resolve the contradiction before planning the transformation? Decision: route Plan: {"active": true, "operation": "contradiction_resolution"} Agent State: {"phase": "planning", "question_length_band": "long", "state_name": "initial"} Source State: {"available_modalities": ["s...
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...
Between reading the source list and inspecting the schema, which is the precise next move for validation? 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...
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)
How should we verify the telemetry records by inspecting the relevant content from the database? 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: {"phas...
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...
With only 8 steps left, what's the best move to pinpoint that exact version token from the CSV? 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": "re...
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...
Our last attempt was incomplete; how should we proceed to correctly identify the resource metadata for access rules? Decision: route Plan: {"active": false, "operation": "compatibility"} Agent State: {"phase": "synthesis", "question_length_band": "long", "state_name": "contradiction"} Source State: {"available_modaliti...
Apply this capability when the next decision depends on resource metadata and filters.. 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 (object opt...
What resource should we consult next to understand the fields and types for our validation 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_f...
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 we do next to find the matching record for the latest field definition? Decision: route History: [{"action_family": "tool_use", "result": "weak", "step": 0}] Plan: {"active": false, "operation": "latest_value_selection"} Agent State: {"phase": "inspection", "question_length_band": "short", "state_name": "pa...
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 ...
List the section headings and structural landmarks from the inspected files to guide recovery. Decision: route Plan: {"active": false, "operation": "enumerate_sources"} Agent State: {"phase": "synthesis", "question_length_band": "short", "state_name": "contradiction"} Source State: {"available_modalities": ["text", "pd...
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...
Which pages or ranges contain the conflicting details that need reconciling? Decision: route Plan: {"active": false, "operation": "contradiction_resolution"} Agent State: {"phase": "governance", "question_length_band": "short", "state_name": "insufficient"} Source State: {"available_modalities": ["text", "pdf", "csv", ...
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 need to confirm the correct version of the resource; which one should I use? 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_o...
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 governance check and mixed sources, what symbols and definitions need to be compared for consistency? 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_selec...
The operation produces a reliable result for symbols and definitions under current constraints.. Capabilities: inspect code structure. Accepts: code. Returns: content, code structure. Evidence role: evidence inspection. Prerequisites: source selected. Constraints: code source required. Side effects: read. Arguments: de...
Given the stale assessment and partial source inventory, should I enumerate candidate sources next, ensuring no local state is written? Decision: route History: [{"action_family": "tool_use", "result": "weak", "step": 0}] Plan: {"active": false, "operation": "enumerate_sources"} Agent State: {"phase": "source_discovery...
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...
Since we've checked 8 evidence items and found contradictions, what's the next step to gather missing context around the telemetry and trace requirements? Decision: route Plan: {"active": false, "operation": "enumerate_sources"} Agent State: {"phase": "governance", "question_length_band": "long", "state_name": "insuffi...
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...
We have two candidates with overlapping capabilities; which one should we use to look up the exact resource limit, rather than comparing schemas? Decision: route History: [{"action_family": "tool_use", "result": "weak", "step": 0}, {"action_family": "tool_use", "result": "weak", "step": 1}] Plan: {"active": true, "oper...
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 recovery task requirements are fully covered, given the stale assessment and split context? 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...
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...
With only one step left, should I finalize with the current evidence 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, "operation": "latest_value_selection"} Agent State: {"phase": "te...
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 resolve the ambiguity? Decision: route History: [{"action_family": "tool_use", "result": "weak", "step": 0}] Plan: {"active": false, "operation": "compatibility"} Agent State: {"phase": "governance", "question_length_band": "short", "state_name": "insufficient"}...
The operation produces a reliable result for the selected result or next action under current constraints.. Capabilities: finalize selection. Accepts: assessment, governance state. Returns: terminal result. Evidence role: terminal decision. Prerequisites: requirements complete. Constraints: fresh sufficient assessment ...
Which available source should I consult next for the telemetry details? Decision: route History: [{"action_family": "tool_use", "result": "weak", "step": 0}] Plan: {"active": true, "operation": "lookup_semantic"} Agent State: {"phase": "planning", "question_length_band": "short", "state_name": "initial"} Source State: ...
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 is the next action to advance the workflow? 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", "step": 3}] Plan:...
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)
We found conflicting details in the CSV and PDF sources; what should we inspect next to resolve the exact identifier? Decision: route Plan: {"active": false, "operation": "lookup_exact"} Agent State: {"phase": "synthesis", "question_length_band": "long", "state_name": "contradiction"} Source State: {"available_modaliti...
Use this candidate when the task requires the relevant content.. Capabilities: search content. Accepts: text, pdf. Returns: evidence candidates. Evidence role: candidate discovery. Prerequisites: query available. Constraints: indexed sources required. Side effects: read. Arguments: limit (integer optional), query (stri...
After checking two PDFs, we still lack the exact token; what operation should we run to find that precise code? 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 St...
Invoke the candidate to determine an exact name, code, or token from the available resources.. Capabilities: exact pattern search, identifier search. Accepts: text, code. Returns: evidence candidates. Evidence role: candidate discovery. Prerequisites: query available. Constraints: textual source required. Side effects:...
To meet the quality rules, we need the latest metadata from the text sources; what should we do next to get that resource info? Decision: route History: [{"action_family": "tool_use", "result": "weak", "step": 0}] Plan: {"active": false, "operation": "latest_value_selection"} Agent State: {"phase": "synthesis", "questi...
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 contradictory schema definitions in the CSV files, how should we reconcile the field structure before finalizing? 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 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 current source inventory and the need to enumerate matching records from the Excel source without side effects beyond reading, what operation should be performed next? Decision: route History: [{"action_family": "tool_use", "result": "weak", "step": 0}, {"action_family": "tool_use", "result": "weak", "step": ...
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...
After checking several sources and finding no evidence due to identifier variations, what should be done next to recover and compare sections in the PDF? Decision: route History: [{"action_family": "tool_use", "result": "weak", "step": 0}, {"action_family": "tool_use", "result": "weak", "step": 1}, {"action_family": "t...
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 ...
With multiple passages and a split context, should we enumerate records from the mixed sources or focus on extracting the relevant pages? Which is the correct next move? Decision: route Plan: {"active": true, "operation": "enumerate_records"} Agent State: {"phase": "retrieval", "question_length_band": "long", "state_na...
This operation handles the relevant pages or ranges while preserving the current task state.. Capabilities: search document pages, retrieve passages. Accepts: pdf. Returns: evidence candidates. Evidence role: candidate discovery. Prerequisites: source selected. Constraints: pdf source required. Side effects: read. Argu...
To verify consistency across sources, what operation should we perform next to join the evidence and produce a terminal result? Decision: route History: [{"action_family": "tool_use", "result": "weak", "step": 0}, {"action_family": "tool_use", "result": "weak", "step": 1}] Plan: {"active": false, "operation": "join"} A...
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...
I have one step left and need to map symbols to definitions across mixed telemetry sources. Which next operation should I prioritize? Decision: route Plan: {"active": false, "operation": "enumerate_records"} Agent State: {"phase": "synthesis", "question_length_band": "long", "state_name": "contradiction"} Source State:...
Invoke the candidate to determine symbols and definitions from the available resources.. Capabilities: inspect code structure. Accepts: code. Returns: content, code structure. Evidence role: evidence inspection. Prerequisites: source selected. Constraints: code source required. Side effects: read. Arguments: depth (int...
My previous attempt was incomplete. I need to verify if a candidate field definition is compatible across SQLite sources. What should I try next? Decision: route History: [{"action_family": "tool_use", "result": "weak", "step": 0}, {"action_family": "tool_use", "result": "weak", "step": 1}] Plan: {"active": false, "ope...
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 find the missing context around a schema entry to ensure consistency across CSV sources. What kind of operation should I request? Decision: route Plan: {"active": false, "operation": "compatibility"} Agent State: {"phase": "governance", "question_length_band": "long", "state_name": "insufficient"} Source Stat...
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...
With two steps left, I must decide if resource limits conflict across Excel files. What next action should I take? Decision: route Plan: {"active": false, "operation": "latest_value_selection"} Agent State: {"phase": "governance", "question_length_band": "long", "state_name": "insufficient"} Source State: {"available_m...
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...
We have a near-duplicate candidate and need to compare evidence to ensure all event delivery and retry requirements are covered. What should we do next? Decision: route Plan: {"active": false, "operation": "compare"} Agent State: {"phase": "terminal_readiness", "question_length_band": "long", "state_name": "fresh_suffi...
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...
We need to determine if the available information is sufficient for failure recovery, given the schema ambiguity. 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"...
This operation handles whether available information is sufficient while preserving the current task state.. Capabilities: assess evidence. Accepts: evidence, governance state. Returns: assessment. Evidence role: governance assessment. Prerequisites: requirements updated. Constraints: canonical evidence set required. S...
To manage resource limits and lifecycle, we need to verify the absence of a specific identifier. What should we 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": "absence_verific...
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...
For the next workflow step, we need to verify absence using a hybrid match, but the evidence is contradictory. What information-gathering step should we take? Decision: route History: [{"action_family": "tool_use", "result": "weak", "step": 0}, {"action_family": "tool_use", "result": "weak", "step": 1}] Plan: {"active"...
The operation produces a reliable result for the best next information-gathering step under current constraints.. Capabilities: plan retrieval. Accepts: agent state, text. Returns: plan. Evidence role: none. Prerequisites: objective available. Constraints: none. Side effects: local state write. Arguments: objective (st...
Given the stale assessment and mixed sources, what read-only operation can surface available resources without side effects, focusing on field definitions and compatibility? 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 the available resources.. Capabilities: list sources, discover sources. Accepts: metadata. Returns: source list. Evidence role: source discovery. Prerequisites: none. Constraints: none. Side effects: read. Arguments: filters (object required), scope (string optional)
We've checked only two pieces of evidence so far; what remains to be done to locate exact content across the PDFs, given the disputed requirements and limited steps? Decision: route History: [{"action_family": "tool_use", "result": "weak", "step": 0}] Plan: {"active": false, "operation": "lookup_exact"} Agent State: {"...
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...
Instead of jumping to the final step, what intermediate inspection should identify the exact workflow token, using structural matching across the PDFs? Decision: route History: [{"action_family": "tool_use", "result": "weak", "step": 0}, {"action_family": "tool_use", "result": "weak", "step": 1}] Plan: {"active": false...
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 join result by inspecting metadata and filters across the CSV sources, ensuring the transformation is correct? Decision: route History: [{"action_family": "tool_use", "result": "weak", "step": 0}, {"action_family": "tool_use", "result": "weak", "step": 1}, {"action_family": "tool_use", "result": "...
This operation handles resource metadata and filters while preserving the current task state.. Capabilities: search metadata. Accepts: metadata. Returns: source list. Evidence role: source discovery. Prerequisites: none. Constraints: metadata catalog required. Side effects: read. Arguments: filters (object required), s...
Given 2 steps left and 4 unresolved telemetry requirements, which operation should I prioritize to enumerate records from CSV sources, focusing on fields, types, and structure? Decision: route History: [{"action_family": "tool_use", "result": "weak", "step": 0}, {"action_family": "tool_use", "result": "weak", "step": 1...
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, how should I recover to select the latest matching records across mixed formats, focusing on matching records for resource limits? Decision: route History: [{"action_family": "tool_use", "result": "weak", "step": 0}] Plan: {"active": false, "operation": "latest_value_selection"} Agent State...
Apply this capability when the next decision depends on matching records.. 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: read. Arg...
In the governance phase, what catalog-oriented operation should I request to compare sections and structural landmarks in PDF sources for field definitions? Decision: route History: [{"action_family": "tool_use", "result": "weak", "step": 0}, {"action_family": "tool_use", "result": "weak", "step": 1}] Plan: {"active": ...
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 concise next action should I take to enumerate records from PDF sources, focusing on relevant pages or ranges for telemetry requirements? Decision: route History: [{"action_family": "tool_use", "result": "weak", "step": 0}, {"action_family": "tool_use", "result": "weak", "step": 1}, {"action_family": "tool_use", "...
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...
Which source should I enumerate records from to validate the entity? Decision: route Plan: {"active": false, "operation": "enumerate_records"} Agent State: {"phase": "source_discovery", "question_length_band": "short", "state_name": "source_discovery"} Source State: {"available_modalities": ["text", "metadata"], "evide...
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...
Which definition matches the trace structure? 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", "step": 3}] Plan: {"...
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...
What do I need to inspect to understand the access rules? Decision: route Plan: {"active": false, "operation": "join"} Agent State: {"phase": "inspection", "question_length_band": "short", "state_name": "partial_evidence"} Source State: {"available_modalities": ["pdf", "metadata"], "evidence_topology_observed": "one_pa...
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 is the next operation to select the latest value while considering resource limits? Decision: route Plan: {"active": true, "operation": "latest_value_selection"} Agent State: {"phase": "planning", "question_length_band": "short", "state_name": "initial"} Source State: {"available_modalities": ["excel", "metadata"]...
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...
We have inspected multiple sources and found conflicting evidence. What operation should we perform next to compare the results, given that we need to join data from mixed modalities without altering local state? Decision: route History: [{"action_family": "tool_use", "result": "weak", "step": 0}, {"action_family": "to...
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 fields and have partial coverage. What should we do next to determine if the remaining schema definitions are compatible, considering we haven't done any prior searches? Decision: route Plan: {"active": false, "operation": "compatibility"} Agent State: {"phase": "terminal_readiness", "questio...
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...
We have partial context and need to resolve a contradiction, but we're considering doing another search. However, we have limited steps left. What is the precise next operation to assess if we have enough information, rather than searching again? Decision: route History: [{"action_family": "tool_use", "result": "weak",...
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...
We have completed all requirements and have fresh evidence. How should we verify the final result by checking the evidence against the access rules, given that we have no remaining steps? Decision: route History: [{"action_family": "tool_use", "result": "weak", "step": 0}, {"action_family": "tool_use", "result": "weak"...
Invoke the candidate to determine the selected result or next action from the available resources.. Capabilities: finalize selection, emit terminal result. Accepts: assessment, governance state. Returns: terminal result. Evidence role: terminal decision. Prerequisites: requirements complete. Constraints: fresh sufficie...
With 4 steps left, what should I prioritize to fill gaps in field definitions and compatibility? Decision: route Plan: {"active": true, "operation": "enumerate_records"} Agent State: {"phase": "planning", "question_length_band": "short", "state_name": "initial"} Source State: {"available_modalities": ["csv", "metadata"...
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...
My last attempts were incomplete; what resources are available to verify absence of 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": "absence_verification"} Agent...
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 entries describe resource limits and lifecycle for this entity? Decision: route Plan: {"active": true, "operation": "join"} Agent State: {"phase": "retrieval", "question_length_band": "short", "state_name": "retrieval"} Source State: {"available_modalities": ["csv", "metadata"], "evidence_topology_observe...
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 exact version token to check compatibility? Decision: route History: [{"action_family": "tool_use", "result": "weak", "step": 0}] Plan: {"active": false, "operation": "compatibility"} Agent State: {"phase": "source_discovery", "question_length_band": "short", "state_name": "source_discovery"} Source State: ...
This candidate supports controlled inspection of an exact name, code, or token.. Capabilities: exact pattern search. Accepts: text, code. Returns: evidence candidates. Evidence role: candidate discovery. Prerequisites: query available. Constraints: textual source required. Side effects: read. Arguments: case sensitive ...
Given the stale assessment and known source inventory, what next operation should inspect the resource metadata and filters to resolve version noise? Decision: route History: [{"action_family": "tool_use", "result": "weak", "step": 0}, {"action_family": "tool_use", "result": "weak", "step": 1}] Plan: {"active": false, ...
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)
We need to reconcile contradictory evidence and recover from failure. What should we do next to examine fields, types, and structure? Decision: route History: [{"action_family": "tool_use", "result": "weak", "step": 0}, {"action_family": "tool_use", "result": "weak", "step": 1}, {"action_family": "tool_use", "result": ...
This operation handles fields, types, and structure while preserving the current task state.. Capabilities: inspect structured schema. Accepts: csv, excel, sqlite. Returns: schema. Evidence role: structure discovery. Prerequisites: source selected. Constraints: structured source required. Side effects: read. Arguments:...
To meet telemetry and trace requirements, what next operation should enumerate matching records from known sources? Decision: route History: [{"action_family": "tool_use", "result": "weak", "step": 0}] Plan: {"active": true, "operation": "enumerate_sources"} Agent State: {"phase": "planning", "question_length_band": "l...
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 complete requirements and partial source inventory, what next operation should locate sections and structural landmarks to find the relevant technical instruction? Decision: route History: [{"action_family": "tool_use", "result": "weak", "step": 0}, {"action_family": "tool_use", "result": "weak", "step": 1}] Plan...
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 mixed sources inspected, which operation should I run next to join the evidence and identify the relevant pages or ranges, ensuring no side effects beyond reading and local state writes? Decision: route History: [{"action_family": "tool_use", "result": "weak", "step": 0}, {"action_family": "tool_use", "result...
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...
Since I've already checked snippets from complementary sources and found near-duplicates, what operation should I perform next on the selected resource to verify consistency across the SQLite sources, using metadata filters, without altering external state? Decision: route History: [{"action_family": "tool_use", "resul...
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...
Instead of re-assessing the whole context, which operation should I do next to resolve the contradiction about access rules by extracting the relevant symbols and definitions, given the stale assessment and many distractors? Decision: route Plan: {"active": true, "operation": "contradiction_resolution"} Agent State: {"...
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 the data transformation, which operation should I run next to extract the relevant evidence from the PDFs and compare it against the expected document structure, given the identifier variation? Decision: route Plan: {"active": true, "operation": "lookup_semantic"} Agent State: {"phase...
This operation handles a candidate result while preserving the current task state.. Capabilities: inspect evidence. Accepts: evidence candidates. Returns: evidence. Evidence role: evidence inspection. Prerequisites: evidence candidate selected. Constraints: candidate evidence required. Side effects: read. Arguments: cl...
With only one step left, what is the most critical missing context to retrieve for version compatibility? Decision: route Plan: {"active": false, "operation": "lookup_semantic"} Agent State: {"phase": "terminal_readiness", "question_length_band": "long", "state_name": "fresh_sufficient"} Source State: {"available_modal...
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 last attempt was ambiguous. How should I reconcile the conflicting evidence about field definitions and compatibility? Decision: route History: [{"action_family": "tool_use", "result": "weak", "step": 0}] Plan: {"active": false, "operation": "lookup_exact"} Agent State: {"phase": "synthesis", "question_length_band"...
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 sources should I enumerate to ensure full coverage of the task requirements, given the 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}, {"ac...
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...
Is the current evidence sufficient to determine the access rules and permissions, or do I need more records? Decision: route History: [{"action_family": "tool_use", "result": "weak", "step": 0}] Plan: {"active": false, "operation": "enumerate_records"} Agent State: {"phase": "inspection", "question_length_band": "long"...
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...
We have the exact identifier but sources show variations. Which candidate should we select next? Decision: route Plan: {"active": true, "operation": "compatibility"} Agent State: {"phase": "retrieval", "question_length_band": "short", "state_name": "retrieval"} Source State: {"available_modalities": ["code", "metadata"...
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...
We have snippets only and near-duplicates. What should we do to gather the missing information? Decision: route Plan: {"active": true, "operation": "lookup_exact"} Agent State: {"phase": "retrieval", "question_length_band": "short", "state_name": "retrieval"} Source State: {"available_modalities": ["text", "metadata"],...
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...
We need to verify absence of a passage. What resources are available to confirm this? Decision: route History: [{"action_family": "tool_use", "result": "weak", "step": 0}, {"action_family": "tool_use", "result": "weak", "step": 1}] Plan: {"active": true, "operation": "absence_verification"} Agent State: {"phase": "plan...
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)
We have CSV sources with version noise and need to compare. What content should we use next? 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": "source_di...
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 stale assessment and partial progress, enumerate the exact resource limit token from the inspected PDF, ensuring no local state is written and only read operations are used. Decision: route History: [{"action_family": "tool_use", "result": "weak", "step": 0}, {"action_family": "tool_use", "result": "weak", "s...
Apply this capability when the next decision depends on an exact name, code, or token.. Capabilities: exact pattern search. Accepts: text, code. Returns: evidence candidates. Evidence role: candidate discovery. Prerequisites: query available. Constraints: textual source required. Side effects: read. Arguments: case sen...
We've inspected multiple sources but haven't checked the governance state. What is the next workflow step's metadata filter, considering the complete requirements and the mixed modalities? Decision: route History: [{"action_family": "tool_use", "result": "weak", "step": 0}, {"action_family": "tool_use", "result": "weak...
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...
With full context and one step left, should we extract the schema from the Excel file to resolve the contradiction, rather than just listing candidate evidence? Decision: route History: [{"action_family": "tool_use", "result": "weak", "step": 0}, {"action_family": "tool_use", "result": "weak", "step": 1}, {"action_fami...
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 recovery, which matching records should we retrieve from the mixed sources, given the near-duplicate obstacle and stale assessment, without modifying local state? Decision: route History: [{"action_family": "tool_use", "result": "weak", "step": 0}, {"action_family": "tool_use", "result": "weak", "step": 1...
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...
I have one step left and need to finalize the telemetry/trace requirements. Which next operation should I prioritize to identify the sections and structural landmarks in the PDF source? Decision: route History: [{"action_family": "tool_use", "result": "weak", "step": 0}, {"action_family": "tool_use", "result": "weak", ...
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 an incomplete comparison attempt with version noise, what operation should I perform next to recover and find the relevant pages or ranges for the data quality validation? Decision: route History: [{"action_family": "tool_use", "result": "weak", "step": 0}, {"action_family": "tool_use", "result": "weak", "step": ...
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 the next workflow step, what operation should I use to enumerate available sources and select the right resource from the PDF catalog? Decision: route Plan: {"active": false, "operation": "enumerate_sources"} Agent State: {"phase": "inspection", "question_length_band": "long", "state_name": "partial_evidence"} Sour...
This candidate supports controlled inspection of the selected resource.. Capabilities: read content, inspect full source. Accepts: text, code. Returns: content. Evidence role: evidence inspection. Prerequisites: source selected. Constraints: local source required. Side effects: read. Arguments: offset (integer required...
What is the next action to retrieve the symbols and definitions needed for the data transformation from the code source? Decision: route Plan: {"active": true, "operation": "latest_value_selection"} Agent State: {"phase": "retrieval", "question_length_band": "long", "state_name": "retrieval"} Source State: {"available_...
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 inspection state and multiple passages, what should I do next to resolve the contradiction about version compatibility? Decision: route History: [{"action_family": "tool_use", "result": "weak", "step": 0}] Plan: {"active": false, "operation": "contradiction_resolution"} Agent State: {"phase": "inspectio...
Use this candidate when the task requires a candidate result.. Capabilities: inspect evidence. Accepts: evidence candidates. Returns: evidence. Evidence role: evidence inspection. Prerequisites: evidence candidate selected. Constraints: candidate evidence required. Side effects: read. Arguments: claim (string optional)...
I need to find the missing surrounding context for the resource limits and lifecycle. What operation should I perform next? Decision: route History: [{"action_family": "tool_use", "result": "weak", "step": 0}] Plan: {"active": false, "operation": "lookup_exact"} Agent State: {"phase": "inspection", "question_length_ban...
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...
Given the contradictory evidence from multiple sources, what should I do to check if the access rules agree or conflict? 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 agreement or conflict between results under current constraints.. Capabilities: compare evidence, detect contradictions. Accepts: evidence. Returns: evidence comparison. Evidence role: evidence synthesis. Prerequisites: evidence inspected. Constraints: multiple evidence requ...
Considering the never-assessed state and disputed requirements, what operation should I run to validate the data quality and cover all constraints? Decision: route Plan: {"active": false, "operation": "latest_value_selection"} Agent State: {"phase": "inspection", "question_length_band": "long", "state_name": "partial_e...
The operation produces a reliable result for task requirements and coverage under current constraints.. Capabilities: update requirements. Accepts: evidence, agent state. Returns: governance state. Evidence role: governance update. Prerequisites: evidence inspected. Constraints: tracked requirements required. Side effe...
Given the stale assessment and partial context, should we compare the available evidence without side effects before deciding if we can proceed? 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 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 checked multiple sources; now we need to join the CSV data. What's the next step after the schema is known? Decision: route History: [{"action_family": "tool_use", "result": "weak", "step": 0}, {"action_family": "tool_use", "result": "weak", "step": 1}, {"action_family": "tool_use", "result": "weak", "step": 2}, ...
This candidate supports controlled inspection of 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...
Instead of generating a plan, should we first retrieve the specific technical instruction from the complementary sources? Decision: route History: [{"action_family": "tool_use", "result": "weak", "step": 0}] Plan: {"active": true, "operation": "compare"} Agent State: {"phase": "planning", "question_length_band": "long"...
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...
How can we verify the event delivery and retry behavior by enumerating records from the Excel file, given the context is split? Decision: route History: [{"action_family": "tool_use", "result": "weak", "step": 0}, {"action_family": "tool_use", "result": "weak", "step": 1}] Plan: {"active": true, "operation": "enumerate...
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)
With only 4 steps left, which operation should I prioritize to retrieve the relevant content, given the search results are stale and version noise is an issue? Decision: route History: [{"action_family": "tool_use", "result": "weak", "step": 0}, {"action_family": "tool_use", "result": "weak", "step": 1}] Plan: {"active...
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...
After an ambiguous attempt, how should I recover to verify the absence of an exact code or token, with schema-bound queries and an unresolved requirement? Decision: route History: [{"action_family": "tool_use", "result": "weak", "step": 0}, {"action_family": "tool_use", "result": "weak", "step": 1}] Plan: {"active": fa...
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 consult to plan the required data transformation, given the schema is ambiguous and the inventory is only partially known? Decision: route History: [{"action_family": "tool_use", "result": "weak", "step": 0}, {"action_family": "tool_use", "result": "weak", "step": 1}, {"acti...
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 is the next action to compare fields, types, and structures across the inspected sources for event delivery and retry behavior? Decision: route History: [{"action_family": "tool_use", "result": "weak", "step": 0}] Plan: {"active": false, "operation": "compare"} Agent State: {"phase": "inspection", "question_length...
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...