Definition
Cancellation propagation carries a stop signal from a parent request to dependent work. Each participating task must observe the signal and cooperate. A cancelled request does not prove that an external business operation was reversed or never completed.
Why It Matters
- An agent may continue checking suppliers after a merchant abandons the draft it was preparing.
- A Commerce Intelligence OS needs to distinguish work that has stopped from business effects that still require reconciliation.
How It Works
- Define the workflow lifetime and which child tasks belong to it. Keep independently required work, such as durable outcome reconciliation, under a separate lifecycle.
- Pass cancellation context through supported downstream calls and check it during long-running local processing. Release resources when stopping.
- Record completed, cancelled, and unknown outcomes separately. If an external write may have succeeded, query authoritative state before issuing a replacement operation.
- Test cancellation during lookup, immediately before a write, and after a remote commit. Treat reversal as a separate business action with its own policy and audit trail.
Ecommerce Example
Context: Illustrative example: a merchant closes an agent-assisted sourcing draft while three supplier availability queries are running.
Recommended move: The parent signals cancellation to those queries. A reservation that may already have completed is recorded for reconciliation rather than assumed absent.
Why it matters: This proposed workflow limits unnecessary work while preserving outcome evidence; it does not claim that iKawn currently deploys a particular transport.
iKawn Framework
Scope
The iKawn framework assigns dependent tasks to a clear request lifecycle.
Signal
Carry the stop condition through cooperating services.
Reconcile
Resolve uncertain commercial effects against authoritative records.
Explain
Show the merchant which work stopped and which outcome remains pending.
Concise Summary
Propagate cancellation to dependent work and verify uncertain side effects separately. Stopping a request is not a transactional rollback.