Concurrent change compatibility: six recorded examples
The downloads contain six original inputs, their expected labels and one recorded API observation per input revision. Disagreements stay visible.
Give a planned change and another task's complete usage contract. Check whether that dependency still works, regardless of whether the edits touch the same file.
Compatibility is relative to a consumer. Adding a field may be compatible with a tolerant reader and incompatible with a reader that rejects unknown fields. Include that behavior in the input.
The result concerns one dependency under stated assumptions. It does not establish that the changes compile together, that tests pass, or that a text merge is conflict-free.
This original interface-review exercise adapts the compatibility question in Medula, linked by the source post. The example changes and labels are ours. It neither locks files nor tests or merges code.

Use the sample to understand the rule, then test your own input for concurrent change compatibility.

Give a planned change and another task's complete usage contract.

Open the decision rules and keep the intended distinction between Compatible, Conflict, Unclear. 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 Unclear before using a result. The label is a decision about the supplied information, not an executed action.
| Original input | Observed label | Leading probability |
|---|---|---|
| Optional argument | Compatible | 95.0% |
| New required argument | Conflict | 100% |
| Renamed field | Conflict | 99.0% |
| Independent same-file edits | Compatible | 100% |
| Unknown alias | Unclear | 99.0% |
| Additive response | Compatible | 100% |
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.
Yes. A schema change can break a query in another file. The relevant connection is the interface or data contract, not the file path.
No. It covers the supplied consumer only. Build, integration, permissions and other dependent code still need their usual checks.
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.