anchor stringlengths 723 2.15k | positive stringlengths 153 8.2k |
|---|---|
Given the versioning context, what should I do next to check field types and structure?
Decision: route
Plan: {"active": false, "operation": "lookup_semantic"}
Agent State: {"phase": "governance", "question_length_band": "short", "state_name": "insufficient"}
Source State: {"available_modalities": ["text", "pdf", "csv"... | 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... |
We've checked snippets from two sources but they conflict. What's the next step to match records consistently?
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 Sta... | Use this candidate when the task requires 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. Arguments: limit ... |
I'm near the end but need to inspect sections and landmarks. Should I extract document structure or do something else?
Decision: route
History: [{"action_family": "tool_use", "result": "weak", "step": 0}]
Plan: {"active": false, "operation": "contradiction_resolution"}
Agent State: {"phase": "terminal_readiness", "ques... | 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 should I verify the event delivery and retry behavior? What operation would give me the relevant pages?
Decision: route
History: [{"action_family": "tool_use", "result": "weak", "step": 0}]
Plan: {"active": false, "operation": "lookup_exact"}
Agent State: {"phase": "inspection", "question_length_band": "long", "sta... | 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 (... |
Given limited steps, prioritize checking if the selected resource supports the required version.
Decision: route
History: [{"action_family": "tool_use", "result": "weak", "step": 0}, {"action_family": "tool_use", "result": "weak", "step": 1}]
Plan: {"active": true, "operation": "compatibility"}
Agent State: {"phase": "... | 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... |
We need to recover from the incomplete attempt: locate the exact definitions for telemetry and trace requirements.
Decision: route
Plan: {"active": false, "operation": "lookup_exact"}
Agent State: {"phase": "inspection", "question_length_band": "long", "state_name": "partial_evidence"}
Source State: {"available_modalit... | 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... |
List the sources that can confirm consistency for the candidate result.
Decision: route
Plan: {"active": false, "operation": "enumerate_sources"}
Agent State: {"phase": "terminal_readiness", "question_length_band": "short", "state_name": "fresh_sufficient"}
Source State: {"available_modalities": ["code", "metadata"], "... | 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... |
Next, verify the absence of the expected validation context in the available data.
Decision: route
History: [{"action_family": "tool_use", "result": "weak", "step": 0}]
Plan: {"active": true, "operation": "absence_verification"}
Agent State: {"phase": "retrieval", "question_length_band": "short", "state_name": "retriev... | 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... |
Check whether the results from the CSV sources agree or conflict, and then decide the next step.
Decision: route
History: [{"action_family": "tool_use", "result": "weak", "step": 0}, {"action_family": "tool_use", "result": "weak", "step": 1}]
Plan: {"active": true, "operation": "latest_value_selection"}
Agent State: {"... | 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... |
What should I do next to ensure the task requirements are covered?
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",... | 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... |
Is the available information enough to proceed to the next workflow step?
Decision: route
History: [{"action_family": "tool_use", "result": "weak", "step": 0}, {"action_family": "tool_use", "result": "weak", "step": 1}, {"action_family": "tool_use", "result": "weak", "step": 2}, {"action_family": "tool_use", "result": ... | 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... |
Given the near-duplicate results, which one should I select as the final version?
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": "inspection", "questi... | 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... |
We need to verify version compatibility but the relevant details are split across sources. What should we inspect next without altering any state?
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 best next information-gathering step.. Capabilities: plan retrieval. Accepts: agent state, text. Returns: plan. Evidence role: none. Prerequisites: objective available. Constraints: none. Side effects: local state write. Arguments: objective (string optional), priori... |
We've exhausted the current evidence and have limited steps left. What resources remain that we haven't tapped for telemetry and trace requirements?
Decision: route
History: [{"action_family": "tool_use", "result": "weak", "step": 0}, {"action_family": "tool_use", "result": "weak", "step": 1}, {"action_family": "tool_u... | 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) |
Instead of re-checking the stale assessment, what specific content should we extract now to determine the required data transformation?
Decision: route
History: [{"action_family": "tool_use", "result": "weak", "step": 0}, {"action_family": "tool_use", "result": "weak", "step": 1}]
Plan: {"active": true, "operation": "c... | Use this candidate when the task requires the relevant content.. Capabilities: search content. Accepts: text, pdf. Returns: evidence candidates. Evidence role: candidate discovery. Prerequisites: query available. Constraints: indexed sources required. Side effects: read. Arguments: limit (integer optional), query (stri... |
How can we verify the exact field definition we need, given complementary sources and a long document? What should we inspect next?
Decision: route
Plan: {"active": true, "operation": "latest_value_selection"}
Agent State: {"phase": "retrieval", "question_length_band": "long", "state_name": "retrieval"}
Source State: {... | 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... |
Given one step left, prioritize finding the resource metadata and filters for access rules; which operation should I run first?
Decision: route
History: [{"action_family": "tool_use", "result": "weak", "step": 0}]
Plan: {"active": false, "operation": "latest_value_selection"}
Agent State: {"phase": "inspection", "quest... | 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... |
The previous attempt was incomplete; I need to recover by examining fields, types, and structure for the next workflow step. What operation should I perform?
Decision: route
Plan: {"active": true, "operation": "compatibility"}
Agent State: {"phase": "planning", "question_length_band": "long", "state_name": "initial"}
S... | 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... |
For consistency checks across sources, I need to enumerate matching records. Which operation should I use to find them?
Decision: route
History: [{"action_family": "tool_use", "result": "weak", "step": 0}, {"action_family": "tool_use", "result": "weak", "step": 1}]
Plan: {"active": false, "operation": "enumerate_record... | 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... |
I need to validate data quality by locating sections and structural landmarks in a PDF. What operation should I perform next?
Decision: route
Plan: {"active": false, "operation": "enumerate_records"}
Agent State: {"phase": "governance", "question_length_band": "long", "state_name": "insufficient"}
Source State: {"avail... | 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 ... |
Given the access control context, identify the relevant pages or ranges that specify the access rules and permissions.
Decision: route
History: [{"action_family": "tool_use", "result": "weak", "step": 0}, {"action_family": "tool_use", "result": "weak", "step": 1}]
Plan: {"active": false, "operation": "compatibility"}
A... | 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... |
Determine the selected resource that satisfies the validation and quality constraints, considering the latest 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_select... | Invoke the candidate to determine the selected resource from the available resources.. 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 (in... |
Find the symbols and definitions that are consistent across the complementary sources to enumerate the relevant records.
Decision: route
Plan: {"active": false, "operation": "enumerate_records"}
Agent State: {"phase": "synthesis", "question_length_band": "long", "state_name": "contradiction"}
Source State: {"available_... | 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... |
Given the need for contradiction resolution and the constraint of no side effects, identify the candidate result that matches the required data transformation.
Decision: route
History: [{"action_family": "tool_use", "result": "weak", "step": 0}]
Plan: {"active": false, "operation": "contradiction_resolution"}
Agent Sta... | 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... |
Given the stale assessment and partial context, what next step is safe to perform without side effects, using only read operations, to find the missing surrounding context for the relevant technical instruction?
Decision: route
History: [{"action_family": "tool_use", "result": "weak", "step": 0}, {"action_family": "too... | 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... |
After inspecting multiple sources and finding complementary evidence, what operation should we perform next to resolve the disagreement between telemetry and trace results, given the exact identifier match?
Decision: route
History: [{"action_family": "tool_use", "result": "weak", "step": 0}, {"action_family": "tool_use... | 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 full context and all requirements are met, but we need to ensure consistency across sources. What should we do next that writes local state, rather than just reading, to verify coverage?
Decision: route
Plan: {"active": true, "operation": "contradiction_resolution"}
Agent State: {"phase": "retrieval", "question... | This operation handles task requirements and coverage while preserving the current task state.. Capabilities: update requirements, track coverage. Accepts: evidence, agent state. Returns: governance state. Evidence role: governance update. Prerequisites: evidence inspected. Constraints: tracked requirements required. S... |
With only one step remaining and a complete requirement set, what evidence-oriented operation should we perform to verify that the available information is sufficient, using metadata filtering?
Decision: route
History: [{"action_family": "tool_use", "result": "weak", "step": 0}, {"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... |
With only two steps left and all requirements already met, which single source should I prioritize next to keep consistency checks on track?
Decision: route
Plan: {"active": false, "operation": "enumerate_sources"}
Agent State: {"phase": "governance", "question_length_band": "long", "state_name": "insufficient"}
Source... | 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... |
After four searches with no resolution, what should I query next to settle the disputed access rule, given only one step remains?
Decision: route
History: [{"action_family": "tool_use", "result": "weak", "step": 0}, {"action_family": "tool_use", "result": "weak", "step": 1}, {"action_family": "tool_use", "result": "wea... | 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... |
Which available data source should I inspect to clarify the disputed field definitions and compatibility?
Decision: route
Plan: {"active": false, "operation": "compatibility"}
Agent State: {"phase": "source_discovery", "question_length_band": "long", "state_name": "source_discovery"}
Source State: {"available_modalitie... | 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) |
Given the split context, what content should I examine next to handle the failure recovery?
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": "... | 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... |
Find the exact code for the required data transformation in the PDF.
Decision: route
History: [{"action_family": "tool_use", "result": "weak", "step": 0}, {"action_family": "tool_use", "result": "weak", "step": 1}]
Plan: {"active": false, "operation": "absence_verification"}
Agent State: {"phase": "governance", "questi... | This operation handles an exact name, code, or token while preserving the current task state.. 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:... |
Which resource metadata and filters match the relevant technical instruction?
Decision: route
Plan: {"active": true, "operation": "compare"}
Agent State: {"phase": "retrieval", "question_length_band": "short", "state_name": "retrieval"}
Source State: {"available_modalities": ["csv", "metadata"], "evidence_topology_obse... | 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... |
What fields, types, and structure are needed for the data transformation?
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": "terminal_readiness", "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:... |
Given the complete requirements and known SQLite source, which matching records support event delivery and retry behavior?
Decision: route
History: [{"action_family": "tool_use", "result": "weak", "step": 0}, {"action_family": "tool_use", "result": "weak", "step": 1}]
Plan: {"active": false, "operation": "compatibility... | 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... |
Before finalizing, I need to locate the section headers in the PDF that outline the technical steps. What should I do next, ensuring no state changes?
Decision: route
History: [{"action_family": "tool_use", "result": "weak", "step": 0}, {"action_family": "tool_use", "result": "weak", "step": 1}]
Plan: {"active": false,... | 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 (... |
We've inspected multiple sources but haven't found the exact page range for the next workflow step. Given the version noise, what should we check next?
Decision: route
Plan: {"active": false, "operation": "absence_verification"}
Agent State: {"phase": "governance", "question_length_band": "long", "state_name": "insuffi... | Use this candidate when the task requires the relevant pages or ranges.. 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. Arguments: page range (ar... |
I have the exact identifier but need to confirm version compatibility. Should I extract the resource's metadata or search for alternative sources?
Decision: route
History: [{"action_family": "tool_use", "result": "weak", "step": 0}, {"action_family": "tool_use", "result": "weak", "step": 1}, {"action_family": "tool_use... | 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... |
To verify the resource limits, I need to enumerate the relevant symbols and definitions from the mixed sources. What should I do next to gather that evidence?
Decision: route
Plan: {"active": false, "operation": "enumerate_records"}
Agent State: {"phase": "governance", "question_length_band": "long", "state_name": "ins... | This operation handles symbols and definitions while preserving the current task state.. Capabilities: inspect code structure. Accepts: code. Returns: content, code structure. Evidence role: evidence inspection. Prerequisites: source selected. Constraints: code source required. Side effects: read. Arguments: depth (int... |
Given one step left, which candidate result should I prioritize to address the telemetry and trace requirements?
Decision: route
History: [{"action_family": "tool_use", "result": "weak", "step": 0}]
Plan: {"active": false, "operation": "compatibility"}
Agent State: {"phase": "synthesis", "question_length_band": "long",... | 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... |
The previous attempt was incomplete. What should I do next to get the missing context for the data transformation?
Decision: route
History: [{"action_family": "tool_use", "result": "weak", "step": 0}]
Plan: {"active": true, "operation": "compatibility"}
Agent State: {"phase": "planning", "question_length_band": "long",... | 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... |
For version compatibility, how do the current results compare? Are they in agreement or conflict?
Decision: route
History: [{"action_family": "tool_use", "result": "weak", "step": 0}]
Plan: {"active": false, "operation": "compare"}
Agent State: {"phase": "terminal_readiness", "question_length_band": "short", "state_nam... | 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... |
What next operation should ensure task requirements are covered across the complementary sources?
Decision: route
Plan: {"active": false, "operation": "lookup_exact"}
Agent State: {"phase": "terminal_readiness", "question_length_band": "short", "state_name": "fresh_sufficient"}
Source State: {"available_modalities": ["... | 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 and context, can we determine if the available information is sufficient to resolve the contradiction?
Decision: route
History: [{"action_family": "tool_use", "result": "weak", "step": 0}, {"action_family": "tool_use", "result": "weak", "step": 1}, {"action_family": "tool_use", "result": "wea... | 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... |
Based on the two inspected sources, which value should be selected as the latest?
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": "part... | 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... |
To proceed with event handling, what is the best next step to gather missing information?
Decision: route
History: [{"action_family": "tool_use", "result": "weak", "step": 0}, {"action_family": "tool_use", "result": "weak", "step": 1}, {"action_family": "tool_use", "result": "weak", "step": 2}, {"action_family": "tool_... | 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... |
Considering the disputed requirements and the available sources, what resources can be used to compare and recover?
Decision: route
Plan: {"active": true, "operation": "compare"}
Agent State: {"phase": "planning", "question_length_band": "long", "state_name": "initial"}
Source State: {"available_modalities": ["text", "... | 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) |
Given stale schema ambiguity, enumerate version compatibility records read-only, using code evidence.
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: {... | This candidate supports controlled inspection of the relevant content.. Capabilities: search content, retrieve passages. Accepts: text, pdf. Returns: evidence candidates. Evidence role: candidate discovery. Prerequisites: query available. Constraints: indexed sources required. Side effects: read. Arguments: limit (inte... |
We've checked some sources but still need an exact lookup for field definitions; what's next without writing state?
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 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 ... |
Don't just fetch metadata; instead, resolve the contradiction by extracting resource limits from code, read-only.
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}, ... | 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) |
How can I verify event delivery and retry behavior by enumerating records from mixed sources, without 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": "enumerate_records"}
... | 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:... |
With only two steps left and one unresolved requirement, should I prioritize verifying the absence of matching records in the Excel source, or resolve the schema ambiguity first?
Decision: route
History: [{"action_family": "tool_use", "result": "weak", "step": 0}, {"action_family": "tool_use", "result": "weak", "step":... | 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... |
After the ambiguous attempt, how should I recover to verify absence of the acronym in the PDF sections, given the schema-bound query?
Decision: route
History: [{"action_family": "tool_use", "result": "weak", "step": 0}, {"action_family": "tool_use", "result": "weak", "step": 1}]
Plan: {"active": true, "operation": "abs... | 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... |
Which catalog or inventory should I consult to locate the relevant pages or ranges in the PDF for the technical instruction, given the unknown source inventory?
Decision: route
History: [{"action_family": "tool_use", "result": "weak", "step": 0}]
Plan: {"active": true, "operation": "join"}
Agent State: {"phase": "plann... | 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... |
What is the next action to select the latest resource value from the CSV, given the disputed requirement progress?
Decision: route
Plan: {"active": false, "operation": "latest_value_selection"}
Agent State: {"phase": "synthesis", "question_length_band": "long", "state_name": "contradiction"}
Source State: {"available_m... | 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... |
Which candidate source's schema matches the field definitions?
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": "source_discovery", "question_leng... | 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... |
Which candidate result corresponds to the latest version?
Decision: route
History: [{"action_family": "tool_use", "result": "weak", "step": 0}, {"action_family": "tool_use", "result": "weak", "step": 1}]
Plan: {"active": true, "operation": "latest_value_selection"}
Agent State: {"phase": "planning", "question_length_ba... | 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... |
What is the surrounding context needed to resolve 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}, {"action_family": "tool_use", "result": "w... | 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... |
Do the evidence candidates agree on the absence of the required entity?
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": "w... | The operation produces a reliable result for agreement or conflict between results under current constraints.. Capabilities: compare evidence. Accepts: evidence. Returns: evidence comparison. Evidence role: evidence synthesis. Prerequisites: evidence inspected. Constraints: multiple evidence required. Side effects: non... |
Given the governance phase and partial requirements, what safe next step should I take to verify absence of a schema-bound item across the CSV evidence, without modifying state?
Decision: route
Plan: {"active": false, "operation": "absence_verification"}
Agent State: {"phase": "governance", "question_length_band": "lon... | 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... |
We've checked four evidence items and have two unresolved requirements. What remains to be done to determine if the available SQLite sources are sufficient for terminal readiness?
Decision: route
History: [{"action_family": "tool_use", "result": "weak", "step": 0}, {"action_family": "tool_use", "result": "weak", "step"... | This candidate supports controlled inspection of whether available information is sufficient.. Capabilities: assess evidence. Accepts: evidence, governance state. Returns: assessment. Evidence role: governance assessment. Prerequisites: requirements updated. Constraints: canonical evidence set required. Side effects: l... |
Given the contradiction between sources, should I now compare the conflicting evidence candidates to resolve the discrepancy, or instead re-run the search that produced near-duplicates?
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 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... |
After inspecting multiple passages and having two observations, what evidence-gathering step should I take to verify the absence of a specific identifier across the text sources, given the split context?
Decision: route
History: [{"action_family": "tool_use", "result": "weak", "step": 0}, {"action_family": "tool_use", ... | 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... |
Given one remaining step, which available resource should I prioritize to resolve the unresolved requirement?
Decision: route
History: [{"action_family": "tool_use", "result": "weak", "step": 0}]
Plan: {"active": false, "operation": "compare"}
Agent State: {"phase": "source_discovery", "question_length_band": "long", "... | The operation produces a reliable result for the available resources under current constraints.. 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... |
The last attempt was incomplete; what should I inspect next to resolve the contradiction and move forward?
Decision: route
Plan: {"active": false, "operation": "contradiction_resolution"}
Agent State: {"phase": "inspection", "question_length_band": "long", "state_name": "partial_evidence"}
Source State: {"available_mod... | 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... |
What is the exact identifier or token I should look up in the available resources to continue planning?
Decision: route
History: [{"action_family": "tool_use", "result": "weak", "step": 0}, {"action_family": "tool_use", "result": "weak", "step": 1}]
Plan: {"active": true, "operation": "enumerate_records"}
Agent State: ... | 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... |
What is the next action to find the relevant resource metadata and filters?
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"... | 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... |
Given the stale governance state, what structure of fields and types should I expect from the telemetry sources to satisfy the trace requirements?
Decision: route
History: [{"action_family": "tool_use", "result": "weak", "step": 0}, {"action_family": "tool_use", "result": "weak", "step": 1}]
Plan: {"active": false, "op... | This operation handles fields, types, and structure while preserving the current task state.. 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:... |
Which records in the SQLite source align with the technical instruction, given the identifier variations?
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... | 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... |
To complete the document analysis, which sections and structural landmarks should be examined to select the latest 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_s... | 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... |
Considering the partial source inventory and schema ambiguity, which pages or ranges in the PDF contain the access rules and permissions, and can you list them without modifying state?
Decision: route
History: [{"action_family": "tool_use", "result": "weak", "step": 0}]
Plan: {"active": false, "operation": "enumerate_s... | 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... |
Given the completed requirements and stale assessment, what read-only operation should select the latest value for the target resource, considering its field definitions and compatibility?
Decision: route
History: [{"action_family": "tool_use", "result": "weak", "step": 0}, {"action_family": "tool_use", "result": "weak... | 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... |
We've already inspected multiple sources and found complementary evidence, but the exact identifier is still unresolved. What stateful operation should we perform next to recover from the failure, focusing on symbols and definitions?
Decision: route
History: [{"action_family": "tool_use", "result": "weak", "step": 0}, ... | 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)... |
Instead of just listing all records, what precise read-only action should enumerate the specific candidate result's access rules, given the known CSV source and split context?
Decision: route
History: [{"action_family": "tool_use", "result": "weak", "step": 0}, {"action_family": "tool_use", "result": "weak", "step": 1}... | 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)... |
Since we only have snippets and need to verify absence, how should we inspect the surrounding context of the target to confirm the next workflow step is missing, using a read-only or state-writing operation?
Decision: route
History: [{"action_family": "tool_use", "result": "weak", "step": 0}, {"action_family": "tool_us... | 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 remaining steps, what should I do next to check agreement or conflict between the results from the different sources?
Decision: route
History: [{"action_family": "tool_use", "result": "weak", "step": 0}]
Plan: {"active": true, "operation": "join"}
Agent State: {"phase": "planning", "question_length_band": "lo... | 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... |
My previous attempt was incomplete; what operation should I perform to cover all task requirements and ensure telemetry/trace requirements are met?
Decision: route
History: [{"action_family": "tool_use", "result": "weak", "step": 0}]
Plan: {"active": true, "operation": "join"}
Agent State: {"phase": "planning", "questi... | 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 available information, what should I do next to determine if it's sufficient for failure recovery?
Decision: route
History: [{"action_family": "tool_use", "result": "weak", "step": 0}]
Plan: {"active": false, "operation": "enumerate_records"}
Agent State: {"phase": "governance", "question_length_band": "long"... | This candidate supports controlled inspection of whether available information is sufficient.. Capabilities: assess evidence, validate sufficiency. Accepts: evidence, governance state. Returns: assessment. Evidence role: governance assessment. Prerequisites: requirements updated. Constraints: canonical evidence set req... |
What is the next action I should take to proceed with the selected result or 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_semantic"}
Agent State: {"phase": "termin... | 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... |
Given the contradictory evidence and need to verify absence, what information-gathering step should I take next?
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"}
A... | 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... |
What resources are available to help with recovery from this failure?
Decision: route
History: [{"action_family": "tool_use", "result": "weak", "step": 0}]
Plan: {"active": true, "operation": "lookup_exact"}
Agent State: {"phase": "retrieval", "question_length_band": "short", "state_name": "retrieval"}
Source State: {"... | 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) |
To move forward with the workflow, what content should I examine next?
Decision: route
Plan: {"active": false, "operation": "compare"}
Agent State: {"phase": "terminal_readiness", "question_length_band": "short", "state_name": "fresh_sufficient"}
Source State: {"available_modalities": ["excel", "metadata"], "evidence_t... | 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... |
Given the stale assessment and exact identifier needed for transformation, what exact name or code should I retrieve now?
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"}
... | 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... |
Given the schema ambiguity, which next step should I take to identify the right source metadata and filters, ensuring no side effects and only reading state?
Decision: route
History: [{"action_family": "tool_use", "result": "weak", "step": 0}, {"action_family": "tool_use", "result": "weak", "step": 1}]
Plan: {"active":... | This candidate supports controlled inspection of 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 optional),... |
We've already inspected multiple sources and need to pick the latest value for the entity. What should we do next to resolve the version noise and determine the correct field types?
Decision: route
History: [{"action_family": "tool_use", "result": "weak", "step": 0}, {"action_family": "tool_use", "result": "weak", "ste... | This candidate supports controlled inspection of fields, types, and structure.. Capabilities: inspect structured schema. Accepts: csv, excel, sqlite. Returns: schema. Evidence role: structure discovery. Prerequisites: source selected. Constraints: structured source required. Side effects: read. Arguments: include types... |
We have snippets from complementary sources but need to join records by exact identifier. Should we proceed with a metadata-filtered search or instead inspect the full document structure?
Decision: route
History: [{"action_family": "tool_use", "result": "weak", "step": 0}, {"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... |
We've completed the requirements but need to verify the transformation. What next step should we take to confirm the output by checking the document's sections and landmarks?
Decision: route
Plan: {"active": false, "operation": "lookup_exact"}
Agent State: {"phase": "governance", "question_length_band": "long", "state_... | 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... |
With zero steps left, prioritize the pages or ranges that confirm the absence of access rules.
Decision: route
History: [{"action_family": "tool_use", "result": "weak", "step": 0}]
Plan: {"active": false, "operation": "absence_verification"}
Agent State: {"phase": "terminal_readiness", "question_length_band": "short", ... | 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 (... |
After the incomplete attempt, recover by focusing on the selected resource to determine the next workflow step.
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_n... | Apply this capability when the next decision depends on 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 r... |
For version compatibility, which symbols and definitions should be looked up in the catalog?
Decision: route
History: [{"action_family": "tool_use", "result": "weak", "step": 0}]
Plan: {"active": false, "operation": "compatibility"}
Agent State: {"phase": "terminal_readiness", "question_length_band": "short", "state_na... | 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 is the next action to inspect a candidate result for the relevant technical instruction?
Decision: route
Plan: {"active": false, "operation": "lookup_exact"}
Agent State: {"phase": "inspection", "question_length_band": "short", "state_name": "partial_evidence"}
Source State: {"available_modalities": ["code", "meta... | 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... |
I need to find the latest value for this entity, but the relevant document is long. 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": true, "operation": "latest_value_selection"}
Agent... | 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... |
We've inspected multiple sources but haven't found what we're looking for. How should we proceed to verify its absence?
Decision: route
Plan: {"active": true, "operation": "absence_verification"}
Agent State: {"phase": "retrieval", "question_length_band": "long", "state_name": "retrieval"}
Source State: {"available_mod... | 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... |
Our goal is to automate the next workflow step, but we need to resolve a contradiction in the evidence. What should we do?
Decision: route
History: [{"action_family": "tool_use", "result": "weak", "step": 0}, {"action_family": "tool_use", "result": "weak", "step": 1}]
Plan: {"active": true, "operation": "contradiction_... | The operation produces a reliable result for task requirements and coverage under current constraints.. Capabilities: update requirements, track coverage. Accepts: evidence, agent state. Returns: governance state. Evidence role: governance update. Prerequisites: evidence inspected. Constraints: tracked requirements req... |
We have partial context and need to decide if we have enough info to synthesize. What next?
Decision: route
History: [{"action_family": "tool_use", "result": "weak", "step": 0}, {"action_family": "tool_use", "result": "weak", "step": 1}, {"action_family": "tool_use", "result": "weak", "step": 2}, {"action_family": "too... | The operation produces a reliable result for whether available information is sufficient under current constraints.. Capabilities: assess evidence. Accepts: evidence, governance state. Returns: assessment. Evidence role: governance assessment. Prerequisites: requirements updated. Constraints: canonical evidence set req... |
Given the assessed evidence and governance state, what next operation should I perform to compare the multiple passages while respecting safety and side-effect constraints?
Decision: route
History: [{"action_family": "tool_use", "result": "weak", "step": 0}, {"action_family": "tool_use", "result": "weak", "step": 1}]
P... | Apply this capability when the next decision depends on the selected result or next action.. Capabilities: finalize selection. Accepts: assessment, governance state. Returns: terminal result. Evidence role: terminal decision. Prerequisites: requirements complete. Constraints: fresh sufficient assessment required. Side ... |
We've already checked the current field definitions and compatibility; what remains to be done to retrieve the latest value, given the stale assessment and exact identifier matching?
Decision: route
History: [{"action_family": "tool_use", "result": "weak", "step": 0}, {"action_family": "tool_use", "result": "weak", "st... | This candidate supports controlled inspection of the best next information-gathering step.. Capabilities: plan retrieval. Accepts: agent state, text. Returns: plan. Evidence role: none. Prerequisites: objective available. Constraints: none. Side effects: local state write. Arguments: objective (string required), priori... |
Instead of jumping to synthesis, what operation should I use to verify the absence of a workflow step, given the available resources and the stale assessment?
Decision: route
Plan: {"active": false, "operation": "absence_verification"}
Agent State: {"phase": "synthesis", "question_length_band": "long", "state_name": "c... | 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 can I verify the result by inspecting the relevant content, given the known source inventory and the need to check for absence of resource limits?
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 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... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.