Concurrent session ownership: six recorded examples
The downloads contain six original inputs, their expected labels and one recorded API observation per input revision. Disagreements stay visible.
Describe overlapping tasks, session identities and the client contract. Compare a shared mutable session with separate instances or reuse that is fully serialized.
A session factory can be shared while the sessions it creates remain separate. Conversely, two variable names can still refer to one mutable session. The input makes object identity explicit.
Serialization is only established when it covers all relevant operations and users. A lock around construction alone says little about concurrent queries or transaction state later.
The linked linter has a specific shared-async-session question. This text review does not open a database, change transaction boundaries or verify a driver's undocumented behavior.
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 concurrent session ownership.

Describe overlapping tasks, session identities and the client contract.

Open the decision rules and keep the intended distinction between Shared session, Separate sessions, Serialized, 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 |
|---|---|---|
| Shared instance in gather | Shared session | 99.0% |
| Session created per task | Separate sessions | 94.0% |
| Sequential reuse | Serialized | 98.0% |
| Whole-operation lock | Serialized | 89.0% |
| Different variable names | Review | 97.0% |
| Partial lock | Shared session | 66.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. A factory can create distinct sessions for each task. The example follows the actual session instances.
Only the supplied complete locking contract can show serialization. Partial locking or unknown users leaves the ownership question unresolved.
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.