Jev status report blocker kind

Identify the blocker described in a work update

Read a status update to distinguish a dependency, unresolved scope or missing access. Keep absent or unclear blockers separate rather than assessing an employee or assigning a severity.

What kind of blocker does this update state?Live API
Try an example

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

Classify the stated obstacle to continuing work.

Decision rules and labels
Dependency blockerScope blockerAccess blockerNo blocker statedNeed 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

Classify the obstacle, not the person.

A frustrated tone does not establish a blocker. The fifth example explicitly says work continues. The other fixtures identify a missing artifact, an unresolved requirement and missing access as different obstacles.

The label can help a reviewer ask a focused follow-up: obtain the artifact, clarify the acceptance criteria or verify access. It does not identify who is responsible or assess the author’s performance.

The source suggests reviewing daily updates for follow-up. This original example preserves the report’s stated evidence and sends no message to a manager or colleague.

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 one spreadsheet row producing two separate classification results
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 work blocker classification.

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

    Add the information to check

    Read a status update to distinguish a dependency, unresolved scope or missing access.

  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 Dependency blocker, Scope blocker, Access blocker, No blocker stated, 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
Waiting for schemaDependency blocker100%
Unknown acceptance ruleScope blocker98.0%
Permission missingAccess blocker100%
Routine progressNo blocker stated100%
Frustration without a blockerNo blocker stated100%
No update textNeed 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 explicit project blockers
  • Preparing evidence-based follow-up questions
  • Replaying the exact synthetic requests and inspecting their distributions

Outside this demonstration

  • Scoring employee performance from a daily note
  • Inferring blame or private emotion from wording
  • Treating six fixture expectations as measured production accuracy
Example FAQ

Questions about status report blocker kind.

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

Does No blocker stated mean there are no problems?

No. It only means the supplied complete update names no obstacle to continuation. Hidden problems remain outside the evidence.

Can a report have two blockers?

Yes. These fixtures make one primary. For equally central blockers, extend the contract to preserve multiple outcomes instead of forcing one.

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.

Try your own status report blocker kind input

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