anchor stringlengths 723 2.15k | positive stringlengths 153 8.2k |
|---|---|
We need to compare resource limits across the CSV files. Which rows contain matching records?
Decision: route
History: [{"action_family": "tool_use", "result": "weak", "step": 0}]
Plan: {"active": false, "operation": "compare"}
Agent State: {"phase": "source_discovery", "question_length_band": "short", "state_name": "s... | Use this candidate when the task requires matching records.. Capabilities: search structured records. Accepts: csv, excel, sqlite. Returns: evidence candidates. Evidence role: candidate discovery. Prerequisites: schema known. Constraints: structured source required. Side effects: read. Arguments: limit (integer require... |
Find the sections in the documents that describe field definitions and compatibility.
Decision: route
History: [{"action_family": "tool_use", "result": "weak", "step": 0}, {"action_family": "tool_use", "result": "weak", "step": 1}]
Plan: {"active": false, "operation": "lookup_semantic"}
Agent State: {"phase": "source_d... | Invoke the candidate to determine sections and structural landmarks from the available resources.. Capabilities: inspect document structure, discover sections. Accepts: pdf. Returns: document structure. Evidence role: structure discovery. Prerequisites: source selected. Constraints: pdf source required. Side effects: r... |
I need to verify that the failure recovery procedures are absent from the relevant pages.
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": "... | Invoke the candidate to determine the relevant pages or ranges from the available resources.. Capabilities: search document pages. Accepts: pdf. Returns: evidence candidates. Evidence role: candidate discovery. Prerequisites: source selected. Constraints: pdf source required. Side effects: read. Arguments: page range (... |
Given the contradictory evidence, which resource should we select for validation and quality checks?
Decision: route
History: [{"action_family": "tool_use", "result": "weak", "step": 0}]
Plan: {"active": false, "operation": "lookup_semantic"}
Agent State: {"phase": "synthesis", "question_length_band": "long", "state_na... | 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... |
We need to inspect event delivery and retry behavior. What read-only operation can enumerate records from mixed sources, filtering by metadata, without writing any local state?
Decision: route
Plan: {"active": false, "operation": "enumerate_records"}
Agent State: {"phase": "inspection", "question_length_band": "long", ... | 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... |
We have partially inspected evidence and compared two items, but one disputed requirement remains. Given the schema ambiguity in PDFs, what stateful next step can filter candidates by metadata to resolve the access rules?
Decision: route
History: [{"action_family": "tool_use", "result": "weak", "step": 0}]
Plan: {"acti... | 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... |
We have partial context but lack surrounding details. Should we enumerate records by exact identifier to retrieve missing context, rather than re-assessing stale governance state?
Decision: route
History: [{"action_family": "tool_use", "result": "weak", "step": 0}, {"action_family": "tool_use", "result": "weak", "step"... | This operation handles missing surrounding context while preserving the current task state.. Capabilities: expand context, resolve split context. Accepts: evidence candidates, evidence. Returns: evidence. Evidence role: context expansion. Prerequisites: evidence candidate selected. Constraints: incomplete context requi... |
We have inspected multiple sources and need to verify absence of something. How can we compare results from complementary sources to confirm agreement, given version noise and schema-bound queries?
Decision: route
Plan: {"active": false, "operation": "absence_verification"}
Agent State: {"phase": "terminal_readiness", ... | 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... |
With only four steps left, which candidate should I prioritize to close the remaining coverage gaps in the access rules?
Decision: route
History: [{"action_family": "tool_use", "result": "weak", "step": 0}, {"action_family": "tool_use", "result": "weak", "step": 1}, {"action_family": "tool_use", "result": "weak", "step... | Invoke the candidate to determine task requirements and coverage from the available resources.. Capabilities: update requirements. Accepts: evidence, agent state. Returns: governance state. Evidence role: governance update. Prerequisites: evidence inspected. Constraints: tracked requirements required. Side effects: loc... |
My last attempt was incomplete; what should I do next to determine if I have enough telemetry evidence to resolve the disputed requirements?
Decision: route
History: [{"action_family": "tool_use", "result": "weak", "step": 0}, {"action_family": "tool_use", "result": "weak", "step": 1}]
Plan: {"active": false, "operatio... | 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 known sources, which catalog entry should I select as the latest value for the access rule, and what's the next action?
Decision: route
History: [{"action_family": "tool_use", "result": "weak", "step": 0}, {"action_family": "tool_use", "result": "weak", "step": 1}, {"action_family": "tool_use", "result": "wea... | Apply this capability when the next decision depends on the selected result or next action.. Capabilities: finalize selection. Accepts: assessment, governance state. Returns: terminal result. Evidence role: terminal decision. Prerequisites: requirements complete. Constraints: fresh sufficient assessment required. Side ... |
What is the best next step to gather information for the required data transformation?
Decision: route
Plan: {"active": true, "operation": "compare"}
Agent State: {"phase": "planning", "question_length_band": "short", "state_name": "initial"}
Source State: {"available_modalities": ["text", "metadata"], "evidence_topolo... | This candidate supports controlled inspection of the best next information-gathering step.. Capabilities: plan retrieval. Accepts: agent state, text. Returns: plan. Evidence role: none. Prerequisites: objective available. Constraints: none. Side effects: local state write. Arguments: objective (string required), priori... |
What operation should I perform next to compare the available resources and their limits?
Decision: route
Plan: {"active": true, "operation": "compare"}
Agent State: {"phase": "planning", "question_length_band": "short", "state_name": "initial"}
Source State: {"available_modalities": ["code", "metadata"], "evidence_top... | 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) |
Can you determine the next step to extract the relevant access rules from 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": "latest_value_selection"}
Agent State: {"phase": "term... | 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... |
What should I do next to find the exact code or token for version compatibility?
Decision: route
History: [{"action_family": "tool_use", "result": "weak", "step": 0}, {"action_family": "tool_use", "result": "weak", "step": 1}]
Plan: {"active": false, "operation": "lookup_semantic"}
Agent State: {"phase": "synthesis", "... | Invoke the candidate to determine an exact name, code, or token from the available resources.. Capabilities: exact pattern search. Accepts: text, code. Returns: evidence candidates. Evidence role: candidate discovery. Prerequisites: query available. Constraints: textual source required. Side effects: read. Arguments: c... |
What operation should I run to enumerate sources with resource metadata and filters, given the unknown inventory?
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"}
Ag... | The operation produces a reliable result for resource metadata and filters under current constraints.. Capabilities: search metadata. Accepts: metadata. Returns: source list. Evidence role: source discovery. Prerequisites: none. Constraints: metadata catalog required. Side effects: read. Arguments: filters (object requ... |
We need the latest value from the Excel file, but only read it and note the field types and structure in the plan; do not write anything locally.
Decision: route
History: [{"action_family": "tool_use", "result": "weak", "step": 0}, {"action_family": "tool_use", "result": "weak", "step": 1}]
Plan: {"active": false, "ope... | 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 already checked the CSV and Excel; the near-duplicate record is still missing. What should we do next to find the matching record without writing anything?
Decision: route
History: [{"action_family": "tool_use", "result": "weak", "step": 0}, {"action_family": "tool_use", "result": "weak", "step": 1}]
Plan: {"acti... | 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 ... |
We need to resolve the contradiction by locating the relevant sections in the documents. Should we extract the document structure or just list the sources? Only read, no side effects.
Decision: route
History: [{"action_family": "tool_use", "result": "weak", "step": 0}, {"action_family": "tool_use", "result": "weak", "s... | Use this candidate when the task requires sections and structural landmarks.. Capabilities: inspect document structure. Accepts: pdf. Returns: document structure. Evidence role: structure discovery. Prerequisites: source selected. Constraints: pdf source required. Side effects: read. Arguments: landmark (string optiona... |
How can we verify the join result by checking the relevant pages and field definitions across the mixed sources, ensuring the schema is compatible and the evidence is recorded?
Decision: route
History: [{"action_family": "tool_use", "result": "weak", "step": 0}, {"action_family": "tool_use", "result": "weak", "step": 1... | 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 only 8 steps left and 4 unresolved requirements, prioritize the next operation on the selected resource to satisfy validation and quality constraints.
Decision: route
History: [{"action_family": "tool_use", "result": "weak", "step": 0}, {"action_family": "tool_use", "result": "weak", "step": 1}, {"action_family":... | 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... |
After an incomplete attempt, what should we do next to recover and find the needed symbols and definitions from the mixed sources?
Decision: route
History: [{"action_family": "tool_use", "result": "weak", "step": 0}, {"action_family": "tool_use", "result": "weak", "step": 1}]
Plan: {"active": false, "operation": "looku... | 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... |
Which candidate result should we examine next to resolve the failure, given the catalog of sources and our current context?
Decision: route
History: [{"action_family": "tool_use", "result": "weak", "step": 0}, {"action_family": "tool_use", "result": "weak", "step": 1}]
Plan: {"active": false, "operation": "compatibilit... | 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... |
With only one step left, what is the next action to gather missing context for version compatibility?
Decision: route
History: [{"action_family": "tool_use", "result": "weak", "step": 0}, {"action_family": "tool_use", "result": "weak", "step": 1}, {"action_family": "tool_use", "result": "weak", "step": 2}, {"action_fam... | 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... |
Compare the evidence from the inspected sources to see if they agree on the access rules.
Decision: route
History: [{"action_family": "tool_use", "result": "weak", "step": 0}, {"action_family": "tool_use", "result": "weak", "step": 1}, {"action_family": "tool_use", "result": "weak", "step": 2}, {"action_family": "tool_... | 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... |
Resolve the contradiction between the code and the task requirements to determine the correct instruction.
Decision: route
History: [{"action_family": "tool_use", "result": "weak", "step": 0}, {"action_family": "tool_use", "result": "weak", "step": 1}]
Plan: {"active": false, "operation": "contradiction_resolution"}
Ag... | 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... |
Determine if the gathered evidence is sufficient to proceed with the recovery plan.
Decision: route
History: [{"action_family": "tool_use", "result": "weak", "step": 0}]
Plan: {"active": false, "operation": "join"}
Agent State: {"phase": "inspection", "question_length_band": "short", "state_name": "partial_evidence"}
S... | 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... |
Retrieve the exact data transformation result from the database, considering the schema constraint.
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":... | 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 have conflicting evidence from multiple sources. What read-only operation should I run next to compare the candidates and resolve the near-duplicate issue?
Decision: route
History: [{"action_family": "tool_use", "result": "weak", "step": 0}, {"action_family": "tool_use", "result": "weak", "step": 1}, {"action_family... | 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),... |
I've only seen snippets so far and the identifier variation is blocking. What should I check next from the available resources to get the latest value?
Decision: route
History: [{"action_family": "tool_use", "result": "weak", "step": 0}]
Plan: {"active": false, "operation": "latest_value_selection"}
Agent State: {"phas... | This candidate supports controlled inspection of the available resources.. Capabilities: list sources. Accepts: metadata. Returns: source list. Evidence role: source discovery. Prerequisites: none. Constraints: none. Side effects: read. Arguments: filters (object optional), scope (string required) |
I need to enumerate all records from the schema-bound source, but I must avoid any state-changing operation. What is the precise next step instead of updating local state?
Decision: route
Plan: {"active": false, "operation": "enumerate_records"}
Agent State: {"phase": "terminal_readiness", "question_length_band": "long... | Use this candidate when the task requires the relevant content.. Capabilities: search content. Accepts: text, pdf. Returns: evidence candidates. Evidence role: candidate discovery. Prerequisites: query available. Constraints: indexed sources required. Side effects: read. Arguments: limit (integer optional), query (stri... |
How can I verify the exact transformation token by checking evidence across formats, given the stale assessment?
Decision: route
History: [{"action_family": "tool_use", "result": "weak", "step": 0}, {"action_family": "tool_use", "result": "weak", "step": 1}, {"action_family": "tool_use", "result": "weak", "step": 2}, {... | This operation handles 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... |
We're almost done but have one step left. Which operation should we run now to confirm the resource metadata and filters are correct, given the partial context?
Decision: route
History: [{"action_family": "tool_use", "result": "weak", "step": 0}, {"action_family": "tool_use", "result": "weak", "step": 1}, {"action_fami... | 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... |
Our last attempt was incomplete. What should we do next to recover and inspect the fields, types, and structure from the SQLite source?
Decision: route
History: [{"action_family": "tool_use", "result": "weak", "step": 0}, {"action_family": "tool_use", "result": "weak", "step": 1}]
Plan: {"active": false, "operation": "... | Apply this capability when the next decision depends on fields, types, and structure.. Capabilities: inspect structured schema, discover fields. Accepts: csv, excel, sqlite. Returns: schema. Evidence role: structure discovery. Prerequisites: source selected. Constraints: structured source required. Side effects: read. ... |
We need to find matching records for resource limits. What operation should we use to enumerate the catalog entries from the spreadsheet?
Decision: route
History: [{"action_family": "tool_use", "result": "weak", "step": 0}]
Plan: {"active": true, "operation": "enumerate_records"}
Agent State: {"phase": "planning", "que... | 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... |
What should we do next to locate the relevant sections and structural landmarks in the PDF 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_use", "result": "weak... | 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 ... |
Find the relevant pages or ranges for the next workflow step.
Decision: route
Plan: {"active": false, "operation": "join"}
Agent State: {"phase": "terminal_readiness", "question_length_band": "short", "state_name": "fresh_sufficient"}
Source State: {"available_modalities": ["text", "pdf", "csv", "excel", "sqlite", "cod... | 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... |
What is the selected resource for handling the failure?
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": "inspection", "question_length_band": "... | 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... |
I need to locate the symbols and definitions to satisfy telemetry and trace requirements.
Decision: route
Plan: {"active": false, "operation": "contradiction_resolution"}
Agent State: {"phase": "terminal_readiness", "question_length_band": "short", "state_name": "fresh_sufficient"}
Source State: {"available_modalities"... | 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 schema ambiguity, which candidate result should be used 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_family": "tool_use", "r... | 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... |
We need to compare the two partial results to find what context is missing, but avoid any operation that writes state or has 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"... | 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... |
We've already inspected multiple sources, but the results conflict. What next step can resolve the contradiction without modifying any state?
Decision: route
History: [{"action_family": "tool_use", "result": "weak", "step": 0}]
Plan: {"active": false, "operation": "contradiction_resolution"}
Agent State: {"phase": "syn... | This candidate supports controlled inspection of agreement or conflict between results.. Capabilities: compare evidence. Accepts: evidence. Returns: evidence comparison. Evidence role: evidence synthesis. Prerequisites: evidence inspected. Constraints: multiple evidence required. Side effects: none. Arguments: comparis... |
Given the exact identifier, should we enumerate all records from the complementary sources, or is there a better next step to ensure full coverage?
Decision: route
History: [{"action_family": "tool_use", "result": "weak", "step": 0}, {"action_family": "tool_use", "result": "weak", "step": 1}]
Plan: {"active": true, "op... | 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 have no prior search and need to verify the absence of an event. What step can confirm the evidence is sufficient, without causing side effects?
Decision: route
Plan: {"active": false, "operation": "absence_verification"}
Agent State: {"phase": "synthesis", "question_length_band": "long", "state_name": "contradictio... | 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... |
Given only one step left, which action should I prioritize to resolve the near-duplicate issue and complete the join?
Decision: route
History: [{"action_family": "tool_use", "result": "weak", "step": 0}, {"action_family": "tool_use", "result": "weak", "step": 1}]
Plan: {"active": false, "operation": "join"}
Agent State... | 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... |
The last attempt was incomplete and ambiguous. What should I do next to recover and gather the needed information?
Decision: route
History: [{"action_family": "tool_use", "result": "weak", "step": 0}, {"action_family": "tool_use", "result": "weak", "step": 1}]
Plan: {"active": true, "operation": "lookup_semantic"}
Agen... | The operation produces a reliable result for the best next information-gathering step under current constraints.. Capabilities: plan retrieval. Accepts: agent state, text. Returns: plan. Evidence role: none. Prerequisites: objective available. Constraints: none. Side effects: local state write. Arguments: objective (st... |
Before proceeding, what resources are available for the next workflow step, given the version noise and stale assessment?
Decision: route
Plan: {"active": true, "operation": "lookup_semantic"}
Agent State: {"phase": "planning", "question_length_band": "long", "state_name": "initial"}
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) |
What content should be used next to handle the disputed requirement and ensure proper event delivery?
Decision: route
Plan: {"active": false, "operation": "join"}
Agent State: {"phase": "terminal_readiness", "question_length_band": "long", "state_name": "fresh_sufficient"}
Source State: {"available_modalities": ["sqlit... | 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 trace ID for the failing telemetry event.
Decision: route
History: [{"action_family": "tool_use", "result": "weak", "step": 0}, {"action_family": "tool_use", "result": "weak", "step": 1}]
Plan: {"active": true, "operation": "lookup_semantic"}
Agent State: {"phase": "planning", "question_length_band": "sh... | 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... |
Show me the metadata filters that distinguish the two schema versions.
Decision: route
History: [{"action_family": "tool_use", "result": "weak", "step": 0}]
Plan: {"active": false, "operation": "compare"}
Agent State: {"phase": "synthesis", "question_length_band": "short", "state_name": "contradiction"}
Source State: {... | 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... |
List all CSV sources with their fields and types to check consistency.
Decision: route
Plan: {"active": false, "operation": "enumerate_sources"}
Agent State: {"phase": "source_discovery", "question_length_band": "short", "state_name": "source_discovery"}
Source State: {"available_modalities": ["csv", "metadata"], "evid... | 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:... |
Compare the matching event records in SQLite to see retry behavior differences.
Decision: route
History: [{"action_family": "tool_use", "result": "weak", "step": 0}]
Plan: {"active": false, "operation": "compare"}
Agent State: {"phase": "inspection", "question_length_band": "short", "state_name": "partial_evidence"}
So... | 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... |
Given the PDF has been inspected and the requirement is complete, identify the document's structural landmarks (sections) to verify absence, without altering local state.
Decision: route
History: [{"action_family": "tool_use", "result": "weak", "step": 0}, {"action_family": "tool_use", "result": "weak", "step": 1}]
Pla... | 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 checked the schema fields and compatibility, but the evidence is stale. With only 2 steps left, which pages or ranges should we retrieve from the mixed sources to enumerate records?
Decision: route
Plan: {"active": true, "operation": "enumerate_records"}
Agent State: {"phase": "retrieval", "question_length_band":... | 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... |
Although we've seen the full context, the assessment is stale. For telemetry and trace requirements, should we inspect the selected resource or instead enumerate sources?
Decision: route
Plan: {"active": false, "operation": "enumerate_sources"}
Agent State: {"phase": "inspection", "question_length_band": "long", "state... | 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... |
The requirement progress is disputed. How can we verify the result by examining symbols and definitions from the evidence candidates, ensuring no side effects?
Decision: route
Plan: {"active": false, "operation": "enumerate_sources"}
Agent State: {"phase": "terminal_readiness", "question_length_band": "long", "state_na... | 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 resolve access rules?
Decision: route
Plan: {"active": true, "operation": "enumerate_records"}
Agent State: {"phase": "planning", "question_length_band": "short", "state_name": "initial"}
Source State: {"available_modalities": ["code", "metadata"], "evi... | 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... |
I have one step left and missing context; what source should I enumerate next to recover the workflow step?
Decision: route
History: [{"action_family": "tool_use", "result": "weak", "step": 0}, {"action_family": "tool_use", "result": "weak", "step": 1}]
Plan: {"active": true, "operation": "enumerate_sources"}
Agent Sta... | 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... |
No steps left; which source candidates show agreement or conflict for failure recovery?
Decision: route
History: [{"action_family": "tool_use", "result": "weak", "step": 0}, {"action_family": "tool_use", "result": "weak", "step": 1}]
Plan: {"active": true, "operation": "enumerate_sources"}
Agent State: {"phase": "plann... | 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 action should I take to check task requirements and coverage?
Decision: route
Plan: {"active": false, "operation": "enumerate_records"}
Agent State: {"phase": "governance", "question_length_band": "short", "state_name": "insufficient"}
Source State: {"available_modalities": ["sqlite", "metadata"], "evidence_t... | 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... |
Are the current records sufficient to determine version compatibility?
Decision: route
History: [{"action_family": "tool_use", "result": "weak", "step": 0}, {"action_family": "tool_use", "result": "weak", "step": 1}]
Plan: {"active": false, "operation": "enumerate_records"}
Agent State: {"phase": "terminal_readiness", ... | 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... |
What should we do next for the 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": "weak", "step": 3}]
Plan: {"... | 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... |
What is the best next step to validate the data quality constraints?
Decision: route
History: [{"action_family": "tool_use", "result": "weak", "step": 0}, {"action_family": "tool_use", "result": "weak", "step": 1}, {"action_family": "tool_use", "result": "weak", "step": 2}, {"action_family": "tool_use", "result": "weak... | 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... |
I've inspected multiple sources but only found one passage. Given the identifier variation, what resources are available to enumerate sources for telemetry and trace requirements?
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 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 the contradictory evidence and stale assessment, what next operation should I perform to select the latest value for the entity-bound query, considering only read or local state write side effects, without altering external systems?
Decision: route
History: [{"action_family": "tool_use", "result": "weak", "step":... | 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 already checked two sources and found nothing due to the acronym obstacle. With the source inventory known and only read side effects allowed, what should we do next to find the exact access rule token in the Excel file?
Decision: route
History: [{"action_family": "tool_use", "result": "weak", "step": 0}, {"actio... | 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 ... |
We have full context from four complementary sources, but the assessment is stale and we're down to one step. Should we verify absence by searching for the resource metadata in the SQLite source, or would it be better to re-run the assessment? What is the precise next move?
Decision: route
History: [{"action_family": "... | 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 have snippets from multiple passages but no full evidence. To enumerate records for telemetry, what verification step should I take next to confirm the schema fields and types, given the schema ambiguity and that only read or local write side effects are permitted?
Decision: route
History: [{"action_family": "tool_u... | 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:... |
I have one step left; which candidate is most likely to confirm the absence, given the broad query and stale assessment?
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... | 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... |
The last attempt was incomplete. How should I recover to locate the right sections, given the schema ambiguity and no prior inspection?
Decision: route
History: [{"action_family": "tool_use", "result": "weak", "step": 0}, {"action_family": "tool_use", "result": "weak", "step": 1}, {"action_family": "tool_use", "result"... | Apply this capability when the next decision depends on sections and structural landmarks.. Capabilities: inspect document structure, discover sections. Accepts: pdf. Returns: document structure. Evidence role: structure discovery. Prerequisites: source selected. Constraints: pdf source required. Side effects: read. Ar... |
Which resource should I consult to get the relevant pages or ranges for the consistency check, without altering state?
Decision: route
Plan: {"active": false, "operation": "compatibility"}
Agent State: {"phase": "source_discovery", "question_length_band": "long", "state_name": "source_discovery"}
Source State: {"availa... | 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 should I do next to resolve the contradiction, using the selected resource and considering the side effects?
Decision: route
History: [{"action_family": "tool_use", "result": "weak", "step": 0}]
Plan: {"active": true, "operation": "contradiction_resolution"}
Agent State: {"phase": "retrieval", "question_length_ban... | 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... |
Inspect the latest value for the entity's symbol definitions.
Decision: route
Plan: {"active": false, "operation": "latest_value_selection"}
Agent State: {"phase": "inspection", "question_length_band": "short", "state_name": "partial_evidence"}
Source State: {"available_modalities": ["text", "pdf", "csv", "excel", "sql... | 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... |
Check if there is any evidence for the event with the exact identifier.
Decision: route
History: [{"action_family": "tool_use", "result": "weak", "step": 0}]
Plan: {"active": true, "operation": "absence_verification"}
Agent State: {"phase": "retrieval", "question_length_band": "short", "state_name": "retrieval"}
Source... | 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... |
I need to understand the context around the candidate result to resolve the near-duplicate.
Decision: route
Plan: {"active": true, "operation": "join"}
Agent State: {"phase": "retrieval", "question_length_band": "short", "state_name": "retrieval"}
Source State: {"available_modalities": ["text", "pdf", "csv", "excel", "... | 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... |
Given the contradictory telemetry results, what is the agreement or conflict between them?
Decision: route
Plan: {"active": false, "operation": "contradiction_resolution"}
Agent State: {"phase": "governance", "question_length_band": "short", "state_name": "insufficient"}
Source State: {"available_modalities": ["pdf", "... | 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 planning phase and partial source inventory, which read-only operation on the CSV evidence would best clarify disputed requirements without modifying local state?
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 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 already checked some evidence but context is split; with zero steps remaining, what join operation on the PDF-derived data would tell us if we have enough to finalize event delivery and retry behavior?
Decision: route
History: [{"action_family": "tool_use", "result": "weak", "step": 0}, {"action_family": "tool_us... | 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 that we've inspected multiple sources and the source modality is SQLite, what exact-identifier join should we run next to validate quality constraints, rather than re-inspecting already seen evidence?
Decision: route
History: [{"action_family": "tool_use", "result": "weak", "step": 0}]
Plan: {"active": false, "op... | 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... |
Given stale assessment and complementary sources, how should we compare the PDF-derived evidence with the CSV data to verify resource limits and lifecycle, ensuring we don't miss schema ambiguity?
Decision: route
History: [{"action_family": "tool_use", "result": "weak", "step": 0}]
Plan: {"active": true, "operation": "... | 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... |
With only one step left, which available resource should I use to resolve the remaining consistency check?
Decision: route
Plan: {"active": false, "operation": "lookup_semantic"}
Agent State: {"phase": "inspection", "question_length_band": "long", "state_name": "partial_evidence"}
Source State: {"available_modalities":... | 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) |
My last attempt didn't resolve the telemetry requirement; what content should I examine 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": "t... | The operation produces a reliable result for the relevant content under current constraints.. Capabilities: search content. Accepts: text, pdf. Returns: evidence candidates. Evidence role: candidate discovery. Prerequisites: query available. Constraints: indexed sources required. Side effects: read. Arguments: limit (i... |
I need to locate an exact token; which source in the catalog could contain it?
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", "resu... | 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 should I do next to resolve the disputed requirement?
Decision: route
History: [{"action_family": "tool_use", "result": "weak", "step": 0}]
Plan: {"active": true, "operation": "contradiction_resolution"}
Agent State: {"phase": "planning", "question_length_band": "short", "state_name": "initial"}
Source State: {"av... | 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 current source inventory and mixed evidence, what fields and types should I enumerate to resolve the schema-bound dispute?
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, discover fields. Accepts: csv, excel, sqlite. Returns: schema. Evidence role: structure discovery. Prerequisites: source selected. Constraints: structured source required. Side effects:... |
How should I handle event delivery and retry when matching records by exact identifier in the CSV evidence?
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: {... | 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 ensure consistency across complementary sources, what sections and structural landmarks should I compare in the mixed documents?
Decision: route
Plan: {"active": false, "operation": "compare"}
Agent State: {"phase": "governance", "question_length_band": "long", "state_name": "insufficient"}
Source State: {"available... | 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... |
For the next workflow step, given the partial source inventory and hybrid match, what pages or ranges should I join from the complementary evidence?
Decision: route
Plan: {"active": false, "operation": "join"}
Agent State: {"phase": "synthesis", "question_length_band": "long", "state_name": "contradiction"}
Source Stat... | The operation produces a reliable result for the relevant pages or ranges under current constraints.. Capabilities: search document pages. Accepts: pdf. Returns: evidence candidates. Evidence role: candidate discovery. Prerequisites: source selected. Constraints: pdf source required. Side effects: read. Arguments: page... |
Which read-only operation should I use next to reconcile the two complementary sources and resolve the contradiction in event delivery, given that I haven't inspected evidence yet and need schema-bound matching?
Decision: route
History: [{"action_family": "tool_use", "result": "weak", "step": 0}, {"action_family": "too... | 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... |
Given that I've already checked some context but haven't seen any evidence yet, what remaining step can filter by metadata to find the latest value for the acronym-defined technical instruction, avoiding any side effects?
Decision: route
History: [{"action_family": "tool_use", "result": "weak", "step": 0}]
Plan: {"acti... | 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 immediately finalizing, what contrastive next move should I take to select the latest failure-handling evidence from the single passage, given that I already have full context and eight observations, but two requirements remain unresolved?
Decision: route
Plan: {"active": false, "operation": "latest_value_se... | 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)... |
How should I verify the required data transformation by inspecting the missing surrounding context, given that the evidence is contradictory and I need to join on an exact identifier, but I haven't seen any assessment yet?
Decision: route
Plan: {"active": false, "operation": "join"}
Agent State: {"phase": "terminal_rea... | 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 only one step left, should I first compare the retrieved evidence for agreement or conflict before finalizing?
Decision: route
History: [{"action_family": "tool_use", "result": "weak", "step": 0}]
Plan: {"active": true, "operation": "absence_verification"}
Agent State: {"phase": "retrieval", "question_length_band... | 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... |
The last attempt was incomplete; what should I do next to cover all task requirements across the sources?
Decision: route
Plan: {"active": false, "operation": "join"}
Agent State: {"phase": "terminal_readiness", "question_length_band": "long", "state_name": "fresh_sufficient"}
Source State: {"available_modalities": ["t... | 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... |
Do I have enough information from the available sources to proceed, or should I check the catalog for more?
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}, {"acti... | 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 to validate the selected result given the constraints?
Decision: route
History: [{"action_family": "tool_use", "result": "weak", "step": 0}, {"action_family": "tool_use", "result": "weak", "step": 1}]
Plan: {"active": false, "operation": "join"}
Agent State: {"phase": "terminal_readiness", "ques... | 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... |
I've got two observations that seem to conflict. What should I do next to gather more info?
Decision: route
History: [{"action_family": "tool_use", "result": "weak", "step": 0}]
Plan: {"active": true, "operation": "contradiction_resolution"}
Agent State: {"phase": "retrieval", "question_length_band": "short", "state_na... | 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 are my options for finding the right sources to check access permissions?
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"}
Sourc... | 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) |
I need to ensure consistency across the documents. What should I look at next?
Decision: route
History: [{"action_family": "tool_use", "result": "weak", "step": 0}, {"action_family": "tool_use", "result": "weak", "step": 1}]
Plan: {"active": false, "operation": "contradiction_resolution"}
Agent State: {"phase": "synthe... | 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 partial source list, what's the next step to find the exact token?
Decision: route
History: [{"action_family": "tool_use", "result": "weak", "step": 0}, {"action_family": "tool_use", "result": "weak", "step": 1}]
Plan: {"active": true, "operation": "contradiction_resolution"}
Agent State:... | The operation produces a reliable result for an exact name, code, or token under current constraints.. Capabilities: exact pattern search. Accepts: text, code. Returns: evidence candidates. Evidence role: candidate discovery. Prerequisites: query available. Constraints: textual source required. Side effects: read. Argu... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.