Skip to main content
Two agents, two remotes that can be asked. Stripe can list refunds by payment; Kubernetes can be read for a deployment’s state. A reconcile hook per action turns a lost reply into a question the remote answers, and the record moves only the way the answer points.

The policy

runnable

The code

runnable file=main.py

What the agent sees

Two lost replies, two different answers from two remotes, no human in either, and no guess in either: the hook that could not have answered would have returned "unknown" and left the record where it was.

The receipt

runnable
Each reconciliation is a RECONCILIATION_STARTED and RECONCILIATION_RESOLVED pair with the answer, so the log says the record moved because Stripe was asked, not because someone assumed.

When an AMBIGUOUS appears

With eager reconciliation it appears and is resolved in the same call. It stays only when the hook answers "unknown" or raises, which is the right outcome when the remote itself cannot be reached: then a person resolves it, and the hook’s failure is in the events.

Next