Jev UI component role fit

Choose a component role for a display requirement

Describe what the interface needs to present. Match one-item summaries, shared-attribute comparisons and ordered procedures to supplied component roles without generating or implementing a layout.

Which component role fits the display need?Live API
Try an example

Original input for the Summary card 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.

Match the requested display to a component role.

Decision rules and labels
Summary cardComparison tableStep listNo fitting roleNeed 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

Choose a known component role, then validate its fields.

The model can select a role from the application’s supplied set. It does not create a component implementation or grant permission to render arbitrary markup. A comparison table still needs rows and shared columns validated by code.

The setup-card fixture names a card but requests an ordered procedure. The role follows the actual display need. No fitting role keeps an unsupported map from being forced into a summary card.

The source describes an experiment with typed decisions and a rendering system. This original example only returns a role label; it does not generate or execute UI code.

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 ui component role matching.

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

    Add the information to check

    Describe what the interface needs to present.

  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 Summary card, Comparison table, Step list, No fitting role, 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
One item previewSummary card100%
Shared attributesComparison table100%
Ordered setupStep list100%
Unsupported interactive chartNo fitting role100%
Several steps called a cardStep list100%
No display requirementNeed 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

  • Choosing a role from a closed component catalog
  • Detecting a request that needs a new component
  • Replaying the exact synthetic requests and inspecting their distributions

Outside this demonstration

  • Rendering unvalidated model-generated markup
  • Pretending an unsupported role fits the existing Blocks
  • Treating six fixture expectations as measured production accuracy
Example FAQ

Questions about UI component role fit.

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

Does the label generate a page?

No. It chooses a role. The application still supplies validated fields and renders the existing component.

What should No fitting role do?

Keep the request for review or extend the component catalog deliberately. Do not silently fabricate fields that an existing Block does not support.

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 UI component role fit input

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