Jev employment claim presence

Identify explicit claims about jobs in product copy

Paste product wording to distinguish claims about replacing, creating or preserving jobs. A description of a task or human review need not make an employment claim.

What employment claim is actually written?Live API
Try an example

The statement concerns positions, not just an automated task.

Source: API-collected workflow inspiration; original demonstration below

Source and example scope

The API-collected roundup links Sniff Test. Its pinned rules define the text distinction adapted here. This original Choice demonstration uses synthetic inputs and adds explicit missing-context handling; the source linter uses its own yes-or-no judgments. It does not reproduce that application or validate the truth of a claim.

Classify employment claims in this copy.

Decision rules and labels
Replacement claimCreation claimPreservation claimMultiple claim typesNo employment claimNeed wording
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

Describing automation does not automatically make a claim about jobs.

The invoice preset divides work between a parser and a reviewer. It does not say whether any position changes. The coordinator preset goes further by explicitly claiming that positions will be replaced.

Creation and preservation are employment claims too. A sentence promising that no employee will ever be replaced deserves evidence review just as a sentence promising new jobs does. The mixed preset records both stated effects without choosing one to hide the other.

This page classifies product copy. It does not evaluate workers, recommend staffing decisions, forecast employment or verify a vendor promise. Treat a detected claim as a cue to inspect its evidence before publication.

The API-collected roundup links Sniff Test. Its pinned rules define the text distinction adapted here. This original Choice demonstration uses synthetic inputs and adds explicit missing-context handling; the source linter uses its own yes-or-no judgments. It does not reproduce that application or validate the truth of a claim.

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 employment claims in copy.

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

    Add the information to check

    Paste product wording to distinguish claims about replacing, creating or preserving jobs.

  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 Replacement claim, Creation claim, Preservation claim, Multiple claim types, No employment claim. 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 wording 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
Position replacementReplacement claim100%
Employment growthCreation claim100%
Jobs preservedPreservation claim100%
Two claimsMultiple claim types99.0%
Task with human reviewNo employment claim96.0%
No wordingNeed wording100%

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

  • Finding employment promises in a landing-page draft
  • Separating task descriptions from job-effect assertions
  • Preparing claims for editorial substantiation

Outside this demonstration

  • Evaluating employees or candidates
  • Deciding staffing levels
  • Predicting employment effects
Example FAQ

Questions about employment claim presence.

Input scope and downstream handling determine what this judgment means.

Does automating a task count as replacing a job?

Not under this rule by itself. The text must explicitly claim a job or employment effect.

Does the selected claim type prove the promise?

No. The label identifies what the supplied wording says. A separate evidence review must assess whether it is supportable.

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 employment claim presence input

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