validation_check
Executes one frozen validation component against existing run evidence, enabling rechecks of old runs without rerunning simulations and returning a durable operation ID.
Instructions
Execute one frozen component on existing evidence. environment/numerics/outputs use run_id and collected data_root='runs/<run_id>'; a terminal failed job can supply complete usable components. Matching old runs can be rechecked under revised criteria without another simulation. A component with checker_id additionally uses analysis_operation_id from analysis_submit on that run's collected data; program version, qualified fixtures and raw data are verified. Static/analysis checks use project files. Returns a durable operation id; missing evidence affects this component only.
Tool call template
Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"task_id": "<task_id>",
"revision": "<revision>",
"plan_id": "<plan_id>",
"component_id": "<component_id>",
"op_id": "<op_id>"
},
"name": "validation_check"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| op_id | Yes | ||
| token | No | ||
| run_id | No | ||
| plan_id | Yes | ||
| task_id | Yes | ||
| revision | Yes | ||
| data_root | No | ||
| component_id | Yes | ||
| analysis_operation_id | No |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| result | Yes |