anchor
stringlengths
723
2.15k
positive
stringlengths
153
8.2k
Given stale assessments and partial evidence with identifier variations, what next operation should I perform to resolve the unresolved requirement without side effects? Decision: route History: [{"action_family": "tool_use", "result": "weak", "step": 0}, {"action_family": "tool_use", "result": "weak", "step": 1}, {"ac...
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...
I've already checked some sources but haven't seen the latest values. What should I do next to reconcile the contradictory evidence? Decision: route History: [{"action_family": "tool_use", "result": "weak", "step": 0}, {"action_family": "tool_use", "result": "weak", "step": 1}] Plan: {"active": false, "operation": "lat...
This candidate supports controlled inspection of a candidate result.. Capabilities: inspect evidence. Accepts: evidence candidates. Returns: evidence. Evidence role: evidence inspection. Prerequisites: evidence candidate selected. Constraints: candidate evidence required. Side effects: read. Arguments: claim (string op...
I need to find more context around the near-duplicate records. Should I enumerate all records or focus on a specific one? 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...
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...
How can I verify whether the candidate results agree or conflict, given that the assessment is fresh but the requirement is disputed? Decision: route Plan: {"active": true, "operation": "lookup_exact"} Agent State: {"phase": "planning", "question_length_band": "long", "state_name": "initial"} Source State: {"available_...
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...
Given 8 steps left and disputed requirements, which next action best covers task requirements? Decision: route Plan: {"active": false, "operation": "lookup_exact"} Agent State: {"phase": "synthesis", "question_length_band": "short", "state_name": "contradiction"} Source State: {"available_modalities": ["pdf", "metadata...
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...
After an incomplete attempt with 2 steps left, is the available information sufficient for the next move? Decision: route History: [{"action_family": "tool_use", "result": "weak", "step": 0}] Plan: {"active": false, "operation": "latest_value_selection"} Agent State: {"phase": "source_discovery", "question_length_band"...
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...
Based on the catalog, which resource should we select next for telemetry requirements? Decision: route Plan: {"active": false, "operation": "compare"} Agent State: {"phase": "source_discovery", "question_length_band": "short", "state_name": "source_discovery"} Source State: {"available_modalities": ["excel", "metadata"...
Apply this capability when the next decision depends on the selected result or next action.. Capabilities: finalize selection. Accepts: assessment, governance state. Returns: terminal result. Evidence role: terminal decision. Prerequisites: requirements complete. Constraints: fresh sufficient assessment required. Side ...
What is the best next step to gather information on access rules? Decision: route History: [{"action_family": "tool_use", "result": "weak", "step": 0}, {"action_family": "tool_use", "result": "weak", "step": 1}, {"action_family": "tool_use", "result": "weak", "step": 2}, {"action_family": "tool_use", "result": "weak", ...
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...
List all resources that define access rules and permissions. Decision: route History: [{"action_family": "tool_use", "result": "weak", "step": 0}, {"action_family": "tool_use", "result": "weak", "step": 1}, {"action_family": "tool_use", "result": "weak", "step": 2}, {"action_family": "tool_use", "result": "weak", "step...
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)
What content is relevant for failure handling and recovery? Decision: route History: [{"action_family": "tool_use", "result": "weak", "step": 0}, {"action_family": "tool_use", "result": "weak", "step": 1}, {"action_family": "tool_use", "result": "weak", "step": 2}, {"action_family": "tool_use", "result": "weak", "step"...
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...
Find the exact name, code, or token for field definitions and 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_family": "tool_use", "result...
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...
Given the current evidence, what metadata and filters apply to version compatibility? Decision: route History: [{"action_family": "tool_use", "result": "weak", "step": 0}] Plan: {"active": false, "operation": "lookup_semantic"} Agent State: {"phase": "terminal_readiness", "question_length_band": "short", "state_name": ...
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...
The assessment is stale and we need to resolve a contradiction. We've only seen snippets, and the source is an Excel file. What should we do next, considering we must not write anything and should avoid a read-only operation? Decision: route History: [{"action_family": "tool_use", "result": "weak", "step": 0}, {"action...
Apply this capability when the next decision depends on fields, types, and structure.. Capabilities: inspect structured schema. Accepts: csv, excel, sqlite. Returns: schema. Evidence role: structure discovery. Prerequisites: source selected. Constraints: structured source required. Side effects: read. Arguments: includ...
We've checked four sources already but haven't found the exact entity. The next source is CSV. What should we do next to locate the matching record, given we have limited steps left? Decision: route History: [{"action_family": "tool_use", "result": "weak", "step": 0}, {"action_family": "tool_use", "result": "weak", "st...
This candidate supports controlled inspection of matching records.. Capabilities: search structured records. Accepts: csv, excel, sqlite. Returns: evidence candidates. Evidence role: candidate discovery. Prerequisites: schema known. Constraints: structured source required. Side effects: read. Arguments: limit (integer ...
We have no evidence yet and the source is mixed. Should we extract the document structure to find sections, or would it be better to search for evidence first? We have limited steps and need a plan. Decision: route Plan: {"active": false, "operation": "lookup_semantic"} Agent State: {"phase": "terminal_readiness", "que...
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...
We've inspected multiple sources but haven't found the latest value. The source is a PDF. What should we do to verify the result by checking the relevant pages or ranges? Decision: route History: [{"action_family": "tool_use", "result": "weak", "step": 0}, {"action_family": "tool_use", "result": "weak", "step": 1}, {"a...
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...
Given one step left and exact identifier, which resource should I inspect to resolve the acronym? Decision: route History: [{"action_family": "tool_use", "result": "weak", "step": 0}] Plan: {"active": false, "operation": "lookup_exact"} Agent State: {"phase": "inspection", "question_length_band": "short", "state_name":...
Invoke the candidate to determine the selected resource from the available resources.. Capabilities: read content. Accepts: text, code. Returns: content. Evidence role: evidence inspection. Prerequisites: source selected. Constraints: local source required. Side effects: read. Arguments: offset (integer optional), reso...
After a disputed attempt, which schema-bound source should I query to verify absence and recover? Decision: route History: [{"action_family": "tool_use", "result": "weak", "step": 0}, {"action_family": "tool_use", "result": "weak", "step": 1}] Plan: {"active": false, "operation": "absence_verification"} Agent State: {"...
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...
From the inspected multi-source evidence, which candidate result should I select as the latest value? Decision: route History: [{"action_family": "tool_use", "result": "weak", "step": 0}] Plan: {"active": false, "operation": "latest_value_selection"} Agent State: {"phase": "governance", "question_length_band": "long", ...
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...
To enumerate sources despite schema ambiguity, which next action should I take for missing 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"} Agent State: {"p...
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...
Given the multiple sources already inspected, what is the next step to compare the results for agreement or conflict? Decision: route History: [{"action_family": "tool_use", "result": "weak", "step": 0}] Plan: {"active": false, "operation": "enumerate_sources"} Agent State: {"phase": "inspection", "question_length_band...
This operation handles agreement or conflict between results while preserving the current task state.. Capabilities: compare evidence, detect contradictions. Accepts: evidence. Returns: evidence comparison. Evidence role: evidence synthesis. Prerequisites: evidence inspected. Constraints: multiple evidence required. Si...
What should we do next to verify that all task requirements are covered and fields are compatible? Decision: route Plan: {"active": false, "operation": "absence_verification"} Agent State: {"phase": "governance", "question_length_band": "short", "state_name": "insufficient"} Source State: {"available_modalities": ["sql...
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...
How can we determine if the available information is sufficient for validation and quality constraints? Decision: route History: [{"action_family": "tool_use", "result": "weak", "step": 0}] Plan: {"active": false, "operation": "lookup_exact"} Agent State: {"phase": "source_discovery", "question_length_band": "long", "s...
Invoke the candidate to determine whether available information is sufficient from the available resources.. Capabilities: assess evidence. Accepts: evidence, governance state. Returns: assessment. Evidence role: governance assessment. Prerequisites: requirements updated. Constraints: canonical evidence set required. S...
Considering the complementary sources and version compatibility, what should be the next action to select the appropriate result? Decision: route History: [{"action_family": "tool_use", "result": "weak", "step": 0}] Plan: {"active": false, "operation": "lookup_semantic"} Agent State: {"phase": "inspection", "question_l...
The operation produces a reliable result for the selected result or next action under current constraints.. Capabilities: finalize selection. Accepts: assessment, governance state. Returns: terminal result. Evidence role: terminal decision. Prerequisites: requirements complete. Constraints: fresh sufficient assessment ...
Given the stale assessment and broad query, what next step should I take to gather evidence without causing side effects? 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 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),...
We've checked snippets but not full evidence; what resource should we inspect next to resolve the disputed requirement? 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 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)
Should I extract the relevant content from the PDF, or would it be better to search for other documents first? Decision: route Plan: {"active": false, "operation": "latest_value_selection"} Agent State: {"phase": "terminal_readiness", "question_length_band": "long", "state_name": "fresh_sufficient"} Source State: {"ava...
This operation handles the relevant content while preserving the current task state.. 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. Argument...
How can I verify the exact identifier across sources using read-only operations? Decision: route History: [{"action_family": "tool_use", "result": "weak", "step": 0}] Plan: {"active": false, "operation": "latest_value_selection"} Agent State: {"phase": "inspection", "question_length_band": "short", "state_name": "parti...
This operation handles an exact name, code, or token while preserving the current task state.. Capabilities: exact pattern search. Accepts: text, code. Returns: evidence candidates. Evidence role: candidate discovery. Prerequisites: query available. Constraints: textual source required. Side effects: read. Arguments: c...
Given one step left, prioritize the next action that resolves the two unresolved requirements by selecting the latest value, using resource metadata and filters to handle identifier variation. Decision: route Plan: {"active": false, "operation": "latest_value_selection"} Agent State: {"phase": "synthesis", "question_le...
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...
After an incomplete attempt, what should we do next to resolve the contradiction? We need to inspect fields, types, and structure, and avoid side effects while handling near-duplicate entries. Decision: route History: [{"action_family": "tool_use", "result": "weak", "step": 0}, {"action_family": "tool_use", "result": "...
The operation produces a reliable result for fields, types, and structure under current constraints.. Capabilities: inspect structured schema. Accepts: csv, excel, sqlite. Returns: schema. Evidence role: structure discovery. Prerequisites: source selected. Constraints: structured source required. Side effects: read. Ar...
Given the resource catalog is known, what operation should we perform next to match records and address resource limits, without naming any tool? Decision: route Plan: {"active": false, "operation": "lookup_semantic"} Agent State: {"phase": "terminal_readiness", "question_length_band": "long", "state_name": "fresh_suff...
Apply this capability when the next decision depends on matching records.. Capabilities: search structured records. Accepts: csv, excel, sqlite. Returns: evidence candidates. Evidence role: candidate discovery. Prerequisites: schema known. Constraints: structured source required. Side effects: read. Arguments: limit (i...
What should we do next to validate data quality? Focus on identifying sections and structural landmarks in the document to compare evidence across formats. Decision: route Plan: {"active": false, "operation": "compatibility"} Agent State: {"phase": "source_discovery", "question_length_band": "long", "state_name": "sour...
This candidate supports controlled inspection of sections and structural landmarks.. Capabilities: inspect document structure. Accepts: pdf. Returns: document structure. Evidence role: structure discovery. Prerequisites: source selected. Constraints: pdf source required. Side effects: read. Arguments: landmark (string ...
Find the exact field definitions and compatibility details in the relevant pages or ranges. Decision: route History: [{"action_family": "tool_use", "result": "weak", "step": 0}] Plan: {"active": true, "operation": "lookup_exact"} Agent State: {"phase": "retrieval", "question_length_band": "short", "state_name": "retrie...
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...
Which resource should be selected for the latest version compatibility? Decision: route History: [{"action_family": "tool_use", "result": "weak", "step": 0}] Plan: {"active": false, "operation": "latest_value_selection"} Agent State: {"phase": "governance", "question_length_band": "short", "state_name": "insufficient"}...
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...
Ensure consistency across sources by aligning symbols and definitions. Decision: route Plan: {"active": false, "operation": "join"} Agent State: {"phase": "source_discovery", "question_length_band": "short", "state_name": "source_discovery"} Source State: {"available_modalities": ["text", "pdf", "csv", "excel", "sqlite...
Invoke the candidate to determine symbols and definitions from the available resources.. Capabilities: inspect code structure. Accepts: code. Returns: content, code structure. Evidence role: evidence inspection. Prerequisites: source selected. Constraints: code source required. Side effects: read. Arguments: depth (int...
Given the stale assessment and complete requirements, what is the next workflow step for the candidate result? 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}, {"a...
The operation produces a reliable result for a candidate result under current constraints.. Capabilities: inspect evidence. Accepts: evidence candidates. Returns: evidence. Evidence role: evidence inspection. Prerequisites: evidence candidate selected. Constraints: candidate evidence required. Side effects: read. Argum...
Given the partial context and exact entity lookup, which next operation should I run to obtain the missing surrounding context without modifying any external systems? Decision: route History: [{"action_family": "tool_use", "result": "weak", "step": 0}] Plan: {"active": false, "operation": "lookup_exact"} Agent 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...
After inspecting multiple sources and finding near-duplicates, what next step should I take to compare the results and resolve conflicts, without causing side effects? Decision: route History: [{"action_family": "tool_use", "result": "weak", "step": 0}, {"action_family": "tool_use", "result": "weak", "step": 1}, {"acti...
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...
Instead of directly applying the transformation, what should I do next to verify that the required data transformation is fully covered by the available evidence? Decision: route Plan: {"active": false, "operation": "latest_value_selection"} Agent State: {"phase": "governance", "question_length_band": "long", "state_na...
Use this candidate when the task requires task requirements and coverage.. Capabilities: update requirements. Accepts: evidence, agent state. Returns: governance state. Evidence role: governance update. Prerequisites: evidence inspected. Constraints: tracked requirements required. Side effects: local state write. Argum...
How can I verify that the current evidence is sufficient for failure recovery, given that some sources are complementary and I haven't checked all of them yet? Decision: route History: [{"action_family": "tool_use", "result": "weak", "step": 0}, {"action_family": "tool_use", "result": "weak", "step": 1}, {"action_famil...
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...
I have 2 steps left and 4 unresolved requirements. Given the fresh assessment and inspected complementary evidence, which near-duplicate candidate should I prioritize for comparison? Decision: route History: [{"action_family": "tool_use", "result": "weak", "step": 0}, {"action_family": "tool_use", "result": "weak", "st...
Invoke the candidate to determine the selected result or next action from the available resources.. Capabilities: finalize selection. Accepts: assessment, governance state. Returns: terminal result. Evidence role: terminal decision. Prerequisites: requirements complete. Constraints: fresh sufficient assessment required...
After a disputed attempt with stale assessment and partial source inventory, what is the best next step to join evidence from the few candidates I have? Decision: route History: [{"action_family": "tool_use", "result": "weak", "step": 0}, {"action_family": "tool_use", "result": "weak", "step": 1}] Plan: {"active": true...
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 schema ambiguity and unknown sources, which available resources should I enumerate to find the relevant technical instruction? Decision: route Plan: {"active": false, "operation": "enumerate_sources"} Agent State: {"phase": "source_discovery", "question_length_band": "long", "state_name": "source_discovery"} Sour...
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)
For consistency across sources, which evidence candidates should I enumerate given the near-duplicate issue? Decision: route History: [{"action_family": "tool_use", "result": "weak", "step": 0}] Plan: {"active": true, "operation": "enumerate_sources"} Agent State: {"phase": "retrieval", "question_length_band": "long", ...
This candidate supports controlled inspection of the relevant content.. Capabilities: search content. Accepts: text, pdf. Returns: evidence candidates. Evidence role: candidate discovery. Prerequisites: query available. Constraints: indexed sources required. Side effects: read. Arguments: limit (integer optional), quer...
Find the exact identifier for the telemetry trace requirement that conflicts with the current evidence. Decision: route History: [{"action_family": "tool_use", "result": "weak", "step": 0}] Plan: {"active": true, "operation": "contradiction_resolution"} Agent State: {"phase": "planning", "question_length_band": "long",...
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...
What metadata filters would pinpoint the validation rule in the Excel file? 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 operation handles resource metadata and filters while preserving the current task state.. Capabilities: search metadata. Accepts: metadata. Returns: source list. Evidence role: source discovery. Prerequisites: none. Constraints: metadata catalog required. Side effects: read. Arguments: filters (object required), s...
List the fields and types needed to enforce the resource limit from the SQLite database. Decision: route Plan: {"active": false, "operation": "enumerate_records"} Agent State: {"phase": "governance", "question_length_band": "short", "state_name": "insufficient"} Source State: {"available_modalities": ["sqlite", "metada...
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:...
Which records in the mixed sources match the field definition for 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_family": "tool_use", "re...
The operation produces a reliable result for matching records under current constraints.. Capabilities: search structured records. Accepts: csv, excel, sqlite. Returns: evidence candidates. Evidence role: candidate discovery. Prerequisites: schema known. Constraints: structured source required. Side effects: read. Argu...
Given the inspected multi-source evidence and complete requirements, which next operation should validate section landmarks across mixed file types without writing state? Decision: route History: [{"action_family": "tool_use", "result": "weak", "step": 0}] Plan: {"active": false, "operation": "compatibility"} Agent Sta...
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 (...
After checking two evidence items and partial requirements, what next step should locate the exact pages or ranges in the PDF for consistency checks, given near-duplicate distractors? Decision: route History: [{"action_family": "tool_use", "result": "weak", "step": 0}, {"action_family": "tool_use", "result": "weak", "s...
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...
For event handling with stale assessments and complete requirements, should we inspect the selected resource's structure for retry behavior, rather than re-reading all evidence? Decision: route History: [{"action_family": "tool_use", "result": "weak", "step": 0}, {"action_family": "tool_use", "result": "weak", "step": ...
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...
During planning with no requirements started and snippets only, what next operation should verify symbols and definitions from complementary sources for failure recovery, without side effects? Decision: route History: [{"action_family": "tool_use", "result": "weak", "step": 0}, {"action_family": "tool_use", "result": "...
This operation handles symbols and definitions while preserving the current task state.. Capabilities: inspect code structure. Accepts: code. Returns: content, code structure. Evidence role: evidence inspection. Prerequisites: source selected. Constraints: code source required. Side effects: read. Arguments: depth (int...
Given 8 steps left and disputed requirements, which candidate should I prioritize next for compatibility checking? Decision: route History: [{"action_family": "tool_use", "result": "weak", "step": 0}, {"action_family": "tool_use", "result": "weak", "step": 1}] Plan: {"active": true, "operation": "compatibility"} Agent ...
Invoke the candidate to determine a candidate result from the available resources.. Capabilities: inspect evidence. Accepts: evidence candidates. Returns: evidence. Evidence role: evidence inspection. Prerequisites: evidence candidate selected. Constraints: candidate evidence required. Side effects: read. Arguments: cl...
My previous attempt was incomplete. What surrounding context should I recover to validate the records? Decision: route Plan: {"active": false, "operation": "enumerate_records"} Agent State: {"phase": "synthesis", "question_length_band": "long", "state_name": "contradiction"} Source State: {"available_modalities": ["tex...
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...
Which available resource can help me reconcile the conflicting outputs from the inspected sources? Decision: route History: [{"action_family": "tool_use", "result": "weak", "step": 0}] Plan: {"active": false, "operation": "join"} Agent State: {"phase": "source_discovery", "question_length_band": "short", "state_name": ...
Apply this capability when the next decision depends on agreement or conflict between results.. Capabilities: compare evidence. Accepts: evidence. Returns: evidence comparison. Evidence role: evidence synthesis. Prerequisites: evidence inspected. Constraints: multiple evidence required. Side effects: none. Arguments: c...
What should I do next to ensure event delivery and retry coverage? Decision: route History: [{"action_family": "tool_use", "result": "weak", "step": 0}, {"action_family": "tool_use", "result": "weak", "step": 1}] Plan: {"active": false, "operation": "lookup_exact"} Agent State: {"phase": "source_discovery", "question_l...
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...
Do we have enough info to proceed, or should we dig deeper? Decision: route History: [{"action_family": "tool_use", "result": "weak", "step": 0}] Plan: {"active": false, "operation": "enumerate_records"} Agent State: {"phase": "source_discovery", "question_length_band": "short", "state_name": "source_discovery"} Source...
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...
What should we do next with the conflicting results? Decision: route History: [{"action_family": "tool_use", "result": "weak", "step": 0}] Plan: {"active": false, "operation": "latest_value_selection"} Agent State: {"phase": "governance", "question_length_band": "short", "state_name": "insufficient"} Source State: {"av...
This operation handles the selected result or next action while preserving the current task state.. Capabilities: finalize selection. Accepts: assessment, governance state. Returns: terminal result. Evidence role: terminal decision. Prerequisites: requirements complete. Constraints: fresh sufficient assessment required...
What's the best way to find the field definitions we need? Decision: route Plan: {"active": true, "operation": "lookup_semantic"} Agent State: {"phase": "planning", "question_length_band": "short", "state_name": "initial"} Source State: {"available_modalities": ["csv", "metadata"], "evidence_topology_observed": "none_o...
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...
What resources do we have available to handle this event delivery issue? Decision: route History: [{"action_family": "tool_use", "result": "weak", "step": 0}, {"action_family": "tool_use", "result": "weak", "step": 1}] Plan: {"active": true, "operation": "compatibility"} Agent State: {"phase": "planning", "question_len...
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)
Before we proceed, we need to locate the relevant content without altering any local state. Which read-only operation should we perform next to enumerate the records we need? 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 the relevant content.. Capabilities: search content. Accepts: text, pdf. Returns: evidence candidates. Evidence role: candidate discovery. Prerequisites: query available. Constraints: indexed sources required. Side effects: read. Arguments: limit (integer optional...
We've checked some sources but haven't found the exact token yet. What should we do next to join the evidence and get the precise name we need for version compatibility? Decision: route History: [{"action_family": "tool_use", "result": "weak", "step": 0}, {"action_family": "tool_use", "result": "weak", "step": 1}, {"ac...
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 ...
Should we now inspect the resource metadata to verify the absence, or would it be better to filter the sources first? What's the precise next move to confirm the missing entry? Decision: route History: [{"action_family": "tool_use", "result": "weak", "step": 0}, {"action_family": "tool_use", "result": "weak", "step": 1...
This operation handles resource metadata and filters while preserving the current task state.. Capabilities: search metadata, filter sources. Accepts: metadata. Returns: source list. Evidence role: source discovery. Prerequisites: none. Constraints: metadata catalog required. Side effects: read. Arguments: filters (obj...
How can we verify the result by examining the fields and structure of the evidence? What read-only operation should we perform next to enumerate the sources and confirm the schema? Decision: route History: [{"action_family": "tool_use", "result": "weak", "step": 0}, {"action_family": "tool_use", "result": "weak", "step...
This operation handles fields, types, and structure while preserving the current task state.. Capabilities: inspect structured schema. Accepts: csv, excel, sqlite. Returns: schema. Evidence role: structure discovery. Prerequisites: source selected. Constraints: structured source required. Side effects: read. Arguments:...
With only two steps left, which next action best matches records across the inspected sources? Decision: route History: [{"action_family": "tool_use", "result": "weak", "step": 0}, {"action_family": "tool_use", "result": "weak", "step": 1}] Plan: {"active": true, "operation": "enumerate_records"} Agent State: {"phase":...
Invoke the candidate to determine matching records from the available resources.. Capabilities: search structured records. Accepts: csv, excel, sqlite. Returns: evidence candidates. Evidence role: candidate discovery. Prerequisites: schema known. Constraints: structured source required. Side effects: read. Arguments: l...
The last attempt was incomplete; what should we do next to compare sections and structural landmarks? Decision: route History: [{"action_family": "tool_use", "result": "weak", "step": 0}, {"action_family": "tool_use", "result": "weak", "step": 1}] Plan: {"active": false, "operation": "compare"} Agent State: {"phase": "...
The operation produces a reliable result for sections and structural landmarks under current constraints.. Capabilities: inspect document structure. Accepts: pdf. Returns: document structure. Evidence role: structure discovery. Prerequisites: source selected. Constraints: pdf source required. Side effects: read. Argume...
Which next step will locate the relevant pages or ranges in the document? 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": ...
Apply this capability when the next decision depends on the relevant pages or ranges.. Capabilities: search document pages. Accepts: pdf. Returns: evidence candidates. Evidence role: candidate discovery. Prerequisites: source selected. Constraints: pdf source required. Side effects: read. Arguments: page range (array r...
What is the next action to enumerate sources for the selected resource? Decision: route History: [{"action_family": "tool_use", "result": "weak", "step": 0}, {"action_family": "tool_use", "result": "weak", "step": 1}] Plan: {"active": false, "operation": "enumerate_sources"} Agent State: {"phase": "synthesis", "questio...
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...
Given the two snippets and the schema, what operation should I run next to compare the definitions of the event delivery and retry symbols? Decision: route Plan: {"active": false, "operation": "compare"} Agent State: {"phase": "synthesis", "question_length_band": "long", "state_name": "contradiction"} Source State: {"a...
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...
Given the contradictory evidence and the exact identifier, what should I do next to resolve the conflict in 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": "contradict...
This operation handles a candidate result while preserving the current task state.. Capabilities: inspect evidence. Accepts: evidence candidates. Returns: evidence. Evidence role: evidence inspection. Prerequisites: evidence candidate selected. Constraints: candidate evidence required. Side effects: read. Arguments: cl...
I need to pick the latest access rule from these PDFs, but I'm missing the surrounding context. What operation should be performed next? Decision: route History: [{"action_family": "tool_use", "result": "weak", "step": 0}] Plan: {"active": false, "operation": "latest_value_selection"} Agent State: {"phase": "governance...
Invoke the candidate to determine missing surrounding context from the available resources.. Capabilities: expand context. Accepts: evidence candidates, evidence. Returns: evidence. Evidence role: context expansion. Prerequisites: evidence candidate selected. Constraints: incomplete context required. Side effects: read...
Considering the contradictory version compatibility results and the need to verify absence, what next operation should I request? Decision: route Plan: {"active": false, "operation": "absence_verification"} Agent State: {"phase": "governance", "question_length_band": "long", "state_name": "insufficient"} Source State: ...
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 stale assessments and unresolved requirements, what read-only step should I take next to ensure coverage without modifying state? Decision: route Plan: {"active": false, "operation": "contradiction_resolution"} Agent State: {"phase": "synthesis", "question_length_band": "long", "state_name": "contradiction"} Sour...
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...
I've already inspected multiple sources and have complete requirements. What should I check next to confirm sufficiency without changing local state? Decision: route History: [{"action_family": "tool_use", "result": "weak", "step": 0}] Plan: {"active": false, "operation": "absence_verification"} Agent State: {"phase": ...
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...
I have full context and fresh assessments. Should I proceed with the selected result or instead gather more evidence? 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": ...
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...
I haven't inspected any evidence yet. What should I retrieve first to verify the exact identifier, without altering state? Decision: route History: [{"action_family": "tool_use", "result": "weak", "step": 0}] Plan: {"active": true, "operation": "lookup_exact"} Agent State: {"phase": "retrieval", "question_length_band":...
This operation handles the best next information-gathering step while preserving the current task state.. Capabilities: plan retrieval. Accepts: agent state, text. Returns: plan. Evidence role: none. Prerequisites: objective available. Constraints: none. Side effects: local state write. Arguments: objective (string req...
With only 4 steps left, which available resource should I prioritize to resolve the field compatibility contradiction? Decision: route History: [{"action_family": "tool_use", "result": "weak", "step": 0}] Plan: {"active": false, "operation": "contradiction_resolution"} Agent State: {"phase": "inspection", "question_len...
Invoke the candidate to determine the available resources from the available resources.. Capabilities: list sources. Accepts: metadata. Returns: source list. Evidence role: source discovery. Prerequisites: none. Constraints: none. Side effects: read. Arguments: filters (object optional), scope (string required)
My last attempt was incomplete due to schema ambiguity; what relevant content should I recover next to settle the resource limit dispute? Decision: route History: [{"action_family": "tool_use", "result": "weak", "step": 0}] Plan: {"active": true, "operation": "latest_value_selection"} Agent State: {"phase": "planning",...
The operation produces a reliable result for the relevant content under current constraints.. Capabilities: search content. Accepts: text, pdf. Returns: evidence candidates. Evidence role: candidate discovery. Prerequisites: query available. Constraints: indexed sources required. Side effects: read. Arguments: limit (i...
I need the exact name or code for the resource whose lifecycle is disputed; which catalog entry should I check? Decision: route Plan: {"active": false, "operation": "contradiction_resolution"} Agent State: {"phase": "inspection", "question_length_band": "long", "state_name": "partial_evidence"} Source State: {"availabl...
Apply this capability when the next decision depends on an exact name, code, or token.. Capabilities: exact pattern search. Accepts: text, code. Returns: evidence candidates. Evidence role: candidate discovery. Prerequisites: query available. Constraints: textual source required. Side effects: read. Arguments: case sen...
What resource metadata and filters should I use next to find the 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": "join"} Agent State: {"phase": "...
This candidate supports controlled inspection of resource metadata and filters.. Capabilities: search metadata. Accepts: metadata. Returns: source list. Evidence role: source discovery. Prerequisites: none. Constraints: metadata catalog required. Side effects: read. Arguments: filters (object required), sort (string op...
Given the current governance state and partial inventory, what fields, types, and structure should be used to join the SQLite source with the other sources for consistency checks? Decision: route History: [{"action_family": "tool_use", "result": "weak", "step": 0}, {"action_family": "tool_use", "result": "weak", "step"...
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 should we match records across the mixed sources when the schema is ambiguous and we need to transform the data? Decision: route History: [{"action_family": "tool_use", "result": "weak", "step": 0}, {"action_family": "tool_use", "result": "weak", "step": 1}] Plan: {"active": true, "operation": "join"} Agent State: ...
This operation handles matching records while preserving the current task state.. Capabilities: search structured records. Accepts: csv, excel, sqlite. Returns: evidence candidates. Evidence role: candidate discovery. Prerequisites: schema known. Constraints: structured source required. Side effects: read. Arguments: l...
To ensure version compatibility, which sections and structural landmarks should we inspect in the mixed sources? Decision: route Plan: {"active": false, "operation": "join"} Agent State: {"phase": "inspection", "question_length_band": "long", "state_name": "partial_evidence"} Source State: {"available_modalities": ["te...
Invoke the candidate to determine sections and structural landmarks from the available resources.. Capabilities: inspect document structure. Accepts: pdf. Returns: document structure. Evidence role: structure discovery. Prerequisites: source selected. Constraints: pdf source required. Side effects: read. Arguments: lan...
Considering the unknown inventory and near-duplicate issue, which pages or ranges should we enumerate from the mixed sources for failure recovery? Decision: route History: [{"action_family": "tool_use", "result": "weak", "step": 0}, {"action_family": "tool_use", "result": "weak", "step": 1}] Plan: {"active": false, "op...
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: ...
Given the schema ambiguity in the PDF, which read-only action should I take next to resolve the exact entity mapping, without writing 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",...
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...
Since I've already checked the full context and the evidence is complementary, what structural join should I perform next on the code to reconcile the disputed definitions, given that my prior assessment is stale? Decision: route Plan: {"active": false, "operation": "join"} Agent State: {"phase": "synthesis", "question...
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 capability overlap, should I now read the candidate result to perform the join for the required transformation, rather than comparing all evidence candidates? Decision: route Plan: {"active": true, "operation": "join"} Agent State: {"phase": "retrieval", "question_length_band": "long", "state_name": "retrieva...
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 the transformation result by reading the missing surrounding context from the code, given the acronym ambiguity and partial source inventory, without writing any state? Decision: route History: [{"action_family": "tool_use", "result": "weak", "step": 0}] Plan: {"active": false, "operation": "join"} Age...
This operation handles missing surrounding context while preserving the current task state.. Capabilities: expand context. Accepts: evidence candidates, evidence. Returns: evidence. Evidence role: context expansion. Prerequisites: evidence candidate selected. Constraints: incomplete context required. Side effects: read...
With only 8 steps left and 2 unresolved requirements, prioritize comparing the contradictory evidence from the 4 inspected sources to decide if they agree or conflict. Decision: route History: [{"action_family": "tool_use", "result": "weak", "step": 0}] Plan: {"active": false, "operation": "lookup_semantic"} Agent Stat...
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...
We have just 1 step remaining and the attempt was incomplete. What should we do to recover and ensure we cover the task requirements from the snippet-only evidence? Decision: route Plan: {"active": false, "operation": "lookup_semantic"} Agent State: {"phase": "governance", "question_length_band": "long", "state_name": ...
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...
We've exhausted our sources and found nothing. Are there any other available resources we haven't checked that could provide the missing evidence? Decision: route History: [{"action_family": "tool_use", "result": "weak", "step": 0}, {"action_family": "tool_use", "result": "weak", "step": 1}, {"action_family": "tool_use...
Apply this capability when the next decision depends on 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 the evidence we need and the assessment is fresh. What should we do next to finalize the result? Decision: route History: [{"action_family": "tool_use", "result": "weak", "step": 0}, {"action_family": "tool_use", "result": "weak", "step": 1}] Plan: {"active": false, "operation": "lookup_semantic"} Agent State: ...
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...
We need to find the right data for the next step. What should we look up now? 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...
Use this candidate when the task requires the best next information-gathering step.. Capabilities: plan retrieval. Accepts: agent state, text. Returns: plan. Evidence role: none. Prerequisites: objective available. Constraints: none. Side effects: local state write. Arguments: objective (string required), priority (str...
What resources are available for defining fields and checking compatibility? Decision: route History: [{"action_family": "tool_use", "result": "weak", "step": 0}] Plan: {"active": false, "operation": "enumerate_sources"} Agent State: {"phase": "terminal_readiness", "question_length_band": "short", "state_name": "fresh_...
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)
We need to find the relevant content for the next workflow step. What should we retrieve? Decision: route Plan: {"active": false, "operation": "join"} Agent State: {"phase": "governance", "question_length_band": "short", "state_name": "insufficient"} Source State: {"available_modalities": ["code", "metadata"], "evidenc...
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. ...
For the event delivery and retry behavior, what exact name or token should we look up, given the PDF source and unknown inventory? Decision: route Plan: {"active": true, "operation": "join"} Agent State: {"phase": "planning", "question_length_band": "long", "state_name": "initial"} Source State: {"available_modalities"...
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 near-duplicate results, how do I filter by metadata to find the right one? Decision: route Plan: {"active": false, "operation": "lookup_semantic"} Agent State: {"phase": "inspection", "question_length_band": "short", "state_name": "partial_evidence"} Source State: {"available_modalities": ["code", "metadata"]...
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...
Since the assessment is stale and we have disputed progress, what fields and types should I check next? Decision: route Plan: {"active": false, "operation": "latest_value_selection"} Agent State: {"phase": "governance", "question_length_band": "long", "state_name": "insufficient"} Source State: {"available_modalities":...
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...
Instead of searching again, what exact identifier matching should I do to compare the two records? 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...
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 I verify the transformation by enumerating sources and inspecting their section structure? 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...
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...