Financial operations / Runtime controls

A timed-out refund should not become two refunds.

A payment provider receives a refund request, but the acknowledgement is lost. The agent wants to repeat it.

Slack#refund-ops
Channel
Payments assistant

The $18.42 refund timed out. Should I send it again?

DriftGate

The timeout does not tell us whether money moved.

Original result unknownScope review
Operation
RF-1048
Provider reply
Missing
Next
Reconcile before retry
Morgan · Payments lead

Check the provider using that same operation identity.

DriftGate

The provider confirmed the first refund.

Original refund foundRecorded
Provider
Confirmed original effect
Second request
None sent
Payments assistant

I’ll report one confirmed refund. There is no second refund attempt.

Ready
THE CONTROL

Make the boundary explicit.

Keep the original logical operation identity and durable attempt. Record the unknown outcome and reconcile through a provider query or supported idempotency mechanism before considering another effect.

An unresolved operation does not automatically create a second refund. The original outcome remains attributable when evidence arrives.

CONNECTED CAPABILITIES

The controls behind the workflow.

Explore the capabilities that compose around this task, rather than treating each step as a separate product.

BUILD WITH INTENTION

Your next agent.
A better starting point.

EXPLORE DRIFTGATE

Find your starting point.

Search DriftGate

Quick jumps