anchor stringlengths 723 2.15k | positive stringlengths 153 8.2k |
|---|---|
Given the disputed requirements and stale assessment, which operation should I run next to resolve identifier variations across mixed sources, ensuring no side effects beyond reading and local state updates?
Decision: route
History: [{"action_family": "tool_use", "result": "weak", "step": 0}, {"action_family": "tool_us... | 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... |
I've already checked some sources but haven't inspected any evidence yet. What should I do next to enumerate all matching records from the known SQLite source, without side effects, to fulfill the data transformation?
Decision: route
History: [{"action_family": "tool_use", "result": "weak", "step": 0}, {"action_family"... | 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 ... |
I have partial context and several passages. Rather than listing all sources, what single read-only operation should I perform to extract the document's sections and structural landmarks for the data transformation?
Decision: route
History: [{"action_family": "tool_use", "result": "weak", "step": 0}, {"action_family": ... | This operation handles sections and structural landmarks while preserving the current task state.. 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 have only snippets and need to verify the latest value from the PDF source. What read operation should I run to locate the relevant pages or ranges, considering the schema ambiguity and resource limits?
Decision: route
Plan: {"active": false, "operation": "latest_value_selection"}
Agent State: {"phase": "source_disco... | This operation handles the relevant pages or ranges while preserving the current task state.. Capabilities: search document pages. Accepts: pdf. Returns: evidence candidates. Evidence role: candidate discovery. Prerequisites: source selected. Constraints: pdf source required. Side effects: read. Arguments: page range (... |
With only 2 steps left, which single source should I inspect next to compare the relevant technical instruction?
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}, {... | Invoke the candidate to determine the selected resource from the available resources.. Capabilities: read content. Accepts: text, code. Returns: content. Evidence role: evidence inspection. Prerequisites: source selected. Constraints: local source required. Side effects: read. Arguments: offset (integer optional), reso... |
My last attempt was incomplete. What should I check next to verify absence and resolve version compatibility for symbols and definitions?
Decision: route
History: [{"action_family": "tool_use", "result": "weak", "step": 0}]
Plan: {"active": true, "operation": "absence_verification"}
Agent State: {"phase": "planning", "... | 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 I pull next to join the complementary sources and understand resource limits and lifecycle?
Decision: route
Plan: {"active": false, "operation": "join"}
Agent State: {"phase": "inspection", "question_length_band": "long", "state_name": "partial_evidence"}
Source State: {"available_modaliti... | Apply this capability when the next decision depends on a candidate result.. Capabilities: inspect evidence. Accepts: evidence candidates. Returns: evidence. Evidence role: evidence inspection. Prerequisites: evidence candidate selected. Constraints: candidate evidence required. Side effects: read. Arguments: claim (st... |
What should I do next to enumerate records and gather the missing surrounding context for resource limits and lifecycle?
Decision: route
History: [{"action_family": "tool_use", "result": "weak", "step": 0}, {"action_family": "tool_use", "result": "weak", "step": 1}]
Plan: {"active": false, "operation": "enumerate_recor... | 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 if the two inspected evidence items agree or conflict regarding the telemetry trace requirement.
Decision: route
Plan: {"active": false, "operation": "lookup_semantic"}
Agent State: {"phase": "governance", "question_length_band": "long", "state_name": "insufficient"}
Source State: {"available_modalities": ["excel... | 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 be done next to resolve the disputed coverage of the telemetry requirements?
Decision: route
History: [{"action_family": "tool_use", "result": "weak", "step": 0}, {"action_family": "tool_use", "result": "weak", "step": 1}, {"action_family": "tool_use", "result": "weak", "step": 2}, {"action_family": "tool_u... | 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... |
Do we have enough information to proceed with the next workflow step?
Decision: route
History: [{"action_family": "tool_use", "result": "weak", "step": 0}]
Plan: {"active": false, "operation": "lookup_semantic"}
Agent State: {"phase": "inspection", "question_length_band": "short", "state_name": "partial_evidence"}
Sour... | 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... |
Considering the contradictory evidence and quality constraints, what should be the next action?
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": "contra... | The operation produces a reliable result for the selected result or next action under current constraints.. Capabilities: finalize selection. Accepts: assessment, governance state. Returns: terminal result. Evidence role: terminal decision. Prerequisites: requirements complete. Constraints: fresh sufficient assessment ... |
Given the disputed requirements and broad query, what read-only step should I take next to enumerate possible sources, without modifying any state?
Decision: route
Plan: {"active": true, "operation": "enumerate_sources"}
Agent State: {"phase": "planning", "question_length_band": "long", "state_name": "initial"}
Source ... | 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),... |
Since I've already inspected multiple sources and exhausted the evidence, what resource can I still check to confirm absence, without changing 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 when the task requires the available resources.. Capabilities: list sources, discover sources. Accepts: metadata. Returns: source list. Evidence role: source discovery. Prerequisites: none. Constraints: none. Side effects: read. Arguments: filters (object required), scope (string optional) |
Given the version noise and partial inventory, what content should I examine next to assess compatibility, rather than jumping to a terminal result?
Decision: route
Plan: {"active": false, "operation": "compatibility"}
Agent State: {"phase": "governance", "question_length_band": "long", "state_name": "insufficient"}
So... | 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... |
To verify the exact event delivery token, which evidence source should I consult next given the complementary sources and known inventory?
Decision: route
Plan: {"active": false, "operation": "enumerate_sources"}
Agent State: {"phase": "terminal_readiness", "question_length_band": "long", "state_name": "fresh_sufficien... | 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 my limited remaining steps, what metadata and filters should I inspect next to join the relevant evidence?
Decision: route
History: [{"action_family": "tool_use", "result": "weak", "step": 0}]
Plan: {"active": false, "operation": "join"}
Agent State: {"phase": "source_discovery", "question_length_band": "long", "... | 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... |
My previous attempt was ambiguous; what fields, types, and structure should I examine to understand event delivery and retry behavior?
Decision: route
History: [{"action_family": "tool_use", "result": "weak", "step": 0}, {"action_family": "tool_use", "result": "weak", "step": 1}, {"action_family": "tool_use", "result":... | The operation produces a reliable result for 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... |
Which catalog entries match my exact identifier to verify version compatibility?
Decision: route
Plan: {"active": false, "operation": "lookup_exact"}
Agent State: {"phase": "inspection", "question_length_band": "short", "state_name": "partial_evidence"}
Source State: {"available_modalities": ["csv", "metadata"], "evide... | 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 sections and structural landmarks should I look at to resolve the contradiction in the technical instruction?
Decision: route
History: [{"action_family": "tool_use", "result": "weak", "step": 0}, {"action_family": "tool_use", "result": "weak", "step": 1}]
Plan: {"active": true, "operation": "contradiction_resoluti... | 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 ... |
Which pages or ranges should be used for the data transformation?
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", "state_name": "fresh_sufficie... | 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 resource should be selected 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": "lookup_semantic"}
Agent State: {"phase": "source_discovery", "question_... | This operation handles the selected resource while preserving the current task state.. Capabilities: read content. Accepts: text, code. Returns: content. Evidence role: evidence inspection. Prerequisites: source selected. Constraints: local source required. Side effects: read. Arguments: offset (integer optional), reso... |
What symbols and definitions are needed to satisfy the validation constraints?
Decision: route
History: [{"action_family": "tool_use", "result": "weak", "step": 0}, {"action_family": "tool_use", "result": "weak", "step": 1}, {"action_family": "tool_use", "result": "weak", "step": 2}, {"action_family": "tool_use", "resu... | 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 stale assessment and no prior inspection, which candidate result is compatible with the technical instruction?
Decision: route
History: [{"action_family": "tool_use", "result": "weak", "step": 0}, {"action_family": "tool_use", "result": "weak", "step": 1}]
Plan: {"active": false, "operation": "compatibility"}... | Apply this capability when the next decision depends on a candidate result.. Capabilities: inspect evidence, verify provenance. Accepts: evidence candidates. Returns: evidence. Evidence role: evidence inspection. Prerequisites: evidence candidate selected. Constraints: candidate evidence required. Side effects: read. A... |
I need to find the exact section in the spreadsheet that describes the required context for the task. What operation should I perform next, considering only read-only actions and ensuring the result is based on the current evidence?
Decision: route
History: [{"action_family": "tool_use", "result": "weak", "step": 0}, {... | 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 inspected multiple sources and found conflicting results. What should we do next to determine if there is agreement or conflict between the results, given that the assessment is stale and we need to enumerate records?
Decision: route
Plan: {"active": false, "operation": "enumerate_records"}
Agent State: {"phase":... | This candidate supports controlled inspection of agreement or conflict between results.. Capabilities: compare evidence. Accepts: evidence. Returns: evidence comparison. Evidence role: evidence synthesis. Prerequisites: evidence inspected. Constraints: multiple evidence required. Side effects: none. Arguments: comparis... |
I need to join information from different sources to understand the access rules. Should I proceed with a structural match or is there a better next step to ensure full coverage of the requirements?
Decision: route
History: [{"action_family": "tool_use", "result": "weak", "step": 0}, {"action_family": "tool_use", "resu... | 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... |
How can I verify that the available information is sufficient to conclude the access rules? What operation should I perform next to check compatibility and ensure we have the full context?
Decision: route
History: [{"action_family": "tool_use", "result": "weak", "step": 0}, {"action_family": "tool_use", "result": "weak... | 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 my remaining 8 steps, which candidate should I prioritize to resolve the near-duplicate field definitions?
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 ... | 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... |
My previous attempt was incomplete; what should I do next to enumerate sources given the version noise?
Decision: route
History: [{"action_family": "tool_use", "result": "weak", "step": 0}, {"action_family": "tool_use", "result": "weak", "step": 1}, {"action_family": "tool_use", "result": "weak", "step": 2}, {"action_f... | 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... |
What resources are available for event delivery and retry behavior?
Decision: route
Plan: {"active": false, "operation": "join"}
Agent State: {"phase": "inspection", "question_length_band": "short", "state_name": "partial_evidence"}
Source State: {"available_modalities": ["pdf", "metadata"], "evidence_topology_observed... | 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 is the next action to gather relevant content on telemetry and trace requirements?
Decision: route
History: [{"action_family": "tool_use", "result": "weak", "step": 0}]
Plan: {"active": false, "operation": "enumerate_sources"}
Agent State: {"phase": "governance", "question_length_band": "short", "state_name": "ins... | 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... |
I have two CSV files with near-duplicate rows and need to merge them. What should I do next?
Decision: route
History: [{"action_family": "tool_use", "result": "weak", "step": 0}, {"action_family": "tool_use", "result": "weak", "step": 1}, {"action_family": "tool_use", "result": "weak", "step": 2}, {"action_family": "to... | 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... |
I'm about to wrap up, but I need to verify that a specific piece of information is absent from the PDFs. What should I check?
Decision: route
History: [{"action_family": "tool_use", "result": "weak", "step": 0}]
Plan: {"active": false, "operation": "absence_verification"}
Agent State: {"phase": "terminal_readiness", "q... | 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... |
I need to combine data from multiple sources into a unified dataset. What's the next action?
Decision: route
Plan: {"active": false, "operation": "join"}
Agent State: {"phase": "synthesis", "question_length_band": "short", "state_name": "contradiction"}
Source State: {"available_modalities": ["csv", "metadata"], "evide... | 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 schema ambiguity, what should I do to find matching records for telemetry and trace requirements?
Decision: route
Plan: {"active": true, "operation": "compatibility"}
Agent State: {"phase": "retrieval", "question_length_band": "long", "state_name": "retrieval"}
Source State: {"available_modalities": ["text", ... | 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 stale assessment and partial context, what read-only operation can identify structural landmarks without writing state?
Decision: route
History: [{"action_family": "tool_use", "result": "weak", "step": 0}, {"action_family": "tool_use", "result": "weak", "step": 1}]
Plan: {"active": false, "operation": "compat... | 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 snippets from two sources but haven't resolved the acronym; what remains to enumerate records to find the relevant page ranges?
Decision: route
History: [{"action_family": "tool_use", "result": "weak", "step": 0}]
Plan: {"active": true, "operation": "enumerate_records"}
Agent State: {"phase": "planning", ... | 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... |
Instead of jumping to a broad search, which precise operation on the selected resource would resolve the near-duplicate field definitions?
Decision: route
History: [{"action_family": "tool_use", "result": "weak", "step": 0}]
Plan: {"active": true, "operation": "contradiction_resolution"}
Agent State: {"phase": "retriev... | This operation handles the selected resource while preserving the current task state.. 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... |
How can we verify the next workflow step by inspecting symbols and definitions from the code source without assuming the inventory?
Decision: route
Plan: {"active": false, "operation": "lookup_exact"}
Agent State: {"phase": "governance", "question_length_band": "long", "state_name": "insufficient"}
Source State: {"avai... | 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 the two unresolved requirements?
Decision: route
History: [{"action_family": "tool_use", "result": "weak", "step": 0}, {"action_family": "tool_use", "result": "weak", "step": 1}, {"action_family": "tool_use", "result": "weak", "step": 2}, {"acti... | 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... |
My earlier attempt was incomplete. What should I check next to verify the absence of the expected identifier in the surrounding context?
Decision: route
History: [{"action_family": "tool_use", "result": "weak", "step": 0}, {"action_family": "tool_use", "result": "weak", "step": 1}, {"action_family": "tool_use", "result... | The operation produces a reliable result for missing surrounding context under current constraints.. Capabilities: expand context. Accepts: evidence candidates, evidence. Returns: evidence. Evidence role: context expansion. Prerequisites: evidence candidate selected. Constraints: incomplete context required. Side effec... |
I need to compare results for resource limits and lifecycle. Which candidate output shows agreement or conflict between them?
Decision: route
Plan: {"active": false, "operation": "lookup_semantic"}
Agent State: {"phase": "governance", "question_length_band": "long", "state_name": "insufficient"}
Source State: {"availab... | 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 step should I take to verify coverage of access rules and permissions given the version noise?
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 candidate supports controlled inspection of task requirements and coverage.. Capabilities: update requirements. Accepts: evidence, agent state. Returns: governance state. Evidence role: governance update. Prerequisites: evidence inspected. Constraints: tracked requirements required. Side effects: local state write... |
We have conflicting evidence from two sources. Do we have enough information to resolve this?
Decision: route
Plan: {"active": false, "operation": "contradiction_resolution"}
Agent State: {"phase": "synthesis", "question_length_band": "short", "state_name": "contradiction"}
Source State: {"available_modalities": ["code... | 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 based on the evidence we've inspected?
Decision: route
History: [{"action_family": "tool_use", "result": "weak", "step": 0}, {"action_family": "tool_use", "result": "weak", "step": 1}, {"action_family": "tool_use", "result": "weak", "step": 2}, {"action_family": "tool_use", "result": "weak", "ste... | This operation handles the selected result or next action while preserving the current task state.. Capabilities: finalize selection. Accepts: assessment, governance state. Returns: terminal result. Evidence role: terminal decision. Prerequisites: requirements complete. Constraints: fresh sufficient assessment required... |
We need to gather more information about access permissions. What's the best next step?
Decision: route
Plan: {"active": true, "operation": "join"}
Agent State: {"phase": "retrieval", "question_length_band": "short", "state_name": "retrieval"}
Source State: {"available_modalities": ["sqlite", "metadata"], "evidence_top... | 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... |
We're handling a failure and need to inspect available resources. What tools can we use?
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": "ins... | 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 assessment and exact identifier, which read-only operation retrieves relevant content for version compatibility, without side effects?
Decision: route
History: [{"action_family": "tool_use", "result": "weak", "step": 0}, {"action_family": "tool_use", "result": "weak", "step": 1}]
Plan: {"active": true, "ope... | Apply this capability when the next decision depends on the relevant content.. Capabilities: search content. Accepts: text, pdf. Returns: evidence candidates. Evidence role: candidate discovery. Prerequisites: query available. Constraints: indexed sources required. Side effects: read. Arguments: limit (integer optional... |
We've inspected multiple sources and found complementary evidence; what remains to compare for the exact access-control token, given schema-only differences?
Decision: route
Plan: {"active": false, "operation": "compare"}
Agent State: {"phase": "governance", "question_length_band": "long", "state_name": "insufficient"}... | 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 ... |
With full context and complete requirements, what next move (not just listing sources) best compares event delivery metadata to avoid retry noise?
Decision: route
History: [{"action_family": "tool_use", "result": "weak", "step": 0}, {"action_family": "tool_use", "result": "weak", "step": 1}]
Plan: {"active": false, "op... | Use this candidate when the task requires 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) |
To verify telemetry schema under ambiguity, what evidence-oriented step should we take to enumerate candidate sources matching the required fields?
Decision: route
History: [{"action_family": "tool_use", "result": "weak", "step": 0}]
Plan: {"active": false, "operation": "enumerate_sources"}
Agent State: {"phase": "gove... | 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, prioritize finding matching records for the entity, filtering by metadata, while ignoring the acronym issue.
Decision: route
History: [{"action_family": "tool_use", "result": "weak", "step": 0}]
Plan: {"active": true, "operation": "lookup_semantic"}
Agent State: {"phase": "retrieval", "questio... | 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 previous attempt was incomplete. What should we do next to enumerate records and identify structural landmarks, given the split context?
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 sections and structural landmarks under current constraints.. Capabilities: inspect document structure. Accepts: pdf. Returns: document structure. Evidence role: structure discovery. Prerequisites: source selected. Constraints: pdf source required. Side effects: read. Argume... |
Given the disputed requirements and only one step left, which resource should we inspect to find the relevant pages or ranges, without side effects?
Decision: route
Plan: {"active": false, "operation": "enumerate_records"}
Agent State: {"phase": "inspection", "question_length_band": "long", "state_name": "partial_evide... | This candidate supports controlled inspection of 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 ra... |
What should we do next to enumerate sources and select the resource, focusing on event delivery and retry behavior?
Decision: route
History: [{"action_family": "tool_use", "result": "weak", "step": 0}, {"action_family": "tool_use", "result": "weak", "step": 1}, {"action_family": "tool_use", "result": "weak", "step": 2}... | This candidate supports controlled inspection of the selected 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... |
What next operation should pick the latest telemetry symbol definitions from the mixed sources?
Decision: route
Plan: {"active": false, "operation": "latest_value_selection"}
Agent State: {"phase": "governance", "question_length_band": "short", "state_name": "insufficient"}
Source State: {"available_modalities": ["text... | 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 operation would surface the exact workflow step we need, given the schema-bound lookup?
Decision: route
Plan: {"active": false, "operation": "lookup_exact"}
Agent State: {"phase": "governance", "question_length_band": "short", "state_name": "insufficient"}
Source State: {"available_modalities": ["text", "pdf", "c... | 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... |
To verify absence of surrounding context for the exact identifier, what operation should be performed?
Decision: route
Plan: {"active": false, "operation": "absence_verification"}
Agent State: {"phase": "terminal_readiness", "question_length_band": "long", "state_name": "fresh_sufficient"}
Source State: {"available_mod... | 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... |
Considering the contradictory results and stale assessment, what operation compares evidence to check consistency across sources?
Decision: route
History: [{"action_family": "tool_use", "result": "weak", "step": 0}]
Plan: {"active": false, "operation": "latest_value_selection"}
Agent State: {"phase": "synthesis", "ques... | Apply this capability when the next decision depends on agreement or conflict between results.. Capabilities: compare evidence, detect contradictions. Accepts: evidence. Returns: evidence comparison. Evidence role: evidence synthesis. Prerequisites: evidence inspected. Constraints: multiple evidence required. Side effe... |
Given the schema ambiguity and partial progress, what operation should we perform next to resolve contradictions, ensuring no side effects beyond local state writes and reads?
Decision: route
Plan: {"active": true, "operation": "contradiction_resolution"}
Agent State: {"phase": "retrieval", "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 inspected multiple sources and have one piece of evidence, but requirements are unmet. What should we do next to determine if we have enough information, considering we can read and write local state only?
Decision: route
History: [{"action_family": "tool_use", "result": "weak", "step": 0}, {"action_family": "too... | 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 contradictory evidence and a long document, should we extract the exact matching identifier from the PDF, or is there a better next step to ensure compatibility, given we can only read and write local state?
Decision: route
History: [{"action_family": "tool_use", "result": "weak", "step": 0}, {"action_family": "t... | 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... |
Since our assessment is stale and we need to enumerate sources despite identifier variation, what information-gathering step should we take next to verify the result, using only local state writes and reads?
Decision: route
History: [{"action_family": "tool_use", "result": "weak", "step": 0}]
Plan: {"active": true, "op... | This operation handles the best next information-gathering step while preserving the current task state.. Capabilities: plan retrieval. Accepts: agent state, text. Returns: plan. Evidence role: none. Prerequisites: objective available. Constraints: none. Side effects: local state write. Arguments: objective (string req... |
We have 2 steps left and 8 evidence pieces with contradictions. Which available resources should we prioritize to resolve the quality constraint?
Decision: route
History: [{"action_family": "tool_use", "result": "weak", "step": 0}]
Plan: {"active": true, "operation": "enumerate_records"}
Agent State: {"phase": "plannin... | 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) |
The prior attempt didn't work. What relevant content should we look for next to recover and find the technical instruction?
Decision: route
Plan: {"active": false, "operation": "lookup_semantic"}
Agent State: {"phase": "source_discovery", "question_length_band": "long", "state_name": "source_discovery"}
Source State: {... | 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... |
We need an exact name or code and have no steps left. What resource in our catalog can provide it for consistency checks?
Decision: route
Plan: {"active": true, "operation": "enumerate_records"}
Agent State: {"phase": "retrieval", "question_length_band": "long", "state_name": "retrieval"}
Source State: {"available_moda... | 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... |
For the next action, what resource metadata and filters should we use to join the relevant passages?
Decision: route
Plan: {"active": false, "operation": "join"}
Agent State: {"phase": "synthesis", "question_length_band": "long", "state_name": "contradiction"}
Source State: {"available_modalities": ["sqlite", "metadata... | 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... |
What is the schema of the CSV file that lists 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": "source_discovery", "quest... | Use this candidate when the task requires fields, types, and structure.. Capabilities: inspect structured schema. Accepts: csv, excel, sqlite. Returns: schema. Evidence role: structure discovery. Prerequisites: source selected. Constraints: structured source required. Side effects: read. Arguments: include types (boole... |
Which rows in the dataset correspond to the same entity based on the metadata filter?
Decision: route
Plan: {"active": true, "operation": "lookup_semantic"}
Agent State: {"phase": "planning", "question_length_band": "short", "state_name": "initial"}
Source State: {"available_modalities": ["csv", "metadata"], "evidence_... | 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... |
How are the field definitions organized in the document to assess compatibility?
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": "governance", "q... | The operation produces a reliable result for sections and structural landmarks under current constraints.. Capabilities: inspect document structure, discover sections. Accepts: pdf. Returns: document structure. Evidence role: structure discovery. Prerequisites: source selected. Constraints: pdf source required. Side ef... |
Which pages contain the definitions for the fields that need to be compared?
Decision: route
History: [{"action_family": "tool_use", "result": "weak", "step": 0}, {"action_family": "tool_use", "result": "weak", "step": 1}]
Plan: {"active": false, "operation": "enumerate_sources"}
Agent State: {"phase": "synthesis", "qu... | 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... |
We have partial requirements and 4 unresolved issues. Which resource should we inspect next to join the evidence, given we're in failure recovery?
Decision: route
History: [{"action_family": "tool_use", "result": "weak", "step": 0}, {"action_family": "tool_use", "result": "weak", "step": 1}, {"action_family": "tool_use... | 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 checked some sources but not all. What remains to enumerate records from the code to clarify field definitions, given acronym ambiguity?
Decision: route
History: [{"action_family": "tool_use", "result": "weak", "step": 0}]
Plan: {"active": false, "operation": "enumerate_records"}
Agent State: {"phase": "inspectio... | 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)... |
We have complete requirements but need consistency checks. Should we compare the candidate result against the other source, or just accept it?
Decision: route
History: [{"action_family": "tool_use", "result": "weak", "step": 0}, {"action_family": "tool_use", "result": "weak", "step": 1}]
Plan: {"active": false, "operat... | 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)... |
We're synthesizing and need to verify the result. What evidence should we retrieve to confirm the resource limits and lifecycle, given partial context?
Decision: route
Plan: {"active": false, "operation": "lookup_semantic"}
Agent State: {"phase": "synthesis", "question_length_band": "long", "state_name": "contradiction... | 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... |
With only 8 steps left and conflicting evidence from two sources, what should I prioritize to resolve the disagreement?
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 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. How should I recover to ensure my synthesis covers all requirements?
Decision: route
History: [{"action_family": "tool_use", "result": "weak", "step": 0}, {"action_family": "tool_use", "result": "weak", "step": 1}, {"action_family": "tool_use", "result": "weak", "step": 2}, {"action_fam... | 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... |
I have partial progress and 4 steps left. What should I do to verify I have enough information for the transformation?
Decision: route
History: [{"action_family": "tool_use", "result": "weak", "step": 0}]
Plan: {"active": true, "operation": "enumerate_records"}
Agent State: {"phase": "planning", "question_length_band":... | Apply this capability when the next decision depends on whether available information is sufficient.. Capabilities: assess evidence. Accepts: evidence, governance state. Returns: assessment. Evidence role: governance assessment. Prerequisites: requirements updated. Constraints: canonical evidence set required. Side eff... |
Given the contradictory evidence and complete requirements, what should I do next to verify the absence?
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 Sta... | 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 complete requirements and known sources, which next step best gathers evidence to verify consistency across the Excel data?
Decision: route
History: [{"action_family": "tool_use", "result": "weak", "step": 0}, {"action_family": "tool_use", "result": "weak", "step": 1}]
Plan: {"active": true, "operation": "com... | This operation handles the best next information-gathering step while preserving the current task state.. Capabilities: plan retrieval. Accepts: agent state, text. Returns: plan. Evidence role: none. Prerequisites: objective available. Constraints: none. Side effects: local state write. Arguments: objective (string opt... |
What resources are available for handling the event delivery and retry behavior?
Decision: route
History: [{"action_family": "tool_use", "result": "weak", "step": 0}]
Plan: {"active": false, "operation": "enumerate_sources"}
Agent State: {"phase": "inspection", "question_length_band": "short", "state_name": "partial_ev... | 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 ensure consistency across sources, what content should I examine next?
Decision: route
History: [{"action_family": "tool_use", "result": "weak", "step": 0}]
Plan: {"active": true, "operation": "compatibility"}
Agent State: {"phase": "planning", "question_length_band": "short", "state_name": "initial"}
Source State: ... | 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 no prior searches and unknown sources, what exact name or code should I look up to start consistency checks?
Decision: route
Plan: {"active": true, "operation": "lookup_exact"}
Agent State: {"phase": "planning", "question_length_band": "long", "state_name": "initial"}
Source State: {"available_modalities": ["text... | 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... |
Before we finalize, I need to confirm that no source mentions this entity. Can you check the metadata and filters to see if any candidate lacks the required evidence?
Decision: route
History: [{"action_family": "tool_use", "result": "weak", "step": 0}, {"action_family": "tool_use", "result": "weak", "step": 1}]
Plan: {... | Apply this capability when the next decision depends on resource metadata and filters.. Capabilities: search metadata. Accepts: metadata. Returns: source list. Evidence role: source discovery. Prerequisites: none. Constraints: metadata catalog required. Side effects: read. Arguments: filters (object required), sort (st... |
We've checked the SQLite source but haven't looked at its schema yet. What fields and types does it have, and how does that affect the next step?
Decision: route
History: [{"action_family": "tool_use", "result": "weak", "step": 0}]
Plan: {"active": false, "operation": "lookup_semantic"}
Agent State: {"phase": "inspecti... | 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... |
Given the two matching records from different sources, should we join them now, or would it be premature to combine before we have all evidence?
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 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 need to verify the result from the PDF. Can you identify the sections and structural landmarks that would let us compare the evidence across sources?
Decision: route
History: [{"action_family": "tool_use", "result": "weak", "step": 0}, {"action_family": "tool_use", "result": "weak", "step": 1}]
Plan: {"active": fals... | This operation handles 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... |
Given my remaining step budget is zero, which operation should I prioritize next to locate the relevant pages or ranges for the broad query, given the stale assessment and identifier variation?
Decision: route
Plan: {"active": true, "operation": "join"}
Agent State: {"phase": "retrieval", "question_length_band": "long"... | 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 (... |
The previous attempt was incomplete or ambiguous; what recovery step should I take to deliver the event to the selected resource, considering the disputed requirement progress and multiple passages?
Decision: route
History: [{"action_family": "tool_use", "result": "weak", "step": 0}, {"action_family": "tool_use", "resu... | 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... |
Without naming a specific tool, which catalog or resource operation would help me find the symbols and definitions needed for version compatibility, given the partial inventory and version noise?
Decision: route
History: [{"action_family": "tool_use", "result": "weak", "step": 0}, {"action_family": "tool_use", "result"... | This candidate supports controlled inspection of symbols and definitions.. Capabilities: inspect code structure, resolve symbols. Accepts: code. Returns: content, code structure. Evidence role: evidence inspection. Prerequisites: source selected. Constraints: code source required. Side effects: read. Arguments: depth (... |
What should I do next to evaluate a candidate result for resource limits and lifecycle, given the stale assessment and schema ambiguity?
Decision: route
History: [{"action_family": "tool_use", "result": "weak", "step": 0}, {"action_family": "tool_use", "result": "weak", "step": 1}, {"action_family": "tool_use", "result... | 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 verify the absence of a detail in the document. The current evidence only covers part of the context. What should I do next?
Decision: route
Plan: {"active": true, "operation": "absence_verification"}
Agent State: {"phase": "retrieval", "question_length_band": "long", "state_name": "retrieval"}
Source State: ... | 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... |
Compare the results from the telemetry and trace requirements to see if they agree or conflict. What's the next step?
Decision: route
Plan: {"active": false, "operation": "compare"}
Agent State: {"phase": "synthesis", "question_length_band": "long", "state_name": "contradiction"}
Source State: {"available_modalities": ... | 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... |
I need to find the exact workflow step that satisfies the task requirements. What should I do next?
Decision: route
Plan: {"active": false, "operation": "lookup_exact"}
Agent State: {"phase": "inspection", "question_length_band": "short", "state_name": "partial_evidence"}
Source State: {"available_modalities": ["excel"... | 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... |
Given the contradiction in the telemetry evidence and the partial source inventory, what should I do next to resolve it?
Decision: route
History: [{"action_family": "tool_use", "result": "weak", "step": 0}]
Plan: {"active": true, "operation": "contradiction_resolution"}
Agent State: {"phase": "retrieval", "question_len... | Apply this capability when the next decision depends on whether available information is sufficient.. Capabilities: assess evidence, validate sufficiency. Accepts: evidence, governance state. Returns: assessment. Evidence role: governance assessment. Prerequisites: requirements updated. Constraints: canonical evidence ... |
Compare the two text sources we just inspected and tell me which one is compatible with our versioning requirement, but avoid any operation that writes state.
Decision: route
History: [{"action_family": "tool_use", "result": "weak", "step": 0}]
Plan: {"active": false, "operation": "compare"}
Agent State: {"phase": "ter... | 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 SQLite inventory and found one record, but the requirement is still disputed. What should we do next to gather the missing evidence, considering we can only read and update local state?
Decision: route
History: [{"action_family": "tool_use", "result": "weak", "step": 0}, {"action_family": "too... | 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... |
We've inspected multiple sources and have eight pieces of evidence, but the field definitions are still unclear. Should we fetch the available resources to join the schema information, rather than searching again?
Decision: route
History: [{"action_family": "tool_use", "result": "weak", "step": 0}, {"action_family": "t... | 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 we verify the telemetry and trace requirements by comparing the relevant content from the text sources we've partially inspected, without modifying anything?
Decision: route
History: [{"action_family": "tool_use", "result": "weak", "step": 0}]
Plan: {"active": false, "operation": "compare"}
Agent State: {"phase... | 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.