Separate update time from fix time
Synthetic T-241 promises an investigation update at 14:00. The actual update goes at 14:05, five minutes late. It explains that the cause is not yet verified and sets the next update for 16:00 under the fixture’s agreed plan. This new checkpoint does not erase the missed one or promise repair by 16:00. A later verified repair can end the investigation with its actual result.
| Record | Promised / actual | Meaning | State |
|---|---|---|---|
| Update U-1 | 14:00 / 14:05 | Investigation update | Delivered 5 minutes late |
| Update U-2 | 16:00 / not yet delivered | Next update only | Pending |
| Repair R-1 | Completion time unknown | Technical outcome | No invented deadline |
Replan without rewriting the earlier promise
- Compare promised and actual update
- Record the missed interval
- Set an evidenced next checkpoint
- Keep repair state separate
If there is no verified repair estimate, communicate that uncertainty instead of turning the update time into an estimate.
Does U-2 prove R-1 will finish by 16:00?
Show the worked answer
No. U-2 is an update commitment. R-1 still has unknown completion timing; U-1 remains five minutes late.
Retain missed updates when recording a new checkpoint. Keep the next communication time distinct from any evidenced repair estimate.