Jev page clutter role

Distinguish page clutter from essential controls

Describe a page element and its role. Separate ads, promotions and cookie overlays from essential content and controls, preserving uncertain mixtures rather than removing elements automatically.

Which role is supported by this description?Live API
Try an example

Blank space alone does not establish an advertisement slot.

Source: API-collected workflow inspiration; original demonstration below

Source and example scope

The API-collected roundup links the cited project, whose pinned code provides the decision purpose. This demonstration separately authors its Choice rubric, priorities, missing-context outcomes and synthetic inputs. It neither runs the upstream application nor verifies its performance, security or execution claims.

Classify the element.

Decision rules and labels
KeepCookie overlayAd spacePromotionUncertain
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

An overlay is not automatically disposable.

The sign-in preset describes account access; the newsletter preset describes an optional invitation. The unlabeled rectangle supplies no role evidence at all. Visual shape alone is insufficient for deciding what an element does.

The empty ad-slot preset includes a label and a stated purpose. An arbitrary blank rectangle would not provide that evidence. A container mixing the only navigation with a campaign remains Uncertain because a single cleanup action could remove useful controls.

The source extension separates classification from its hiding policy. This original window stops earlier: it returns a label from pasted descriptions and neither inspects a live DOM nor clicks, removes elements or grants consent.

The API-collected roundup links the cited project, whose pinned code provides the decision purpose. This demonstration separately authors its Choice rubric, priorities, missing-context outcomes and synthetic inputs. It neither runs the upstream application nor verifies its performance, security or execution 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 page element classification.

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

    Add the information to check

    Describe a page element and its role.

  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 Keep, Cookie overlay, Ad space, Promotion, Uncertain. 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 uncertain or unexpected results 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
Unidentified blank rectangleUncertain98.0%
Consent dialogCookie overlay100%
Empty reserved slotAd space100%
Newsletter invitationPromotion100%
Login accessKeep100%
Mixed containerUncertain99.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

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

  • Testing element-role descriptions before cleanup rules
  • Preserving authentication and main content
  • Recognizing mixed containers that need more context

Outside this demonstration

  • Bypassing a paywall
  • Accepting cookie consent automatically
  • Hiding live elements from this window
Example FAQ

Questions about page clutter role.

Input scope and downstream handling determine what this judgment means.

Does Cookie overlay accept or reject cookies?

No. It identifies the described role only. Hiding a dialog and making a consent choice are separate actions.

Can an empty space always be classified as Ad space?

No. The preset explicitly identifies a reserved advertisement slot. Without that context, Uncertain is the appropriate offered route.

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 page clutter role input

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