Transaction effect order: six recorded examples
The downloads contain six original inputs, their expected labels and one recorded API observation per input revision. Disagreements stay visible.
Describe the transaction, commit and actual dispatch path. Compare an early email or enqueue with a deferred action or transactional outbox, preserving unknown helper behavior.
A database rollback cannot recall an email already sent or a message already delivered to another service. The relevant question is when the external effect occurs, not when a helper with a reassuring name was called.
Writing an outbox row is database work. Its dispatch is a separate step. The input must establish that the dispatcher only consumes committed rows before the Deferred label is justified.
The source linter includes a side-effect-in-transaction rule. This exercise checks supplied ordering; it does not implement retries, exactly-once delivery or a complete outbox system.
This is an independently authored text demonstration inspired by the linked X discussion. Its rules and synthetic inputs are ours. It does not reproduce the author’s application, verify reported outcomes, or perform an external action.

Use the sample to understand the rule, then test your own input for transaction effect order.

Describe the transaction, commit and actual dispatch path.

Open the decision rules and keep the intended distinction between Before commit, Deferred, No external effect, Review. Edit the choices only when testing your own rule.

Use a sample first, then try your own input. Compare the selected label with the other returned probabilities.

Review Review before using a result. The label is a decision about the supplied information, not an executed action.
| Original input | Observed label | Leading probability |
|---|---|---|
| Email inside the transaction | Before commit | 98.0% |
| After-commit callback | Deferred | 97.0% |
| Transactional outbox | Deferred | 99.0% |
| Database-only work | No external effect | 97.0% |
| Unknown enqueue helper | Review | 69.0% |
| Broker enqueue before commit | Before commit | 98.0% |
These are six original synthetic inputs, tested once per request revision. The percentage is the leading option probability, not measured accuracy. Authored expectations and any disagreements remain in the downloadable evidence. 6 of 6 results matched the authored fixture expectations.Verified
The downloads contain six original inputs, their expected labels and one recorded API observation per input revision. Disagreements stay visible.
The single-request SDK runner uses your private TYPESAFE_API_KEY. The offline consumer reads saved observations, checks request hashes and prints a pending output. It does not call the model or change any external system.
# Offline: inspect the downloaded saved observations. No API key is needed.
python preview_choice_workflow.py samples.json saved-api-results.json
# Optional live request: install the SDK and set TYPESAFE_API_KEY privately.
npm install @typesafe-ai/sdk@0.6.0
node run-choice-sample.mjs samples.json case-1
# The live response prints to the terminal; it does not update saved-api-results.json.The input contract and these limits define what the result means.
No. Delivery can still fail or repeat. This label only describes the supplied order relative to successful commit.
A row in the same transaction is still database state. An immediate call to an external broker has already crossed the commit boundary.
It describes the distribution over the supplied choices for this request. These six synthetic examples are functional tests with authored expectations, not a production accuracy benchmark.
No. The demo displays a label and distribution. The downloadable consumer produces a pending preview packet. Application code and a separate authorization policy would control any real action.
Edit the example above to see how a changed fact affects the decision, or open the Playground for another task.