decompose_failure
Measure the numeric difference between original and corrected values: how much lies along the supplied linear rule directions (projection) and how much lies outside them (residual), with per-field contributions. Diagnostic only: it does not establish a cause, and neither record is verified. Use with a known-correct version to diff against; use analyze_anomaly when you only have the suspicious payload. Diagnostics-tier tool.
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": {
"api_key": "<api_key>",
"original_values": "<original_values>",
"corrected_values": "<corrected_values>"
},
"name": "decompose_failure"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| api_key | Yes | GeodesicAI API key (gai_...) | |
| blueprint | No | Load rules from this Blueprint instead of passing them inline | |
| original_values | Yes | Original numeric field values as {field: number} | |
| corrected_values | Yes | Corrected/expected numeric field values as {field: number} | |
| derivation_rules | No | Math rules as objects. Types: add, subtract, multiply, divide, round, copy, sum (multi-operand), items_multiply, items_sum. Each needs 'type' plus its fields; see the blueprint_guide prompt | |
| formal_constraints | No | Constraint objects. Types incl. magnitude_anchor {field,min,max}, relative_anchor {field,reference_field,ratio_min,ratio_max}, max_action_threshold {field,threshold,on_violation}, required_fields {fields}, equals, range, in_set, regex_match, items_magnitude_anchor; see the blueprint_guide prompt |