Jev website feedback change type

Classify website feedback by the requested change

Read a feedback note to distinguish wording, visual and interaction changes. Preserve equally requested mixed edits before planning the work; the result does not identify a project owner.

What kind of website edit is requested?Live API
Try an example

Original input for the Copy edit outcome. Edit the evidence to send a new request.

Source: Background discussion on X

Source and example scope

These fictional inputs and decision rules were written for this page. The linked X discussion provides background; the technical implementation follows TypeSafe's Choice contract.

Classify the edit explicitly requested.

Decision rules and labels
Copy editVisual editBehavior editMixed editNeed 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

A client note needs an edit scope before a task.

Brighter appears in the proposed headline, but the client requests wording only. The classifier follows the requested edit rather than interpreting an adjective as a design instruction.

Mixed edit keeps equal layout and validation work together for review. Splitting that note into implementation tasks is a separate application step that needs the project and relevant files.

The source describes an email-to-issue workflow. This adaptation classifies a note’s edit type; it does not create a Linear issue, edit a site or open a pull request.

These fictional inputs and decision rules were written for this page. The linked X discussion provides background; the technical implementation follows TypeSafe's Choice contract.

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 website feedback types.

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

    Add the information to check

    Read a feedback note to distinguish wording, visual and interaction changes.

  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 Copy edit, Visual edit, Behavior edit, Mixed edit, 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
Button wordingCopy edit100%
More spacingVisual edit100%
New filter behaviorBehavior edit100%
Layout plus behaviorMixed edit100%
Visual words in copyCopy edit100%
No requested changeNeed 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

  • Reviewing client notes before making implementation tasks
  • Separating copy requests from visual and interaction changes
  • Replaying the exact synthetic requests and inspecting their distributions

Outside this demonstration

  • Guessing a project from an absent screenshot
  • Editing a website from an ambiguous note
  • Treating six fixture expectations as measured production accuracy
Example FAQ

Questions about website feedback change type.

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

Does this select the destination project?

No. It classifies the requested edit. Project assignment needs the client, project context and ownership evidence.

Can a visual edit require code changes?

Yes. Visual describes the requested outcome, not the file type. A CSS or component edit can still be Visual edit when interaction behavior stays unchanged.

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 website feedback change type input

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