Jev concurrent change compatibility

Review whether concurrent changes preserve a caller's contract

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.

concurrent change compatibilityLive API
Try an example

The documented default preserves the existing call.

Source: API-collected workflow inspiration; original demonstration below

Source and example scope

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.

Compare the proposed change with the other task’s complete usage contract: Compatible if that usage still works unchanged; Conflict if a stated requirement is broken; Unclear if a relevant contract, default, alias or migration behavior is missing.

Decision rules and labels
CompatibleConflictUnclear
A real response from the Jev API

Edit any input to explore a different decision. No request is sent until you run it.

Your next decision

Not run yet

Choose an example or write your own input, then run it to see the ranked choices.

Results are not stored by this site. Your submitted text is processed by the API provider.

The decision

What the decision checks

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.

Illustration of checking a code change and reviewing a flagged line
Illustration of the decision flow.
How it works

Try the example in four steps

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

  1. Illustration of adding the text or evidence for a decision

    Add the information to check

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

  2. Illustration of defining a question and its allowed choices

    Confirm the question and labels

    Open the decision rules and keep the intended distinction between Compatible, Conflict, Unclear. Edit the choices only when testing your own rule.

  3. Illustration of sending one input and comparing the returned choices

    Run the decision

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

  4. Illustration of reviewing a result and an uncertain item before using it

    Review the next step

    Review Unclear before using a result. The label is a decision about the supplied information, not an executed action.

Our API test

Recorded API observations

Recorded API observations
Original inputObserved labelLeading probability
Optional argumentCompatible95.0%
New required argumentConflict100%
Renamed fieldConflict99.0%
Independent same-file editsCompatible100%
Unknown aliasUnclear99.0%
Additive responseCompatible100%

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

Understand the results

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.

Using the result in your application

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.

Replay options

Inspect saved outputs or request a new decision

View the code example
Two independent commands
# 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.
Scope of this demo

Where this decision fits

Useful scope

  • Reviewing concurrent agent plans
  • Checking interface changes against named consumers
  • Identifying missing compatibility guarantees

Outside this demonstration

  • Locking or merging files
  • Running integration tests
  • Proving all unknown consumers remain compatible
Example FAQ

Using this example

The input contract and these limits define what the result means.

Can changes in different files conflict?

Yes. A schema change can break a query in another file. The relevant connection is the interface or data contract, not the file path.

Does Compatible mean it is safe to merge?

No. It covers the supplied consumer only. Build, integration, permissions and other dependent code still need their usual checks.

Does the leading probability measure accuracy?

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.

Will a result change an external system?

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.

Test a different input

Edit the example above to see how a changed fact affects the decision, or open the Playground for another task.