Settle unknown and overdue calls
What It Does
Investigation asks what the provider did with an uncertain execution instead of repeating its operation. The same scheduled pass detects work that has become overdue or lost. Exhausted uncertainty becomes a person’s task, except that final non-sensitive not-found results can fail automatically.
The Flow
When Something Fails
The next pass revisits due work; backlog and silence alarms expose delay. Due investigations can remain waiting. Count a failed lookup as inconclusive. The provider’s outcome remains uncertain. A status comparison loses harmlessly to another settlement. The saved outcome remains the winner’s; provider lookups can still repeat. Log failed mail delivery. The attention record exists even if no email arrives. A later pass repeats a failed timeout write. The old in-flight state can remain until recovery. Refuse an execution outside the attention state. An incorrect recorded result is not automatically corrected. A competing outcome emits no duplicate event. Event delivery can still wait on its separate routing workflow.
Open Design Questions
No declared reconciler mutex establishes exclusion between runs. Investigation uses the current account pin and active deployment, and archive expiry remains undecided.