Jev note intake kind

Sort an inbox note as a task, idea or reference

Paste a captured note to identify its stated purpose. Distinguish an action to carry out from a possibility or saved reference, keeping notes with two equally central purposes marked as mixed.

What kind of note did you capture?Live API
Try an example

Original input for the Task 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 note’s stated purpose.

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

A note can mention an action without assigning it.

A proposal for a reminder tool contains send, but it is still an idea. The committed follow-up names work to carry out. That distinction matters when a capture inbox feeds a task list.

Reference material should remain available without becoming a to-do item. Mixed preserves a note that both records an explanation and assigns a follow-up, so the receiving application can split it deliberately.

This is an original intake example inspired by a discussion of organizing Telegram captures in Obsidian. It does not read either service or create notes in a vault.

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 note inbox classification.

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

    Add the information to check

    Paste a captured note to identify its stated purpose.

  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 Task, Idea, Reference, Mixed, 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
Committed follow-upTask100%
Possible experimentIdea100%
Saved documentationReference99.0%
Two purposesMixed99.0%
An idea containing an action wordIdea100%
No captured 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 a personal capture inbox
  • Reviewing notes before turning them into tasks
  • Replaying the exact synthetic requests and inspecting their distributions

Outside this demonstration

  • Creating calendar deadlines from implied intent
  • Choosing a destination project without its context
  • Treating six fixture expectations as measured production accuracy
Example FAQ

Questions about note intake kind.

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

Can a reference note include a command?

Yes. Quoted instructions in documentation can remain Reference when the note is explicitly saved for consultation. Purpose matters more than the presence of an imperative verb.

Does Mixed create two notes?

No. The label makes the two purposes visible. The application or user decides whether to split the capture.

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 note intake kind input

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