approval-invalidation
Does a change to the approved thing invalidate the approval under a materiality policy? — Compares what a human or system approved with what is about to be executed (a quote, order, plan, diff summary: any JSON) under a caller-supplied materiality policy: per-path rules exact / ignore / numeric tolerance (absolute or percent) / no-increase / no-decrease, with the longest matching path winning and a default for unlisted paths. Also covers quote revisions (approved revision number must e
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": {
"approved": "<approved>",
"current": "<current>"
},
"name": "approval-invalidation"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| asOf | No | RFC 3339 instant for the expiry check; no clock is read. | |
| policy | No | ||
| current | Yes | The version about to be executed (JSON). | |
| approved | Yes | The approved snapshot (JSON). | |
| approvedAt | No | RFC 3339 instant. | |
| currentRevision | No | ||
| validForSeconds | No | ||
| approvedRevision | No | ||
| requireSameRevision | No | Default true when either revision is given (a missing partner gives unknown): an approval for another revision does not cover this one. Send false to ignore the revisions. |