Jev resource purpose classification

Tell a tutorial from a demo or announcement

Read a resource excerpt to identify whether it teaches steps, shows a result or announces a development. Preserve equally central mixed purposes instead of guessing from its source label.

What role does this resource serve?Live API
Try an example

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

Read the supplied fictional excerpt and classify its primary purpose.

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

Platform and resource purpose are different labels.

A resource can teach a procedure, show a result or announce a release. The original excerpts make those functions explicit, so the judgment does not depend on a platform name or an unseen linked page.

The tutorial fixture contains actual fictional steps. The demonstration shows an outcome while explicitly omitting setup. Mixed purpose retains an equally central announcement and procedure instead of forcing one role.

This example does not search live platforms or claim to reproduce the source author’s research agent. It classifies supplied original descriptions as an intake step.

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 selecting a caption token for emphasis in an edit timeline
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 research resource types.

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

    Add the information to check

    Read a resource excerpt to identify whether it teaches steps, shows a result or announces a development.

  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 Tutorial, Demonstration, Announcement, Mixed purpose, 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
Setup walkthroughTutorial100%
Result shownDemonstration88.0%
Release noteAnnouncement84.0%
Equal instruction and newsMixed purpose93.0%
Demo in the titleTutorial88.0%
No excerptNeed 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

  • Organizing mixed research resources by purpose
  • Checking titles that do not match resource contents
  • Replaying the exact synthetic requests and inspecting their distributions

Outside this demonstration

  • Inferring a video’s contents from its platform
  • Treating a demonstration as reproducible setup evidence
  • Treating six fixture expectations as measured production accuracy
Example FAQ

Questions about resource purpose classification.

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

Does Demonstration prove the system works reliably?

No. It identifies the resource’s purpose. Reproducibility, failure coverage and measurement quality require their own evidence.

Can a tutorial also announce a release?

Yes. Mixed purpose applies when both functions are equally central. If one function is clearly primary, classify that primary role.

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.

Classify an excerpt you want to read

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