Jev app navigation selection

Choose navigation that fits a layout brief

Describe the required navigation structure. Compare a sidebar, icon rail and top bar, including a brief that none of those components can satisfy.

Which offered navigation meets the brief?Live API
Try an example

The brief asks for the full labeled panel.

Source: API-collected workflow inspiration; original demonstration below

Source and example scope

The API-collected studio roundup links this project. Its pinned implementation supplies the decision vocabulary discussed here. The six inputs and handling rules are original synthetic examples. This window returns a Choice label; it does not run the linked application or reproduce its speed, cost or output-quality claims.

Choose the navigation that satisfies the supplied brief.

Decision rules and labels
SidebarIcon railTop barNo offered fitNeed navigation brief
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 component catalog gives the decision a concrete boundary.

The three choices describe different structures, not interchangeable visual themes. A full sidebar keeps grouped names visible. An icon rail uses less width and reveals labels on hover.

A clear request for bottom-only tabs is outside this catalog. That differs from a vague request to build a bookstore app, which provides too little information to select navigation.

The model returns a layout key. It does not generate JSX, render the navigation or prove that the selected component is accessible. Those responsibilities remain with the application and its component library.

The API-collected studio roundup links this project. Its pinned implementation supplies the decision vocabulary discussed here. The six inputs and handling rules are original synthetic examples. This window returns a Choice label; it does not run the linked application or reproduce its speed, cost or output-quality claims.

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 app navigation choice.

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

    Add the information to check

    Describe the required navigation structure.

  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 Sidebar, Icon rail, Top bar, No offered fit, Need navigation brief. 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 navigation brief 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
Grouped labelsSidebar100%
More content roomIcon rail100%
Horizontal linksTop bar100%
Bottom onlyNo offered fit98.0%
Conflicting requirementsNeed navigation brief59.0%
No layout specifiedNeed navigation brief100%

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

Replay the saved synthetic requests to inspect each recorded decision

Replay the saved synthetic requests to inspect each recorded decision. Authored expectations and model disagreements remain available; these examples are not a production accuracy benchmark.

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

  • Routing a layout brief to a registered component
  • Distinguishing an unsupported layout from missing context
  • Keeping a layout vocabulary explicit

Outside this demonstration

  • Generating a new navigation component
  • Predicting the best layout from an industry name
  • Verifying accessibility or responsive behavior
Example FAQ

Questions about app navigation selection.

Input scope and downstream handling determine what this judgment means.

Can it choose a bottom tab bar?

Not from this catalog. The correct bounded outcome is No offered fit.

Does it render the chosen navigation?

No. This demonstration returns a label; the source application uses code and registered components to render its choices.

Is the leading probability an accuracy measurement?

No. It is one value in the returned distribution over this request’s choices. The six synthetic fixtures have authored expectations; they do not measure production accuracy.

What happens on an API failure?

The window displays an error without a fresh judgment. An incomplete-input outcome describes the supplied evidence and is not used as a fallback for provider failure.

Try your own app navigation selection input

Edit the input above, or open the Playground to explore another decision.