Jev screen role classification

Classify the role of a described interface screen

Provide redacted interface labels to distinguish authentication, payment, private account content and ordinary content. The result describes the supplied metadata rather than inspecting a screen or granting access.

screen role classificationLive API
Try an example

The labels describe authentication input.

Source: API-collected workflow inspiration; original demonstration below

Source and example scope

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.

Classify supplied redacted interface labels.

Decision rules and labels
AuthenticationPaymentPrivate account contentOrdinary contentReview
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

All examples contain synthetic labels and explicitly removed values. This page does not capture a browser screen or inspect your account.

The source-linked focus app considers screen purpose and privacy. Our adaptation classifies redacted metadata; it is not a privacy filter that authorizes uploading the original screen.

A real integration must apply permissions, data minimization and deterministic redaction before a hosted request. Ordinary content is a descriptive label, not a guarantee that no sensitive text exists.

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.

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 interface screen roles.

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

    Add the information to check

    Provide redacted interface labels to distinguish authentication, payment, private account content and ordinary content.

  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 Authentication, Payment, Private account content, Ordinary content, Review. 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 Review 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
Sign-in formAuthentication100%
Checkout fieldsPayment100%
Private inboxPrivate account content98.0%
Public documentationOrdinary content97.0%
Missing roleReview97.0%
Unresolved extractionReview95.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

Understand the results

Interface screen roles: 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

  • Testing UI-role labels with fictional metadata.
  • Documenting uncertain screens in a privacy-aware prototype.
  • Separating a current input flow from unrelated navigation labels.

Outside this demonstration

  • Sending real credentials, payment values or private messages for classification.
  • Using a model label as the gate that permits data transmission.
Example FAQ

Using this example

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

Can this decide whether a real screen may be uploaded?

No. Permission and redaction must be enforced before sending data. This text exercise is not an authorization mechanism.

Does Ordinary content mean safe?

No. It describes the supplied public-content role. It does not verify every field, remove personal data or override application permissions.

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.