Real integration attempts: where does the contract break?

[atikakernel]

Use this thread to report attempts to place Dataoad around a real or sandboxed side-effecting action.

We are specifically looking for cases where the contract is difficult or impossible to implement honestly—not feature wishlists.

Please include, when possible:

• the action type, such as payment, email, ticket, refund, or infrastructure change;
• the provider's idempotency and identity guarantees;
• when the mutation becomes externally committed;
• how verification observes the intended effect;
• what remains uncertain after timeout, cancellation, or process loss;
• whether you could run the bundled harness and where onboarding failed.

Sanitize every example. Do not include secrets, personal data, account identifiers, or production payloads. A failed installation or a workflow that cannot produce trustworthy verification evidence is useful feedback too.