anchor
stringlengths
723
2.15k
positive
stringlengths
153
8.2k
Given the limited steps and stale assessment, which operation should run next to find matching records in the Excel source for event retry details? Decision: route History: [{"action_family": "tool_use", "result": "weak", "step": 0}] Plan: {"active": false, "operation": "absence_verification"} Agent State: {"phase": "s...
Invoke the candidate to determine matching records from the available resources.. Capabilities: search structured records. Accepts: csv, excel, sqlite. Returns: evidence candidates. Evidence role: candidate discovery. Prerequisites: schema known. Constraints: structured source required. Side effects: read. Arguments: l...
After the ambiguous attempt failed, what operation recovers by identifying sections and landmarks in the document to locate the technical instruction? Decision: route Plan: {"active": false, "operation": "absence_verification"} Agent State: {"phase": "governance", "question_length_band": "long", "state_name": "insuffic...
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...
Considering the partial catalog and conflicting snippets, what resource-oriented step determines the correct page range for the next workflow automation task? 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 relevant pages or ranges.. Capabilities: search document pages. Accepts: pdf. Returns: evidence candidates. Evidence role: candidate discovery. Prerequisites: source selected. Constraints: pdf source required. Side effects: read. Arguments: page range (array r...
What is the concise next action to inspect the selected CSV resource for event delivery behavior, given no evidence has been found yet? Decision: route History: [{"action_family": "tool_use", "result": "weak", "step": 0}, {"action_family": "tool_use", "result": "weak", "step": 1}, {"action_family": "tool_use", "result"...
Use this candidate when the task requires the selected resource.. Capabilities: read content, inspect full source. Accepts: text, code. Returns: content. Evidence role: evidence inspection. Prerequisites: source selected. Constraints: local source required. Side effects: read. Arguments: offset (integer required), reso...
Directly state the operation to examine symbols and definitions in the code source to clarify the relevant technical instruction for document analysis. Decision: route History: [{"action_family": "tool_use", "result": "weak", "step": 0}, {"action_family": "tool_use", "result": "weak", "step": 1}] Plan: {"active": false...
Use this candidate when the task requires 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...
How can I verify the candidate result for event handling without explicitly searching, using the current multi-source context and remaining budget? Decision: route History: [{"action_family": "tool_use", "result": "weak", "step": 0}, {"action_family": "tool_use", "result": "weak", "step": 1}, {"action_family": "tool_us...
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 achieve consistency across sources, what indirect operation fills in the missing surrounding context from the SQLite database for the latest values? Decision: route History: [{"action_family": "tool_use", "result": "weak", "step": 0}, {"action_family": "tool_use", "result": "weak", "step": 1}, {"action_family": "too...
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...
Combining the need for exact lookup with the constraint of a long document, what operation determines agreement or conflict for the next workflow step? Decision: route History: [{"action_family": "tool_use", "result": "weak", "step": 0}, {"action_family": "tool_use", "result": "weak", "step": 1}] Plan: {"active": false...
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 schema ambiguity in our data quality validation, what read-only operation should we use next to verify requirement coverage without altering local state? Decision: route History: [{"action_family": "tool_use", "result": "weak", "step": 0}, {"action_family": "tool_use", "result": "weak", "step": 1}] Plan: {"ac...
This candidate supports controlled inspection of task requirements and coverage.. Capabilities: update requirements, track coverage. Accepts: evidence, agent state. Returns: governance state. Evidence role: governance update. Prerequisites: evidence inspected. Constraints: tracked requirements required. Side effects: l...
We have checked two evidence passages but still face version compatibility contradictions. Is the current information sufficient to proceed, or do we need to assess it further? Decision: route History: [{"action_family": "tool_use", "result": "weak", "step": 0}, {"action_family": "tool_use", "result": "weak", "step": 1...
This candidate supports controlled inspection of 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...
Since the assessment is fresh and resources are limited, should I finalize the selection now or inspect document structure first to resolve remaining acronym ambiguities? Decision: route History: [{"action_family": "tool_use", "result": "weak", "step": 0}] Plan: {"active": false, "operation": "contradiction_resolution"...
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...
How should I verify the best next step for gathering information on resource limits, given that current evidence sources are contradictory and near-duplicate? Decision: route Plan: {"active": true, "operation": "compare"} Agent State: {"phase": "retrieval", "question_length_band": "long", "state_name": "retrieval"} Sou...
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 four steps remaining and stale assessments, what is the priority order for inspecting available text resources to satisfy telemetry trace requirements? 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 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 previous search was ambiguous. How can I recover by finding the relevant technical instruction content from the available code sources? Decision: route History: [{"action_family": "tool_use", "result": "weak", "step": 0}, {"action_family": "tool_use", "result": "weak", "step": 1}] Plan: {"active": true, "operation":...
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...
Which catalog-oriented operation should I use to find the exact technical token needed, considering the contradictory evidence from mixed source types? Decision: route History: [{"action_family": "tool_use", "result": "weak", "step": 0}, {"action_family": "tool_use", "result": "weak", "step": 1}, {"action_family": "too...
This candidate supports controlled inspection of an exact name, code, or token.. Capabilities: exact pattern search, identifier search. Accepts: text, code. Returns: evidence candidates. Evidence role: candidate discovery. Prerequisites: query available. Constraints: textual source required. Side effects: read. Argumen...
What is the next action to check resource metadata filters for the technical instruction, given the long document needle obstacle? Decision: route History: [{"action_family": "tool_use", "result": "weak", "step": 0}] Plan: {"active": false, "operation": "lookup_exact"} Agent State: {"phase": "source_discovery", "questi...
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 CSV source and schema ambiguity, what is the next step to determine the field types and structure for access rules? Decision: route History: [{"action_family": "tool_use", "result": "weak", "step": 0}, {"action_family": "tool_use", "result": "weak", "step": 1}] Plan: {"active": true, "operation": "enumerate_r...
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...
Since the identifiers vary across mixed sources, how can I reconcile the consistency checks using the available structured data? Decision: route Plan: {"active": false, "operation": "compatibility"} Agent State: {"phase": "governance", "question_length_band": "long", "state_name": "insufficient"} Source State: {"availa...
This operation handles matching records while preserving the current task state.. Capabilities: search structured records. Accepts: csv, excel, sqlite. Returns: evidence candidates. Evidence role: candidate discovery. Prerequisites: schema known. Constraints: structured source required. Side effects: read. Arguments: l...
I need to clarify the telemetry trace requirements. How do I locate the specific sections and landmarks within the document to support this? Decision: route History: [{"action_family": "tool_use", "result": "weak", "step": 0}] Plan: {"active": false, "operation": "enumerate_sources"} Agent State: {"phase": "source_disc...
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, which pages in the PDF contain the relevant information, given the acronym obstacle and limited remaining steps? Decision: route History: [{"action_family": "tool_use", "result": "weak", "step": 0}, {"action_family": "tool_use", "result": "weak", "step": 1}] Plan: {"active": false, "operatio...
Apply this capability when the next decision depends on 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: ...
I have a code source selected. What read-only operation lets me examine the resource limits without altering the current state? Decision: route History: [{"action_family": "tool_use", "result": "weak", "step": 0}, {"action_family": "tool_use", "result": "weak", "step": 1}] Plan: {"active": false, "operation": "lookup_s...
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 haven't checked the symbols yet. How do we inspect the code structure to verify field compatibility for schema management? Decision: route Plan: {"active": false, "operation": "compare"} Agent State: {"phase": "terminal_readiness", "question_length_band": "long", "state_name": "fresh_sufficient"} Source State: {"ava...
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)...
Should I inspect the candidate result from the Excel file or search the metadata catalog again to confirm the access permissions? Decision: route History: [{"action_family": "tool_use", "result": "weak", "step": 0}, {"action_family": "tool_use", "result": "weak", "step": 1}] Plan: {"active": false, "operation": "join"}...
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 can I verify if the single snippet found provides enough context for the access rules, or do I need to expand the surrounding information? Decision: route History: [{"action_family": "tool_use", "result": "weak", "step": 0}, {"action_family": "tool_use", "result": "weak", "step": 1}, {"action_family": "tool_use", "...
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 eight steps left and conflicting event retry data, which operation best verifies if the sources agree? 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 agreement or conflict between results from the available resources.. Capabilities: compare evidence. Accepts: evidence. Returns: evidence comparison. Evidence role: evidence synthesis. Prerequisites: evidence inspected. Constraints: multiple evidence required. Side effects: none. Argum...
My last check missed field details. Given four unresolved items, how should I update coverage to verify schema compatibility? Decision: route History: [{"action_family": "tool_use", "result": "weak", "step": 0}, {"action_family": "tool_use", "result": "weak", "step": 1}] Plan: {"active": false, "operation": "absence_ve...
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...
Two steps remain. Which catalog-based check confirms if current quality validation data meets the strict constraints needed? 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", "...
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...
Next action: confirm if trace telemetry requirements are met so we can finalize the result. 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_e...
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...
One step left. What specific retrieval move resolves the contradictory telemetry logs for this trace requirement? Decision: route Plan: {"active": true, "operation": "absence_verification"} Agent State: {"phase": "retrieval", "question_length_band": "long", "state_name": "retrieval"} Source State: {"available_modalitie...
Use this candidate when the task requires the best next information-gathering step.. Capabilities: plan retrieval. Accepts: agent state, text. Returns: plan. Evidence role: none. Prerequisites: objective available. Constraints: none. Side effects: local state write. Arguments: objective (string required), priority (str...
How can I identify which resources contain the field definitions needed to resolve the schema dispute without guessing? 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"}...
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 prove version compatibility. What content check will find the missing evidence to close these four gaps? Decision: route History: [{"action_family": "tool_use", "result": "weak", "step": 0}, {"action_family": "tool_use", "result": "weak", "step": 1}, {"action_family": "tool_use", "result": "weak", "step": 2},...
The operation produces a reliable result for the relevant content under current constraints.. 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. ...
Combining two open quality checks with stale assessments, how do I locate the exact token defining the validation rule? Decision: route History: [{"action_family": "tool_use", "result": "weak", "step": 0}, {"action_family": "tool_use", "result": "weak", "step": 1}, {"action_family": "tool_use", "result": "weak", "step"...
The operation produces a reliable result for an exact name, code, or token under current constraints.. Capabilities: exact pattern search. Accepts: text, code. Returns: evidence candidates. Evidence role: candidate discovery. Prerequisites: query available. Constraints: textual source required. Side effects: read. Argu...
Given the modality constraints and read-only safety requirements, what is the next operation to retrieve resource metadata for lifecycle filtering? Decision: route History: [{"action_family": "tool_use", "result": "weak", "step": 0}, {"action_family": "tool_use", "result": "weak", "step": 1}] Plan: {"active": false, "o...
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...
Having exhausted prior checks on telemetry sources, what is the remaining step to inspect field structures and types for trace validation? Decision: route History: [{"action_family": "tool_use", "result": "weak", "step": 0}, {"action_family": "tool_use", "result": "weak", "step": 1}, {"action_family": "tool_use", "resu...
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...
To distinguish between matching records and finalizing selection in a data quality task, what precise next move avoids the tempting alternative of early termination? Decision: route History: [{"action_family": "tool_use", "result": "weak", "step": 0}, {"action_family": "tool_use", "result": "weak", "step": 1}, {"action...
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...
How can we verify the result by inspecting sections and structural landmarks from the selected PDF source to confirm the next workflow step? Decision: route Plan: {"active": false, "operation": "absence_verification"} Agent State: {"phase": "source_discovery", "question_length_band": "long", "state_name": "source_disco...
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...
With one step left and access control rules disputed, prioritize retrieving relevant page ranges over other operations to resolve the immediate requirement. 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 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 (...
Following an ambiguous attempt to identify the latest value, how do we recover by reading the selected Excel resource to clarify the next workflow step? Decision: route History: [{"action_family": "tool_use", "result": "weak", "step": 0}, {"action_family": "tool_use", "result": "weak", "step": 1}, {"action_family": "to...
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...
From the available code catalog, what operation inspects symbols and definitions to resolve the disputed workflow step without naming specific identifiers? Decision: route History: [{"action_family": "tool_use", "result": "weak", "step": 0}] Plan: {"active": false, "operation": "lookup_semantic"} Agent State: {"phase":...
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...
Inspect the candidate result from the SQLite source to clarify telemetry trace requirements and resolve the current dispute. Decision: route History: [{"action_family": "tool_use", "result": "weak", "step": 0}] Plan: {"active": false, "operation": "lookup_semantic"} Agent State: {"phase": "inspection", "question_length...
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...
Given the schema ambiguity in the CSV, what is the best next step to gather the missing surrounding context needed for field definitions? Decision: route History: [{"action_family": "tool_use", "result": "weak", "step": 0}, {"action_family": "tool_use", "result": "weak", "step": 1}] Plan: {"active": false, "operation":...
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...
With multiple sources inspected, how can I determine if the version compatibility data aligns or conflicts across them without performing a new search? Decision: route Plan: {"active": false, "operation": "lookup_semantic"} Agent State: {"phase": "governance", "question_length_band": "long", "state_name": "insufficient...
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...
Since the source inventory is unknown and evidence is only snippets, how do I ensure the required data transformation requirements are fully tracked? Decision: route History: [{"action_family": "tool_use", "result": "weak", "step": 0}, {"action_family": "tool_use", "result": "weak", "step": 1}] Plan: {"active": false, ...
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...
Considering the mixed modalities and stale assessment, how do I verify if the current evidence is sufficient to define the next workflow step despite schema ambiguity? Decision: route History: [{"action_family": "tool_use", "result": "weak", "step": 0}, {"action_family": "tool_use", "result": "weak", "step": 1}] Plan: ...
The operation produces a reliable result for 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...
With fresh evidence and complete requirements, how should I safely finalize the result regarding event delivery while respecting read-only side-effect constraints? Decision: route Plan: {"active": true, "operation": "enumerate_sources"} Agent State: {"phase": "planning", "question_length_band": "long", "state_name": "i...
This candidate supports controlled inspection of 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 assessment ...
Having checked four items but with stale assessments, what is the optimal next move to find the exact identifier for event retry logic in mixed formats? Decision: route History: [{"action_family": "tool_use", "result": "weak", "step": 0}] Plan: {"active": true, "operation": "lookup_semantic"} Agent State: {"phase": "re...
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...
Should I list all available resources again or directly inspect the Excel file's structure to compare failure recovery settings, given no obstacles remain? Decision: route History: [{"action_family": "tool_use", "result": "weak", "step": 0}, {"action_family": "tool_use", "result": "weak", "step": 1}] Plan: {"active": 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 I verify the version compatibility claim using the relevant content from mixed sources, given the requirement progress is currently disputed? Decision: route History: [{"action_family": "tool_use", "result": "weak", "step": 0}] Plan: {"active": false, "operation": "join"} Agent State: {"phase": "governance", "q...
This operation handles the relevant content while preserving the current task state.. Capabilities: search content. Accepts: text, pdf. Returns: evidence candidates. Evidence role: candidate discovery. Prerequisites: query available. Constraints: indexed sources required. Side effects: read. Arguments: limit (integer o...
I have one step left and need to validate an exact token. Should I use a precise pattern match or finalize the selection now? Decision: route History: [{"action_family": "tool_use", "result": "weak", "step": 0}] Plan: {"active": false, "operation": "lookup_exact"} Agent State: {"phase": "inspection", "question_length_b...
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...
My last retrieval failed due to schema ambiguity. Should I query metadata filters to clarify resource details before retrying? Decision: route History: [{"action_family": "tool_use", "result": "weak", "step": 0}] Plan: {"active": true, "operation": "contradiction_resolution"} Agent State: {"phase": "retrieval", "questi...
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...
Given the partial inventory, which operation best reveals the field structure and types of the selected spreadsheet? Decision: route Plan: {"active": false, "operation": "enumerate_records"} Agent State: {"phase": "governance", "question_length_band": "long", "state_name": "insufficient"} Source State: {"available_moda...
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...
Next, should I search for matching records in the structured source to clarify the retry behavior? Decision: route History: [{"action_family": "tool_use", "result": "weak", "step": 0}] Plan: {"active": false, "operation": "lookup_semantic"} Agent State: {"phase": "synthesis", "question_length_band": "short", "state_nam...
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 ...
Do I need to inspect the document's structural landmarks to join these evidence sets before finalizing? 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": "t...
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 do I identify the specific page ranges containing the telemetry trace requirements without using obvious search verbs? Decision: route Plan: {"active": false, "operation": "lookup_semantic"} Agent State: {"phase": "synthesis", "question_length_band": "long", "state_name": "contradiction"} Source State: {"available_...
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 (...
To ensure version compatibility, what is the best way to extract the full content of the selected resource? 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 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...
Combining the code modality and broad query, how should I enumerate symbols to define field 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}, {"actio...
The operation produces a reliable result for symbols and definitions under current constraints.. Capabilities: inspect code structure. Accepts: code. Returns: content, code structure. Evidence role: evidence inspection. Prerequisites: source selected. Constraints: code source required. Side effects: read. Arguments: de...
Given the contradictory evidence topology and known source inventory, which read-only operation should I perform next to inspect a specific candidate result without triggering any state changes? Decision: route History: [{"action_family": "tool_use", "result": "weak", "step": 0}, {"action_family": "tool_use", "result":...
Apply this capability when the next decision depends on 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...
I have checked initial snippets but lack surrounding context for event delivery details. Since no other searches remain, how do I expand the current evidence to capture the missing retry behavior context? Decision: route Plan: {"active": true, "operation": "enumerate_records"} Agent State: {"phase": "retrieval", "quest...
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...
Should I compare the eight inspected evidence items to detect conflicts, or is it safer to just assess if the data is sufficient? Distinguish the move that validates quality constraints against the tempting alternative. Decision: route History: [{"action_family": "tool_use", "result": "weak", "step": 0}, {"action_famil...
Use this candidate when the task requires agreement or conflict between results.. Capabilities: compare evidence. Accepts: evidence. Returns: evidence comparison. Evidence role: evidence synthesis. Prerequisites: evidence inspected. Constraints: multiple evidence required. Side effects: none. Arguments: comparison (str...
How can I verify that my version compatibility findings fully cover all tracked requirements using the available CSV evidence, given that the previous assessment is now stale? Decision: route History: [{"action_family": "tool_use", "result": "weak", "step": 0}, {"action_family": "tool_use", "result": "weak", "step": 1}...
This operation handles task requirements and coverage while preserving the current task state.. Capabilities: update requirements. Accepts: evidence, agent state. Returns: governance state. Evidence role: governance update. Prerequisites: evidence inspected. Constraints: tracked requirements required. Side effects: loc...
With only one step remaining and no fresh assessment, should I prioritize validating if the two observed evidence items are sufficient, or should I inspect the CSV schema first to ensure quality constraints are met? Decision: route History: [{"action_family": "tool_use", "result": "weak", "step": 0}, {"action_family": ...
The operation produces a reliable result for whether available information is sufficient under current constraints.. Capabilities: assess evidence, validate sufficiency. Accepts: evidence, governance state. Returns: assessment. Evidence role: governance assessment. Prerequisites: requirements updated. Constraints: cano...
After an ambiguous attempt at joining code resources, I need to finalize the selection. Given the fresh assessment and complete requirements, what is the correct terminal operation to lock in the next action? Decision: route History: [{"action_family": "tool_use", "result": "weak", "step": 0}, {"action_family": "tool_u...
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 ...
With contradictory evidence and zero steps remaining, what planning operation should guide the best next information-gathering step for document analysis, considering the split context obstacle and partial source inventory? Decision: route History: [{"action_family": "tool_use", "result": "weak", "step": 0}, {"action_f...
Apply this capability when the next decision depends on the best next information-gathering step.. Capabilities: plan retrieval. Accepts: agent state, text. Returns: plan. Evidence role: none. Prerequisites: objective available. Constraints: none. Side effects: local state write. Arguments: objective (string required),...
What is the next read-only action to list the available resources for telemetry trace requirements, ensuring no state is modified while addressing the disputed requirement progress? Decision: route History: [{"action_family": "tool_use", "result": "weak", "step": 0}, {"action_family": "tool_use", "result": "weak", "ste...
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 have a single evidence snippet from a structured source. What operation should I run to find the relevant content needed for consistency checks? Decision: route History: [{"action_family": "tool_use", "result": "weak", "step": 0}] Plan: {"active": false, "operation": "lookup_exact"} Agent State: {"phase": "synthesis"...
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...
I need to identify a specific token within the codebase but cannot use obvious search verbs. How do I proceed with the available resources? Decision: route History: [{"action_family": "tool_use", "result": "weak", "step": 0}, {"action_family": "tool_use", "result": "weak", "step": 1}, {"action_family": "tool_use", "res...
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...
My goal is to ensure version compatibility across documents. Which action allows me to filter resources by their metadata attributes effectively? Decision: route History: [{"action_family": "tool_use", "result": "weak", "step": 0}, {"action_family": "tool_use", "result": "weak", "step": 1}] Plan: {"active": true, "oper...
The operation produces a reliable result for resource metadata and filters under current constraints.. Capabilities: search metadata, filter sources. Accepts: metadata. Returns: source list. Evidence role: source discovery. Prerequisites: none. Constraints: metadata catalog required. Side effects: read. Arguments: filt...
With mixed sources and disputed requirements for telemetry, I need to understand the structure. What is the right move to inspect fields and types? Decision: route Plan: {"active": true, "operation": "latest_value_selection"} Agent State: {"phase": "retrieval", "question_length_band": "long", "state_name": "retrieval"}...
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...
I must validate data quality constraints while ensuring no side effects occur. What is the safest operation to match records in a mixed-modality environment? 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 matching records.. Capabilities: search structured records. Accepts: csv, excel, sqlite. Returns: evidence candidates. Evidence role: candidate discovery. Prerequisites: schema known. Constraints: structured source required. Side effects: read. Arguments: limit (i...
I have checked multiple passages but still lack clarity on the document layout. What next step reveals the sections and structural landmarks? Decision: route History: [{"action_family": "tool_use", "result": "weak", "step": 0}, {"action_family": "tool_use", "result": "weak", "step": 1}, {"action_family": "tool_use", "r...
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 ...
Should I broaden my search or focus on specific page ranges to resolve this contradiction? Distinguish the precise next move from a general content scan. Decision: route Plan: {"active": false, "operation": "contradiction_resolution"} Agent State: {"phase": "inspection", "question_length_band": "long", "state_name": "p...
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...
How can I verify that the selected resource actually contains the field definitions I need for schema management? Decision: route Plan: {"active": true, "operation": "latest_value_selection"} Agent State: {"phase": "planning", "question_length_band": "long", "state_name": "initial"} Source State: {"available_modalities...
This operation handles the selected resource while preserving the current task state.. Capabilities: read content. Accepts: text, code. Returns: content. Evidence role: evidence inspection. Prerequisites: source selected. Constraints: local source required. Side effects: read. Arguments: offset (integer optional), reso...
With only four steps left and version noise blocking progress, which read-only operation should I prioritize to map symbols and definitions for compatibility? 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 symbols and definitions from the available resources.. Capabilities: inspect code structure. Accepts: code. Returns: content, code structure. Evidence role: evidence inspection. Prerequisites: source selected. Constraints: code source required. Side effects: read. Arguments: depth (int...
My previous lookup was ambiguous due to paraphrasing. To recover and identify the correct workflow step from the Excel data, what is the best next move? Decision: route History: [{"action_family": "tool_use", "result": "weak", "step": 0}, {"action_family": "tool_use", "result": "weak", "step": 1}] Plan: {"active": fals...
The operation produces a reliable result for a candidate result under current constraints.. Capabilities: inspect evidence. Accepts: evidence candidates. Returns: evidence. Evidence role: evidence inspection. Prerequisites: evidence candidate selected. Constraints: candidate evidence required. Side effects: read. Argum...
I need to validate data quality constraints but lack full context. Which catalog-oriented operation should I use to expand the surrounding information without writing state? Decision: route History: [{"action_family": "tool_use", "result": "weak", "step": 0}, {"action_family": "tool_use", "result": "weak", "step": 1}, ...
Apply this capability when the next decision depends on 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...
For failure recovery, I need to check if multiple sources agree. What is the next concise action to compare these results? Decision: route Plan: {"active": false, "operation": "latest_value_selection"} Agent State: {"phase": "governance", "question_length_band": "long", "state_name": "insufficient"} Source State: {"ava...
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...
Directly, what operation should I perform to update requirement coverage for this consistency check task given the current evidence? Decision: route History: [{"action_family": "tool_use", "result": "weak", "step": 0}] Plan: {"active": false, "operation": "compare"} Agent State: {"phase": "governance", "question_length...
This operation handles task requirements and coverage while preserving the current task state.. Capabilities: update requirements, track coverage. Accepts: evidence, agent state. Returns: governance state. Evidence role: governance update. Prerequisites: evidence inspected. Constraints: tracked requirements required. S...
Is the current CSV-based evidence enough to confirm source consistency, or do I need another retrieval step before concluding? Decision: route History: [{"action_family": "tool_use", "result": "weak", "step": 0}] Plan: {"active": true, "operation": "lookup_exact"} Agent State: {"phase": "retrieval", "question_length_ba...
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...
Goal: ensure cross-source consistency. With fresh assessment available, what is the logical terminal action to lock in the selected result? Decision: route Plan: {"active": true, "operation": "join"} Agent State: {"phase": "retrieval", "question_length_band": "long", "state_name": "retrieval"} Source State: {"available...
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...
Combining the data processing goal with zero observed evidence and stale assessments, what is the optimal next step to find relevant PDF sources? Decision: route History: [{"action_family": "tool_use", "result": "weak", "step": 0}, {"action_family": "tool_use", "result": "weak", "step": 1}] Plan: {"active": true, "oper...
The operation produces a reliable result for the best next information-gathering step under current constraints.. Capabilities: plan retrieval. Accepts: agent state, text. Returns: plan. Evidence role: none. Prerequisites: objective available. Constraints: none. Side effects: local state write. Arguments: objective (st...
Given the need to resolve a contradiction between two mixed-modality sources and a partial inventory, what is the safest next read-only operation to clarify available resources before proceeding? Decision: route History: [{"action_family": "tool_use", "result": "weak", "step": 0}, {"action_family": "tool_use", "result"...
Apply this capability when the next decision depends on the 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)
Since no evidence has been inspected yet and the source inventory is unknown for this SQLite-based schema task, what specific content inspection step should occur next to address field definitions? Decision: route Plan: {"active": true, "operation": "lookup_semantic"} Agent State: {"phase": "planning", "question_length...
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...
For an Excel-based versioning check involving acronyms, should I perform an exact pattern search for the specific token or expand the context of existing candidates to verify compatibility? Decision: route History: [{"action_family": "tool_use", "result": "weak", "step": 0}, {"action_family": "tool_use", "result": "wea...
This operation handles an exact name, code, or token while preserving the current task state.. Capabilities: exact pattern search, identifier search. Accepts: text, code. Returns: evidence candidates. Evidence role: candidate discovery. Prerequisites: query available. Constraints: textual source required. Side effects:...
With stale assessments and two unresolved requirements in document analysis, how can I verify the result by checking resource metadata filters against the current governance state? Decision: route Plan: {"active": false, "operation": "lookup_semantic"} Agent State: {"phase": "governance", "question_length_band": "long"...
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...
Under a limited step budget with contradictory event handling evidence, what is the priority action to inspect structured schemas to determine field types before finalizing any selection? Decision: route History: [{"action_family": "tool_use", "result": "weak", "step": 0}] Plan: {"active": false, "operation": "enumerat...
Invoke the candidate to determine fields, types, and structure from the available resources.. Capabilities: inspect structured schema. Accepts: csv, excel, sqlite. Returns: schema. Evidence role: structure discovery. Prerequisites: source selected. Constraints: structured source required. Side effects: read. Arguments:...
After an ambiguous attempt to match records in a CSV source for event delivery, what recovery-oriented step should I take to re-inspect the structured schema and resolve the near-duplicate issue? Decision: route History: [{"action_family": "tool_use", "result": "weak", "step": 0}] Plan: {"active": false, "operation": "...
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...
With an unknown catalog and mixed modalities for observability tasks, what resource-oriented operation should I initiate to identify sections and structural landmarks without assuming specific tools? Decision: route Plan: {"active": false, "operation": "contradiction_resolution"} Agent State: {"phase": "terminal_readin...
Apply this capability when the next decision depends on sections and structural landmarks.. Capabilities: inspect document structure. Accepts: pdf. Returns: document structure. Evidence role: structure discovery. Prerequisites: source selected. Constraints: pdf source required. Side effects: read. Arguments: landmark (...
What is the concise next action to retrieve the relevant pages or ranges from the PDF source to satisfy the remaining four observability requirements related to trace data? Decision: route History: [{"action_family": "tool_use", "result": "weak", "step": 0}, {"action_family": "tool_use", "result": "weak", "step": 1}, {...
Use this candidate when the task requires the relevant pages or ranges.. Capabilities: search document pages, retrieve passages. Accepts: pdf. Returns: evidence candidates. Evidence role: candidate discovery. Prerequisites: source selected. Constraints: pdf source required. Side effects: read. Arguments: page range (ar...
I have selected a local resource. What operation should I run next to access its technical content? Decision: route History: [{"action_family": "tool_use", "result": "weak", "step": 0}, {"action_family": "tool_use", "result": "weak", "step": 1}] Plan: {"active": true, "operation": "compare"} Agent State: {"phase": "ret...
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...
How can I determine which symbols and definitions are present in the code to check 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...
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...
My goal is to verify version compatibility. What action lets me examine a specific candidate result from the Excel data? 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...
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...
Since the snippets lack surrounding context and I need consistency checks across sources, what step fills those gaps? 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...
Apply this capability when the next decision depends on missing surrounding context.. Capabilities: expand context, resolve split context. Accepts: evidence candidates, evidence. Returns: evidence. Evidence role: context expansion. Prerequisites: evidence candidate selected. Constraints: incomplete context required. Si...
I need to compare results without modifying state. Which read-only operation ensures agreement or conflict detection between them? Decision: route Plan: {"active": false, "operation": "compare"} Agent State: {"phase": "source_discovery", "question_length_band": "long", "state_name": "source_discovery"} Source State: {"...
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...
Having checked the full context but with stale assessments, how do I update the tracking of task requirements and coverage? Decision: route History: [{"action_family": "tool_use", "result": "weak", "step": 0}] Plan: {"active": true, "operation": "absence_verification"} Agent State: {"phase": "planning", "question_lengt...
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...
Instead of searching more text, how do I determine if the gathered information is sufficient to meet the technical instruction? Decision: route History: [{"action_family": "tool_use", "result": "weak", "step": 0}] Plan: {"active": false, "operation": "absence_verification"} 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...
How can I verify that the contradictory PDF evidence supports the final decision 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":...
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...
With only eight steps left, what is the highest-priority action to locate telemetry and trace requirements from the available structured data? Decision: route Plan: {"active": true, "operation": "join"} Agent State: {"phase": "retrieval", "question_length_band": "long", "state_name": "retrieval"} Source State: {"availa...
Invoke the candidate to determine the best next information-gathering step from the available resources.. Capabilities: plan retrieval. Accepts: agent state, text. Returns: plan. Evidence role: none. Prerequisites: objective available. Constraints: none. Side effects: local state write. Arguments: objective (string req...
After my previous attempts failed to yield a clear answer, how can I recover by identifying what resources are actually available for this document analysis? Decision: route History: [{"action_family": "tool_use", "result": "weak", "step": 0}, {"action_family": "tool_use", "result": "weak", "step": 1}, {"action_family"...
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)
I need to verify resource limits and lifecycle details. What catalog-based operation would help me find the relevant content without naming specific tools? Decision: route History: [{"action_family": "tool_use", "result": "weak", "step": 0}, {"action_family": "tool_use", "result": "weak", "step": 1}] Plan: {"active": f...
Apply this capability when the next decision depends on the relevant content.. Capabilities: search content. Accepts: text, pdf. Returns: evidence candidates. Evidence role: candidate discovery. Prerequisites: query available. Constraints: indexed sources required. Side effects: read. Arguments: limit (integer optional...
What is the next action needed to locate an exact identifier related to resource limits within the current set of documents? Decision: route History: [{"action_family": "tool_use", "result": "weak", "step": 0}, {"action_family": "tool_use", "result": "weak", "step": 1}] Plan: {"active": false, "operation": "absence_ver...
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 ...