Technical reference · for existing users

Stop, cancel and late capture callbacks: inspect activeToken ownership

Stop can yield this capture's drained result; canceled tokens cannot identify a new capture

Short-speech start creates a UUID; captureCompleted accepts only the matching activeToken. Stop ends admission and drains without immediately invalidating this capture’s token. Cancel clears activeToken and cancels the pipeline. Similar UI phases/late callbacks do not establish ownership. This is in-process completion guarding, not authentication or cross-service exactly-once.

Different from foreground and queue review

Foreground checks lifecycle validity; pressure checks previews/final. Here which capture owns an asynchronous result and why stop differs from cancel matters. No capture, cancellation or callback injection ran.

Check Verified scope Manual review Not established
Start Per-capture token in completion closure Current active capture UUID grants user authority
Stop End admission/engine, drain asynchronously Actual final/error Tap means complete cancellation or success
Cancel Clear activeToken/cancel pipeline Canceled versus committed effects Remote recall
captureCompleted Compare activeToken/token first Old result is not a new capture Same text belongs to current target
Cleanup Clears token/pipeline etc. Actual completion/error All call chains duplicate-free
Preview/level Different evidence from final/token When preview was generated Late preview proves delivery
Delivery Controller/insertion guards remain Actual target/permission Capture token grants writes
Recapture New capture versus prior effects Gap/version/old attempt Automatic fill/merge/resend

Synthetic timing review

Capture A was canceled. A’s late completion arrives while activeToken no longer identifies A. It cannot be presented as new capture B or automatically handed off. If A merely stopped, its drain can still complete; record the distinction.

No race-free/zero-loss guarantee is made. Tokens are implementation association, not credentials/signatures. Prior effects retain original receipt/uncertainty review.

FAQ

Is stop the same as cancel?

No. Stop retains asynchronous draining; cancel invalidates the token/pipeline.

Can a UUID-bearing old result join a new draft?

No. Current ownership and target/permission guards still apply.

Is activeToken authentication?

No. Capture association does not grant identity or operation authority.

Does stop tapping mean final exists?

No. Inspect actual completion/error rather than button events.

Does cancellation recall prior inserted contents?

No inference follows. Inspect actual prior/local/remote effects.

Does this establish no callback races?

No device/concurrency test or recovery feature is supplied; fixed guards only.

Reading and source

Lifecycle · Queue/final · Recapture scope · Start · Privacy

Capture lifecycle/token · Pipeline stop/cancel