Jev email attachment triage

Choose which email attachment is relevant to a record

Provide the target record, message and attachment preview. Compare an attachment worth reading with unrelated material or a preview too sparse to decide.

email attachment triageLive API
Try an example

The preview identifies the same job and its revised quote.

Source: API-collected workflow inspiration; original demonstration below

Source and example scope

This is an independently authored text demonstration inspired by the linked X discussion. Its rules and synthetic inputs are ours. It does not reproduce the author’s application, verify reported outcomes, or perform an external action.

Using the target record, message and attachment preview: Read if the attachment contains information needed for that record; Skip if it is clearly unrelated or only decoration; Review if it could matter but the supplied preview does not establish that.

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

An attachment filename alone is a weak signal. This decision compares the supplied message and preview with one target record, so a valid invoice for another customer can still be skipped.

Read means the supplied description contains relevant information. Review preserves uncertainty when a file might matter but its contents are unknown. Neither outcome checks malware, reads a PDF or grants access.

This is an independently authored text demonstration inspired by the linked X discussion. Its rules and synthetic inputs are ours. It does not reproduce the author’s application, verify reported outcomes, or perform an external action.

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 attachment relevance.

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

    Add the information to check

    Provide the target record, message and attachment preview.

  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 Read, Skip, Review. 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 Review 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
Quoted workRead100%
Signature imageSkip95.0%
Unreadable scanReview93.0%
Different customerSkip99.0%
Payment receiptRead98.0%
Misleading filenameSkip86.0%

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

Attachment relevance: 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.

Replay options

Inspect saved outputs or request a new decision

View the code example
Two independent commands
# Offline: inspect the downloaded saved observations. No API key is needed.
python preview_choice_workflow.py samples.json saved-api-results.json

# Optional live request: install the SDK and set TYPESAFE_API_KEY privately.
npm install @typesafe-ai/sdk@0.6.0
node run-choice-sample.mjs samples.json case-1
# The live response prints to the terminal; it does not update saved-api-results.json.
Scope of this demo

Where this decision fits

Useful scope

  • Pre-screening attachment metadata before a separate reader runs
  • Separating job documents from signature images
  • Keeping unknown previews in a manual queue

Outside this demonstration

  • Opening or parsing PDF files
  • Malware detection or attachment security approval
  • Updating customer records automatically
Example FAQ

Using this example

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

Can I paste a filename without a preview?

Yes, but a vague filename may lead to Review. Include the email context and target record; the model cannot inspect bytes that you have not supplied.

Does Read mean the attachment is safe?

No. It means relevant to the target record. File scanning, access checks and a sandbox belong in the application that opens the attachment.

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.