Jev video progress indicator

Check whether a video's structure needs a progress indicator

Describe the video's structure to compare staged explanations with self-contained reactions or punchlines. Choose a show, hide or unclear preference without using duration alone or editing the video.

video progress indicatorLive API
Try an example

The viewer moves through a staged task.

Source: API-collected workflow inspiration; original demonstration below

Source and example scope

This independently authored text exercise adapts an edit decision defined in the linked Jev Shorts Editor repository. Its synthetic shots, simplified rules and missing-input outcomes are original to this page. It does not reproduce a rendered edit, inspect video, or verify the repository’s timing and cost claims.

Choose Show when the clip is a structured walkthrough, numbered list or staged explanation where progress helps orientation.

Decision rules and labels
ShowHideUnclear
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

A progress indicator can help viewers place a step within a sequence. This example asks about that orientation need rather than assuming that every long clip needs a bar or every short clip should omit one.

The model sees the text you supply. Playback timing, screen layout and accessible presentation belong in the player or renderer. The result makes no claim about retention or completion rates.

This independently authored text exercise adapts an edit decision defined in the linked Jev Shorts Editor repository. Its synthetic shots, simplified rules and missing-input outcomes are original to this page. It does not reproduce a rendered edit, inspect video, or verify the repository’s timing and cost 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 video progress indicator.

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

    Add the information to check

    Describe the video's structure to compare staged explanations with self-contained reactions or punchlines.

  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 Show, Hide, Unclear. 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 Unclear 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
Setup walkthroughShow100%
Numbered adviceShow100%
Single reactionHide100%
Single claimHide100%
Length onlyUnclear99.0%
Short but stagedShow100%

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

Video progress indicator: 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.

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

  • Comparing text-based edit choices before rendering
  • Replaying the same synthetic shot with changed context
  • Keeping the selected option and its distribution for an editor

Outside this demonstration

  • Uploading or inspecting video footage
  • Rendering, cutting or exporting a video
  • Proving audience retention or visual quality
Example FAQ

Using this example

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

Does a long clip always get Show?

No. The rule uses structure. A long unstructured reaction still differs from a sequence of steps.

Can the model choose the bar’s color or placement?

Those are outside this request. The output only addresses whether progress orientation is useful for the described content.

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.