Jev batch review feedback kind

Identify what a reviewer note asks you to fix

Paste a reviewer note to distinguish unsupported facts, an unmet instruction and a failed test. Inspect mixed repair requests without assuming the fix has succeeded.

What repair does this review note call for?Live API
Try an example

Original input for the Source support outcome. Edit the evidence to send a new request.

Source: API-collected workflow inspiration; original demonstration below

Source and example scope

This is an original synthetic demonstration adapted from the cited workflow discussion. It does not reproduce the source application or verify its performance, adoption or security claims.

Classify the named repair focus.

Decision rules and labels
Source supportInstruction adherenceTest failureMixed repairNeed evidence
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

Repair focus and repair readiness are different.

This classifier reads what a reviewer asks to fix. In the cost example, latency measurements do not support the quoted cost claim, so the requested repair concerns source support. In the offline-file example, the reviewer names a missing requirement. A later review must check whether the repair was completed.

The source-file example tests a shared word with a different meaning. The note describes executable behavior, so its repair focus is Test failure rather than Source support. Mixed repair keeps equally important requests visible.

The source describes returning specific criticism to workers in a batch loop. This original classifier does not run a swarm, repair a file or validate the workers’ final output.

This is an original synthetic demonstration adapted from the cited workflow discussion. It does not reproduce the source application or verify its performance, adoption or security claims.

Illustration of one spreadsheet row producing two separate classification results
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 review feedback type.

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

    Add the information to check

    Paste a reviewer note to distinguish unsupported facts, an unmet instruction and a failed test.

  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 Source support, Instruction adherence, Test failure, Mixed repair, Need evidence. 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 Need evidence 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
Unsupported claimSource support100%
Ignored requirementInstruction adherence100%
Executable failureTest failure100%
Two repair focusesMixed repair100%
Source word in a testTest failure100%
No feedback noteNeed evidence100%

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

Source and example scope

Compare each saved result with its authored expectation. A disagreement remains in the fixture review; the call is not repeated to obtain a preferred label.

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.

Runnable offline example

Run one sample, then inspect the local packet

View the code example
Single-request replay
npm install @typesafe-ai/sdk@0.6.0
# Set TYPESAFE_API_KEY privately in your shell.
node run-choice-sample.mjs samples.json case-1
python preview_choice_workflow.py samples.json saved-api-results.json
Scope of this demo

Where this decision fits

Useful scope

  • Organizing batch feedback by repair focus
  • Separating evidence, instruction and executable-check problems
  • Replaying the exact synthetic requests and inspecting their distributions

Outside this demonstration

  • Assuming a classified note is actionable or fixed
  • Hiding one repair request in a mixed note
  • Treating six fixture expectations as measured production accuracy
Example FAQ

Questions about batch review feedback kind.

The rubric explains the decision; the application owns the next step.

Does Test failure identify the root cause?

No. It labels the problem named in the note. Diagnosis requires the actual command, output, code and surrounding evidence.

How is this different from feedback readiness?

Repair focus describes the kind of issue. Readiness asks whether the note supplies a usable target and evidence for the worker to act on.

Does the leading probability measure production accuracy?

No. It is the model distribution for this one request. The six examples are functional checks with authored expectations, not a representative benchmark. Inspect disagreements and evaluate your own examples before using the label.

What happens when the API fails?

The window shows an error and supplies no fresh judgment. The downloadable runner sends one request without retries. Need evidence is a valid outcome about incomplete input; it does not stand in for a network or provider failure.

Try your own batch review feedback kind input

Edit the evidence above or use the Playground to test another bounded question.