anchor
stringlengths
723
2.15k
positive
stringlengths
153
8.2k
Given the complete requirements and fresh assessment, which next action avoids any local state writes and only reads, while selecting from the evidence candidates? Decision: route History: [{"action_family": "tool_use", "result": "weak", "step": 0}] Plan: {"active": false, "operation": "absence_verification"} Agent Sta...
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 checked 8 evidence items but still have one unresolved requirement and haven't searched yet. What's the next step to gather information, considering the identifier variation issue? Decision: route Plan: {"active": true, "operation": "compare"} Agent State: {"phase": "retrieval", "question_length_band": "long", "s...
This candidate supports controlled inspection of the best next information-gathering step.. Capabilities: plan retrieval. Accepts: agent state, text. Returns: plan. Evidence role: none. Prerequisites: objective available. Constraints: none. Side effects: local state write. Arguments: objective (string required), priori...
Should we enumerate all sources now or first inspect the evidence we already have? We need to know the available resources for version compatibility, and only reads are allowed. Decision: route History: [{"action_family": "tool_use", "result": "weak", "step": 0}] Plan: {"active": true, "operation": "enumerate_sources"}...
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 data transformation result when the assessment is stale and there are disputed requirements? Which content should we examine to resolve contradictions? Decision: route History: [{"action_family": "tool_use", "result": "weak", "step": 0}, {"action_family": "tool_use", "result": "weak", "step": 1}, ...
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...
Given the remaining budget, what should we prioritize to verify the exact identifier while avoiding side effects? Decision: route History: [{"action_family": "tool_use", "result": "weak", "step": 0}, {"action_family": "tool_use", "result": "weak", "step": 1}] Plan: {"active": false, "operation": "absence_verification"}...
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...
After the incomplete attempt, what should we do next to recover and enumerate the sources despite 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, "operation": "enumerate_sources"}...
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...
Which resource should be inspected next to resolve the contradiction, focusing on fields and types? Decision: route Plan: {"active": true, "operation": "contradiction_resolution"} Agent State: {"phase": "retrieval", "question_length_band": "short", "state_name": "retrieval"} Source State: {"available_modalities": ["csv...
Apply this capability when the next decision depends on fields, types, and structure.. Capabilities: inspect structured schema. Accepts: csv, excel, sqlite. Returns: schema. Evidence role: structure discovery. Prerequisites: source selected. Constraints: structured source required. Side effects: read. Arguments: includ...
What should be done now to join matching records and address the unresolved field definitions? Decision: route Plan: {"active": true, "operation": "join"} Agent State: {"phase": "retrieval", "question_length_band": "short", "state_name": "retrieval"} Source State: {"available_modalities": ["excel", "metadata"], "eviden...
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 ...
What should I do next to locate the sections and structural landmarks needed for the data transformation? Decision: route History: [{"action_family": "tool_use", "result": "weak", "step": 0}, {"action_family": "tool_use", "result": "weak", "step": 1}] Plan: {"active": false, "operation": "contradiction_resolution"} Age...
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...
Could you help me figure out which pages or ranges to look at for resource limits and lifecycle details? 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_...
Invoke the candidate to determine the relevant pages or ranges from the available resources.. Capabilities: search document pages, retrieve passages. Accepts: pdf. Returns: evidence candidates. Evidence role: candidate discovery. Prerequisites: source selected. Constraints: pdf source required. Side effects: read. Argu...
I need to determine the right resource to use for managing limits and lifecycle; what should I check next? Decision: route Plan: {"active": false, "operation": "compatibility"} Agent State: {"phase": "inspection", "question_length_band": "long", "state_name": "partial_evidence"} Source State: {"available_modalities": [...
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...
What operation should I perform to verify consistency across sources regarding symbols and definitions, considering the constraint of no side effects? Decision: route History: [{"action_family": "tool_use", "result": "weak", "step": 0}, {"action_family": "tool_use", "result": "weak", "step": 1}, {"action_family": "tool...
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 and the need to enumerate records, what read-only operation should I perform next to surface a candidate result, while ensuring no side effects and using only the available code, CSV, Excel, metadata, SQLite, or text inputs? Decision: route Plan: {"active": false, "operation": "enumerat...
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...
We've only seen snippets and the schema differs between sources, but the identifier should match exactly. What next read step would join the missing surrounding context from the CSV or Excel inputs, given the validation constraints are disputed and I have one step left? Decision: route Plan: {"active": true, "operation...
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...
Instead of re-running the metadata filter, which read-only action would compare the complementary results from the multi-source inspection to reveal agreement or conflict, given the schema ambiguity and that we've already searched twice? Decision: route History: [{"action_family": "tool_use", "result": "weak", "step": ...
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 the consistency across sources by inspecting the document structure or evidence comparison, given the disputed requirements and unknown inventory, while allowing a local state write if needed, to confirm coverage of all task requirements? Decision: route History: [{"action_family": "tool_use", "result"...
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...
Given the partial context and only two steps left, should we spend the next step on checking if we have enough evidence or on something else? Decision: route History: [{"action_family": "tool_use", "result": "weak", "step": 0}] Plan: {"active": true, "operation": "lookup_semantic"} Agent State: {"phase": "retrieval", "...
Invoke the candidate to determine whether available information is sufficient from the available resources.. Capabilities: assess evidence. Accepts: evidence, governance state. Returns: assessment. Evidence role: governance assessment. Prerequisites: requirements updated. Constraints: canonical evidence set required. S...
The last attempt was ambiguous; what should we do next to resolve the near-duplicate and pick the right result? Decision: route History: [{"action_family": "tool_use", "result": "weak", "step": 0}] Plan: {"active": false, "operation": "lookup_semantic"} Agent State: {"phase": "source_discovery", "question_length_band":...
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 ...
We have many sources available; what is the best next step to gather more information within our resource limits? Decision: route Plan: {"active": true, "operation": "compare"} Agent State: {"phase": "retrieval", "question_length_band": "long", "state_name": "retrieval"} Source State: {"available_modalities": ["pdf", "...
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 resources do we have left to proceed with the next workflow step? Decision: route History: [{"action_family": "tool_use", "result": "weak", "step": 0}, {"action_family": "tool_use", "result": "weak", "step": 1}, {"action_family": "tool_use", "result": "weak", "step": 2}, {"action_family": "tool_use", "result": "we...
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)
Given the stale assessment and known sources, find the latest value from the text source despite identifier variation. Decision: route Plan: {"active": true, "operation": "latest_value_selection"} Agent State: {"phase": "retrieval", "question_length_band": "long", "state_name": "retrieval"} Source State: {"available_mo...
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...
With full context and no retrieval obstacle, identify the exact token from the Excel source for the required transformation. Decision: route History: [{"action_family": "tool_use", "result": "weak", "step": 0}, {"action_family": "tool_use", "result": "weak", "step": 1}] Plan: {"active": false, "operation": "lookup_exac...
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...
To handle event delivery and retry, enumerate all source metadata and filters from the code source given split 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": "weak", "step"...
Invoke the candidate to determine resource metadata and filters from the available resources.. Capabilities: search metadata. Accepts: metadata. Returns: source list. Evidence role: source discovery. Prerequisites: none. Constraints: metadata catalog required. Side effects: read. Arguments: filters (object required), s...
Given partial inventory and version noise, extract the schema fields and types from the Excel source for 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": "look...
The operation produces a reliable result for fields, types, and structure under current constraints.. Capabilities: inspect structured schema. Accepts: csv, excel, sqlite. Returns: schema. Evidence role: structure discovery. Prerequisites: source selected. Constraints: structured source required. Side effects: read. Ar...
Given the stale assessment and partial source inventory, which operation should I run next to enumerate all sources that match these broad records, without writing any external state? Decision: route History: [{"action_family": "tool_use", "result": "weak", "step": 0}, {"action_family": "tool_use", "result": "weak", "s...
This candidate supports controlled inspection of matching records.. Capabilities: search structured records, filter records. Accepts: csv, excel, sqlite. Returns: evidence candidates. Evidence role: candidate discovery. Prerequisites: schema known. Constraints: structured source required. Side effects: read. Arguments:...
Since I've only seen snippets and the schema is ambiguous, what should I check next to find the sections and structural landmarks needed for the next workflow step, without causing side effects? Decision: route History: [{"action_family": "tool_use", "result": "weak", "step": 0}] Plan: {"active": false, "operation": "c...
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 ...
Instead of immediately extracting all text, what precise operation should I perform to locate the relevant pages or ranges in this PDF, given the full context is already inspected? Decision: route History: [{"action_family": "tool_use", "result": "weak", "step": 0}] Plan: {"active": false, "operation": "compatibility"}...
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...
To verify the synthesized result against the selected resource, which operation should I use to fetch evidence from that resource, ensuring compatibility with the existing plan? Decision: route History: [{"action_family": "tool_use", "result": "weak", "step": 0}, {"action_family": "tool_use", "result": "weak", "step": ...
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...
Given limited steps, which operation should I prioritize to resolve contradictions in symbols and definitions for version compatibility? Decision: route Plan: {"active": false, "operation": "contradiction_resolution"} Agent State: {"phase": "governance", "question_length_band": "long", "state_name": "insufficient"} Sou...
Invoke the candidate to determine symbols and definitions from the available resources.. Capabilities: inspect code structure. Accepts: code. Returns: content, code structure. Evidence role: evidence inspection. Prerequisites: source selected. Constraints: code source required. Side effects: read. Arguments: depth (int...
My previous attempt was incomplete. What should I do next to compare candidate results for the required data transformation? 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", "...
The operation produces a reliable result for a candidate result under current constraints.. Capabilities: inspect evidence. Accepts: evidence candidates. Returns: evidence. Evidence role: evidence inspection. Prerequisites: evidence candidate selected. Constraints: candidate evidence required. Side effects: read. Argum...
I need to find missing surrounding context for event delivery and retry behavior. What catalog or resource operation should I request next? Decision: route Plan: {"active": true, "operation": "enumerate_records"} Agent State: {"phase": "retrieval", "question_length_band": "long", "state_name": "retrieval"} Source State...
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...
What next action should I take to check agreement or conflict between results on event delivery and retry behavior? Decision: route Plan: {"active": false, "operation": "lookup_semantic"} Agent State: {"phase": "governance", "question_length_band": "long", "state_name": "insufficient"} Source State: {"available_modalit...
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...
Based on the partial requirements and the eight evidence items already seen, what operation should be performed next to determine if any requirements remain uncovered? Decision: route History: [{"action_family": "tool_use", "result": "weak", "step": 0}, {"action_family": "tool_use", "result": "weak", "step": 1}, {"acti...
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...
Given the stale assessment and the multiple passages, what should be done to check whether the available information is sufficient for version compatibility? Decision: route History: [{"action_family": "tool_use", "result": "weak", "step": 0}, {"action_family": "tool_use", "result": "weak", "step": 1}] Plan: {"active":...
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...
Since the evidence is contradictory and the requirements are complete, what action should be taken to verify the absence of a needed piece of information? Decision: route History: [{"action_family": "tool_use", "result": "weak", "step": 0}, {"action_family": "tool_use", "result": "weak", "step": 1}, {"action_family": "...
Invoke the candidate to determine the selected 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...
Given the snippets-only inspection and the near-duplicate obstacle, what is the best next information-gathering step to select the latest value for the workflow? Decision: route History: [{"action_family": "tool_use", "result": "weak", "step": 0}] Plan: {"active": true, "operation": "latest_value_selection"} Agent Stat...
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...
We need to verify absence of resources before finalizing. Which read-only operation on the available resources should we perform next, considering only the evidence snippets we have? Decision: route Plan: {"active": false, "operation": "absence_verification"} Agent State: {"phase": "synthesis", "question_length_band": ...
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)
We've inspected multiple sources but hit a schema ambiguity. Given the PDFs and what we've already checked, what should we do next to find the exact content? Decision: route Plan: {"active": false, "operation": "lookup_exact"} Agent State: {"phase": "inspection", "question_length_band": "long", "state_name": "partial_e...
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...
We have partial context and a stale assessment. Instead of just searching again, what operation should we perform to compare the exact token across complementary sources? Decision: route History: [{"action_family": "tool_use", "result": "weak", "step": 0}, {"action_family": "tool_use", "result": "weak", "step": 1}] Pla...
Use this candidate when the task requires an exact name, code, or token.. Capabilities: exact pattern search. Accepts: text, code. Returns: evidence candidates. Evidence role: candidate discovery. Prerequisites: query available. Constraints: textual source required. Side effects: read. Arguments: case sensitive (boolea...
How can we verify that the technical instruction we extracted is compatible with the resource metadata? What next step should we take to confirm the evidence? Decision: route History: [{"action_family": "tool_use", "result": "weak", "step": 0}] Plan: {"active": false, "operation": "compatibility"} Agent State: {"phase"...
This operation handles resource metadata and filters while preserving the current task state.. Capabilities: search metadata. Accepts: metadata. Returns: source list. Evidence role: source discovery. Prerequisites: none. Constraints: metadata catalog required. Side effects: read. Arguments: filters (object required), s...
Given 4 steps left and one unresolved requirement, which next operation should prioritize to inspect fields, types, and structure from the known Excel source? Decision: route History: [{"action_family": "tool_use", "result": "weak", "step": 0}, {"action_family": "tool_use", "result": "weak", "step": 1}] Plan: {"active"...
The operation produces a reliable result for fields, types, and structure under current constraints.. Capabilities: inspect structured schema, discover fields. Accepts: csv, excel, sqlite. Returns: schema. Evidence role: structure discovery. Prerequisites: source selected. Constraints: structured source required. Side ...
After a failed ambiguous attempt with 4 steps left, what recovery operation should identify matching records for the required data transformation? Decision: route History: [{"action_family": "tool_use", "result": "weak", "step": 0}, {"action_family": "tool_use", "result": "weak", "step": 1}, {"action_family": "tool_use...
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 2 steps remaining, what resource should we consult to find sections and structural landmarks for the relevant technical instruction? Decision: route History: [{"action_family": "tool_use", "result": "weak", "step": 0}] Plan: {"active": false, "operation": "lookup_exact"} Agent State: {"phase": "terminal_readiness"...
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 (...
With 2 steps left, what next action should compare evidence to identify relevant pages or ranges for the data transformation? Decision: route History: [{"action_family": "tool_use", "result": "weak", "step": 0}] Plan: {"active": false, "operation": "compare"} Agent State: {"phase": "inspection", "question_length_band":...
This candidate supports controlled inspection of the relevant pages or ranges.. Capabilities: search document pages. Accepts: pdf. Returns: evidence candidates. Evidence role: candidate discovery. Prerequisites: source selected. Constraints: pdf source required. Side effects: read. Arguments: page range (array required...
Given the known SQLite source and complete requirements, which operation should I perform next to check the selected resource's limits and lifecycle, given the stale assessment and broad query? Decision: route History: [{"action_family": "tool_use", "result": "weak", "step": 0}, {"action_family": "tool_use", "result": ...
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...
I need to verify the absence of certain symbols and definitions in the technical instructions. Given the stale assessment and mixed sources, what should I do next to confirm this absence? Decision: route Plan: {"active": false, "operation": "absence_verification"} Agent State: {"phase": "synthesis", "question_length_ba...
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...
To resolve version compatibility issues, I need to enumerate candidate records from the SQLite source. What next step should I take to list these records, given the unknown inventory and schema-bound query? Decision: route History: [{"action_family": "tool_use", "result": "weak", "step": 0}, {"action_family": "tool_use...
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...
Given the CSV source and partial context, I need to verify the absence of surrounding context for version compatibility. What next step should I take, considering the disputed requirements and structural match? Decision: route History: [{"action_family": "tool_use", "result": "weak", "step": 0}] Plan: {"active": true, ...
The operation produces a reliable result for missing surrounding context under current constraints.. Capabilities: expand context. Accepts: evidence candidates, evidence. Returns: evidence. Evidence role: context expansion. Prerequisites: evidence candidate selected. Constraints: incomplete context required. Side effec...
We've inspected multiple sources and have partial requirements. Given the stale assessment and two unresolved items, what read-only operation can compare the CSV-derived evidence to check for agreement or conflict, without writing local state? Decision: route History: [{"action_family": "tool_use", "result": "weak", "s...
Apply this capability when the next decision depends on agreement or conflict between results.. Capabilities: compare evidence. Accepts: evidence. Returns: evidence comparison. Evidence role: evidence synthesis. Prerequisites: evidence inspected. Constraints: multiple evidence required. Side effects: none. Arguments: c...
We've already checked some sources but the inventory is partial. For the remaining access-rule requirements, what structural enumeration should we run next on the PDF evidence to cover all permissions, given we've done two searches already? Decision: route History: [{"action_family": "tool_use", "result": "weak", "step...
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 haven't made progress on requirements and the source inventory is unknown. Instead of just reading the CSV again, what local-state-writing inspection step would help determine if we have enough information to recover from the split-context failure? Decision: route History: [{"action_family": "tool_use", "result": "w...
This operation handles whether available information is sufficient while preserving the current task state.. Capabilities: assess evidence, validate sufficiency. Accepts: evidence, governance state. Returns: assessment. Evidence role: governance assessment. Prerequisites: requirements updated. Constraints: canonical ev...
We have complete requirements and fresh assessment, but schema ambiguity remains. To verify our synthesis across sources, what read-only enumeration of records should we do to confirm the consistency of the selected result? Decision: route History: [{"action_family": "tool_use", "result": "weak", "step": 0}] Plan: {"ac...
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 4 steps left and 2 unresolved requirements, what is the most critical next action to verify the absence of the entity across complementary sources? Decision: route History: [{"action_family": "tool_use", "result": "weak", "step": 0}] Plan: {"active": true, "operation": "absence_verification"} Agent State: {"p...
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 the ambiguous attempt, what available resources should I consult next to resolve the disputed requirement and locate the specific technical instruction in the long document? Decision: route Plan: {"active": false, "operation": "lookup_exact"} Agent State: {"phase": "governance", "question_length_band": "long", "s...
The operation produces a reliable result for the available resources under current constraints.. Capabilities: list sources. Accepts: metadata. Returns: source list. Evidence role: source discovery. Prerequisites: none. Constraints: none. Side effects: read. Arguments: filters (object optional), scope (string required)
Given the stale assessment and partial inventory, which catalog or source listing should I refresh to find the relevant content for the telemetry and trace requirements? 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 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 step to find the exact field name or token that matches the definition, given the identifier variation and complete requirements? Decision: route History: [{"action_family": "tool_use", "result": "weak", "step": 0}] Plan: {"active": true, "operation": "compatibility"} Agent State: {"phase": "planning",...
This candidate supports controlled inspection of an exact name, code, or token.. Capabilities: exact pattern search. Accepts: text, code. Returns: evidence candidates. Evidence role: candidate discovery. Prerequisites: query available. Constraints: textual source required. Side effects: read. Arguments: case sensitive ...
Given the complete telemetry requirements and partial source inventory, what resource metadata and filters should be applied next? Decision: route History: [{"action_family": "tool_use", "result": "weak", "step": 0}, {"action_family": "tool_use", "result": "weak", "step": 1}] Plan: {"active": false, "operation": "looku...
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)
Considering the disputed field definitions and multiple passages, what should be selected as the latest value for the entity? Decision: route History: [{"action_family": "tool_use", "result": "weak", "step": 0}, {"action_family": "tool_use", "result": "weak", "step": 1}] Plan: {"active": false, "operation": "latest_val...
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:...
For the required data transformation, which records match the metadata filters from the Excel source? Decision: route History: [{"action_family": "tool_use", "result": "weak", "step": 0}] Plan: {"active": false, "operation": "enumerate_records"} Agent State: {"phase": "terminal_readiness", "question_length_band": "long...
Invoke the candidate to determine matching records from the available resources.. Capabilities: search structured records. Accepts: csv, excel, sqlite. Returns: evidence candidates. Evidence role: candidate discovery. Prerequisites: schema known. Constraints: structured source required. Side effects: read. Arguments: l...
Given the complete requirements and known PDF source, what structural landmarks should be identified to resolve schema ambiguity? Decision: route Plan: {"active": false, "operation": "latest_value_selection"} Agent State: {"phase": "governance", "question_length_band": "long", "state_name": "insufficient"} Source State...
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 versioning task and that we've only seen one piece of evidence so far, what is the next step that must avoid any side effects beyond reading and local writes, to locate the exact pages or ranges that match the identifier? Decision: route History: [{"action_family": "tool_use", "result": "weak", "step": 0}] Pl...
Apply this capability when the next decision depends on the relevant pages or ranges.. Capabilities: search document pages. Accepts: pdf. Returns: evidence candidates. Evidence role: candidate discovery. Prerequisites: source selected. Constraints: pdf source required. Side effects: read. Arguments: page range (array r...
Since we've already checked the full context and found nothing after exhausting sources, but we still have several steps left, what should we do next to address the telemetry and trace requirements for the selected resource, given that the document is long and we need a broad search? Decision: route History: [{"action_...
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...
We haven't started looking yet, but we need to find the field definitions and compatibility info. Should we search for the exact schema-bound symbol or instead just browse the code structure? What's the precise next move? Decision: route Plan: {"active": false, "operation": "lookup_exact"} Agent State: {"phase": "synth...
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...
We've seen only snippets and need to verify the candidate result against the technical instruction in the PDF. How should we proceed to confirm the join operation's output, given that we have a complete requirement but one unresolved? Decision: route History: [{"action_family": "tool_use", "result": "weak", "step": 0},...
This operation handles a candidate result while preserving the current task state.. Capabilities: inspect evidence. Accepts: evidence candidates. Returns: evidence. Evidence role: evidence inspection. Prerequisites: evidence candidate selected. Constraints: candidate evidence required. Side effects: read. Arguments: cl...
With only 2 steps left, what should I prioritize to fill in the missing context around the access rules? Decision: route History: [{"action_family": "tool_use", "result": "weak", "step": 0}, {"action_family": "tool_use", "result": "weak", "step": 1}, {"action_family": "tool_use", "result": "weak", "step": 2}, {"action_...
Invoke the candidate to determine missing surrounding context from the available resources.. Capabilities: expand context. Accepts: evidence candidates, evidence. Returns: evidence. Evidence role: context expansion. Prerequisites: evidence candidate selected. Constraints: incomplete context required. Side effects: read...
The results seem inconsistent; what next action should I take to reconcile 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": 2}, {"action_family": "to...
The operation produces a reliable result for agreement or conflict between results under current constraints.. Capabilities: compare evidence. Accepts: evidence. Returns: evidence comparison. Evidence role: evidence synthesis. Prerequisites: evidence inspected. Constraints: multiple evidence required. Side effects: non...
What operation can I run to verify that all validation requirements are covered? Decision: route History: [{"action_family": "tool_use", "result": "weak", "step": 0}, {"action_family": "tool_use", "result": "weak", "step": 1}, {"action_family": "tool_use", "result": "weak", "step": 2}, {"action_family": "tool_use", "re...
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...
What should I do next to determine if the gathered info is sufficient? 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": "we...
This candidate supports controlled inspection of whether available information is sufficient.. Capabilities: assess evidence. Accepts: evidence, governance state. Returns: assessment. Evidence role: governance assessment. Prerequisites: requirements updated. Constraints: canonical evidence set required. Side effects: l...
We have a complete set of requirements and fresh assessments. Given the broad query and partial inventory, what should we do next to compare the field definitions from the available sources? Decision: route History: [{"action_family": "tool_use", "result": "weak", "step": 0}, {"action_family": "tool_use", "result": "we...
Use this candidate when the task requires the selected result or next action.. Capabilities: finalize selection. Accepts: assessment, governance state. Returns: terminal result. Evidence role: terminal decision. Prerequisites: requirements complete. Constraints: fresh sufficient assessment required. Side effects: local...
Given the split context and the need to compare lexical matches, what is the best next information-gathering step to identify the next workflow step? Decision: route History: [{"action_family": "tool_use", "result": "weak", "step": 0}] Plan: {"active": true, "operation": "compare"} Agent State: {"phase": "retrieval", "...
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...
Since our assessments are stale and we have partial context, what resources are available to resolve the schema ambiguity and support the planning phase? Decision: route History: [{"action_family": "tool_use", "result": "weak", "step": 0}, {"action_family": "tool_use", "result": "weak", "step": 1}, {"action_family": "t...
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)
Given the disputed requirements and the need to enumerate records with metadata filtering, what content should we retrieve to validate quality constraints? Decision: route History: [{"action_family": "tool_use", "result": "weak", "step": 0}] Plan: {"active": false, "operation": "enumerate_records"} Agent State: {"phase...
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...
Find the exact identifier for the entity involved in the failure, but only read from sources and do not modify any state. Decision: route History: [{"action_family": "tool_use", "result": "weak", "step": 0}, {"action_family": "tool_use", "result": "weak", "step": 1}, {"action_family": "tool_use", "result": "weak", "ste...
Apply this capability when the next decision depends on an exact name, code, or token.. Capabilities: exact pattern search. Accepts: text, code. Returns: evidence candidates. Evidence role: candidate discovery. Prerequisites: query available. Constraints: textual source required. Side effects: read. Arguments: case sen...
We've already checked the main source and its complementary source. Now retrieve the metadata for the resource with the remaining filter, and update the local state with what you find. Decision: route Plan: {"active": true, "operation": "lookup_exact"} Agent State: {"phase": "retrieval", "question_length_band": "long",...
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...
Instead of summarizing the content, extract the schema of the Excel source: list the fields, types, and structure. Do not read from any other modality. 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 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...
How can I verify that the matching records from the schema lookup are correct? Show me the evidence candidates that support the match. Decision: route History: [{"action_family": "tool_use", "result": "weak", "step": 0}, {"action_family": "tool_use", "result": "weak", "step": 1}, {"action_family": "tool_use", "result":...
This operation handles 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...
Given the remaining step budget, which structural sections should be prioritized next? Decision: route Plan: {"active": true, "operation": "lookup_exact"} Agent State: {"phase": "planning", "question_length_band": "short", "state_name": "initial"} Source State: {"available_modalities": ["text", "pdf", "csv", "excel", "...
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...
After the ambiguous attempt, which page ranges should be re-examined to resolve the access rules? Decision: route History: [{"action_family": "tool_use", "result": "weak", "step": 0}, {"action_family": "tool_use", "result": "weak", "step": 1}] Plan: {"active": false, "operation": "latest_value_selection"} Agent State: ...
The operation produces a reliable result for the relevant pages or ranges under current constraints.. Capabilities: search document pages. Accepts: pdf. Returns: evidence candidates. Evidence role: candidate discovery. Prerequisites: source selected. Constraints: pdf source required. Side effects: read. Arguments: page...
For the selected resource, which validation constraints should be applied next? Decision: route History: [{"action_family": "tool_use", "result": "weak", "step": 0}] Plan: {"active": true, "operation": "lookup_exact"} Agent State: {"phase": "planning", "question_length_band": "short", "state_name": "initial"} Source St...
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...
What symbols and definitions should be retrieved next for telemetry tracing? Decision: route History: [{"action_family": "tool_use", "result": "weak", "step": 0}, {"action_family": "tool_use", "result": "weak", "step": 1}, {"action_family": "tool_use", "result": "weak", "step": 2}, {"action_family": "tool_use", "result...
This candidate supports controlled inspection of symbols and definitions.. Capabilities: inspect code structure. Accepts: code. Returns: content, code structure. Evidence role: evidence inspection. Prerequisites: source selected. Constraints: code source required. Side effects: read. Arguments: depth (integer required)...
Given the stale assessment and the identifier variation, which candidate result should we inspect 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_f...
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)...
What is the missing surrounding context for the required data transformation? 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", "resul...
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...
How do the results from complementary sources agree or conflict regarding version compatibility? Decision: route Plan: {"active": false, "operation": "join"} Agent State: {"phase": "source_discovery", "question_length_band": "short", "state_name": "source_discovery"} Source State: {"available_modalities": ["sqlite", "m...
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...
Considering the never-assessed state and schema ambiguity, what task requirements are covered for 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": "source_discovery", ...
The operation produces a reliable result for task requirements and coverage under current constraints.. Capabilities: update requirements. Accepts: evidence, agent state. Returns: governance state. Evidence role: governance update. Prerequisites: evidence inspected. Constraints: tracked requirements required. Side effe...
Given the inspected sources and fresh assessment, is the available evidence sufficient to proceed, or should we search for a source that matches the exact identifier? Decision: route History: [{"action_family": "tool_use", "result": "weak", "step": 0}, {"action_family": "tool_use", "result": "weak", "step": 1}, {"actio...
Apply this capability when the next decision depends on whether available information is sufficient.. Capabilities: assess evidence. Accepts: evidence, governance state. Returns: assessment. Evidence role: governance assessment. Prerequisites: requirements updated. Constraints: canonical evidence set required. Side eff...
We have already checked two complementary sources and the assessment is fresh. What should we do next to compare the access rules, given we have no remaining steps? Decision: route History: [{"action_family": "tool_use", "result": "weak", "step": 0}, {"action_family": "tool_use", "result": "weak", "step": 1}] Plan: {"a...
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...
The assessment is stale and we have not inspected any evidence. Should we re-run the semantic search to enumerate all relevant sources, or is it better to inspect the existing candidates first? Decision: route History: [{"action_family": "tool_use", "result": "weak", "step": 0}] Plan: {"active": true, "operation": "enu...
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...
We have only seen snippets and no full evidence, and the assessment is missing. How can we verify the consistency across sources using the available resources, given the near-duplicate obstacle? Decision: route History: [{"action_family": "tool_use", "result": "weak", "step": 0}, {"action_family": "tool_use", "result":...
Invoke the candidate to determine the available resources from 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...
Given only two steps left, which candidate content best matches the field definitions and compatibility focus? Decision: route Plan: {"active": false, "operation": "lookup_semantic"} Agent State: {"phase": "inspection", "question_length_band": "long", "state_name": "partial_evidence"} Source State: {"available_modaliti...
Invoke the candidate to determine the relevant content from the available resources.. Capabilities: search content. Accepts: text, pdf. Returns: evidence candidates. Evidence role: candidate discovery. Prerequisites: query available. Constraints: indexed sources required. Side effects: read. Arguments: limit (integer o...
After the failed attempts, what should I retrieve next to recover the exact name or token for the schema? 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"...
The operation produces a reliable result for an exact name, code, or token under current constraints.. Capabilities: exact pattern search. Accepts: text, code. Returns: evidence candidates. Evidence role: candidate discovery. Prerequisites: query available. Constraints: textual source required. Side effects: read. Argu...
Which available resource metadata and filters should I inspect to resolve the contradiction about limits and lifecycle? Decision: route Plan: {"active": true, "operation": "contradiction_resolution"} Agent State: {"phase": "retrieval", "question_length_band": "long", "state_name": "retrieval"} Source State: {"available...
Apply this capability when the next decision depends on resource metadata and filters.. Capabilities: search metadata. Accepts: metadata. Returns: source list. Evidence role: source discovery. Prerequisites: none. Constraints: metadata catalog required. Side effects: read. Arguments: filters (object required), sort (st...
What next action should I take to determine the exact fields, types, and structure for event delivery and retry behavior? Decision: route History: [{"action_family": "tool_use", "result": "weak", "step": 0}, {"action_family": "tool_use", "result": "weak", "step": 1}] Plan: {"active": false, "operation": "join"} Agent S...
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 contradictory evidence from the SQLite source, what operation should resolve the near-duplicate matching records 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...
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...
Based on the current synthesis phase and schema ambiguity, what should we do to enumerate the sections and structural landmarks across the mixed sources? Decision: route History: [{"action_family": "tool_use", "result": "weak", "step": 0}] Plan: {"active": false, "operation": "enumerate_records"} Agent State: {"phase":...
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...
To locate the relevant pages or ranges for the technical instruction, what action should we take given the partial context and unknown inventory? Decision: route History: [{"action_family": "tool_use", "result": "weak", "step": 0}, {"action_family": "tool_use", "result": "weak", "step": 1}] Plan: {"active": false, "ope...
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 (...
Considering the partial source inventory and the required data transformation, what operation should we perform on the selected resource to resolve the contradiction? Decision: route History: [{"action_family": "tool_use", "result": "weak", "step": 0}] Plan: {"active": false, "operation": "contradiction_resolution"} Ag...
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...
Given stale assessments and partial source inventory, what next operation enumerates sources for entity-bound symbols and definitions, with read-only side effects and no state writes? Decision: route Plan: {"active": false, "operation": "enumerate_sources"} Agent State: {"phase": "terminal_readiness", "question_length_...
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...
After one prior search and only snippet inspection, what operation performs an exact lookup for the entity-bound candidate result across multiple passages, using semantic match, without writing state? Decision: route History: [{"action_family": "tool_use", "result": "weak", "step": 0}] Plan: {"active": false, "operatio...
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...
In planning with disputed requirements, what operation joins telemetry and trace requirements by exact identifier, using PDF sources, to fill missing surrounding context, and does not write state? Decision: route History: [{"action_family": "tool_use", "result": "weak", "step": 0}] Plan: {"active": true, "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...
After two prior searches and multi-source inspection, what operation performs a semantic lookup for schema-bound version compatibility, comparing results across Excel sources, without side effects? Decision: route History: [{"action_family": "tool_use", "result": "weak", "step": 0}, {"action_family": "tool_use", "resul...
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...