The request
{
"name": "wever_commitment-slippage-check",
"arguments": {
"as_of": "2026-11-18",
"commitments": [
{
"id": "c1",
"commitment": "Send Dana the revised Q1 forecast",
"promisee": "Dana",
"started_at": "2026-11-10",
"due": "2026-11-20",
"progress": 90
},
{
"id": "c2",
"commitment": "Send Lee the vendor shortlist",
"promisee": "Lee",
"started_at": "2026-11-08",
"due": "2026-11-24",
"progress": 25
},
{
"id": "c3",
"commitment": "Send Sam the board pack figures",
"promisee": "Sam",
"started_at": "2026-11-02",
"due": "2026-11-14",
"progress": 70,
"flagged_at": "2026-11-16",
"measured_against": "date_passed"
}
]
}
}What the report returns
Verdict: slippage_unflagged.
| Finding, slip unflagged | 1 commitment is projected to finish late with no warning to the promisee: c2 (25% done, due 2026-11-24, projected 2026-12-18). |
|---|
| Finding, warned after due | 1 warning reached the promisee only after the date had passed: c3 (due 2026-11-14, warned 2026-11-16). |
|---|
| Fix, slip unflagged | Warn the promisee now about every commitment projected to finish late, with the new expected date and what would bring it back. |
|---|
| Fix, warned after due | Warn the promisee while the work remaining still projects late, not once the date has passed. |
|---|
Commitments are slipping without timely warning: slip unflagged and warned after due.
Ten days into the vendor shortlist, the agent is 25% done, a pace that finishes on 18 December against a 24 November date, and Lee has heard nothing. The board pack figures were due on 14 November and Sam heard about the delay two days later, once the date had passed. The revised forecast is 90% done with two days to go and reads as on track. A warning to Lee today, with the new expected date and what would bring the shortlist back, still leaves six days to act.