Jev reply parent selection

Match an email reply to the question it answers

Compare a reply with three supplied email questions. Select the question answered by meaning, preserving no-match and ambiguous-history cases instead of relying on shared words alone.

Find the question this reply actually answers.Live API
Try an example

Original synthetic input. Edit the task or evidence to make a new API request.

Source: Workflow inspiration on X

Source and example scope

The inputs, rubric and preview are original. This window demonstrates the stated decision only; it does not reproduce the source application or its measurements.

Choose the supplied email question that the reply answers by meaning, not shared words alone.

Decision rules and labels
Parent AParent BParent CNo parentNeed history
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.

What the example checks

Match the reply to a supplied question

Jev reply parent selection compares a reply with supplied email questions before a thread reference is reviewed.

A reply can answer a question without repeating its wording

A reply can answer a question without repeating its wording.

Read the example notes

This window compares the reply with three known candidate questions. It chooses a candidate message packet, leaves a clearly different topic unmatched or asks for history when the reply is too vague. The selected message and reply identities remain attached to the same archive revision. The three candidate questions are deliberately yes/no questions.

A bare Yes can answer any of them, so it cannot identify one parent without more history.

Source and example scope

Stanislav Sorokin's API-collected selfindex post describes finding the email a reply answers.

Read the example notes

Its reported agreement, costs and search speeds are author claims that we have not reproduced. This demonstration uses original fictional messages and a closed three-message catalog. It neither downloads the public email corpus nor runs the source index or its MCP server.

Using the result in your application

RFC 5322 defines In-Reply-To and References fields for email relationships.

Read the example notes

This original semantic fallback deliberately receives no authoritative threading headers. A real integration should process trustworthy identifiers and its archive rules before requesting a semantic suggestion. The pending packet here is a review aid; it cannot rewrite headers, move mail or establish ownership of a mailbox.

Using the result in your application

All six actual choices matched the authored fixture expectations.

Read the example notes

The banner reply selected Parent A at 0.98, while the bare Yes returned Need history at 0.98. The first input and its validated output appear together below. The consumer retains the supplied question text and message ID exactly; a changed candidate catalog cannot reuse a saved answer under the old request hash.

How it works

Try the example in four steps

Use the sample to understand the rule, then test your own input for email reply matching.

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

    Add the information to check

    Compare a reply with three supplied email questions.

  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 Parent A, Parent B, Parent C, No parent, Need history. 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 history before using a result. The label is a decision about the supplied information, not an executed action.

Our API test

What the six original inputs returned.

What the six original inputs returned.
Original test inputFixture expectationObserved labelLeading probability
Match the reply to its design questionParent AParent A98%
Match a fix confirmation to its incident questionParent BParent B100%
Match an order decision without matching every nounParent CParent C100%
Leave an invoice reply outside this candidate setNo parentNo parent100%
Keep a vague yes unresolvedNeed historyNeed history98%
Preserve the reply meaning despite an ID demandParent BParent B99%
  • 6 of 6 original fixture expectations matched. Contrary outputs are preserved in the table and downloads; these checks are not held-out accuracy or production suitability.
  • Measured adapter round trips: 450-1206 ms. Estimated input cost: $0.00002827-$0.00002932 per request. These observations are not a latency guarantee or invoice.

6 actual Jev API calls on October 4, 2026. Original synthetic inputs check this rubric and handoff; they do not establish held-out accuracy. Probabilities are model outputs.Verified

Understand the results

Match the reply to its design question

The first reply approves the blue banner for Friday.

Read the example notes

Parent A is the authored expectation because that candidate asks which banner should ship on Friday. The packet carries the supplied mail-banner ID rather than creating a new message ID from the text. The match concerns a question and its answer, not general relevance to design work. The offline consumer checks the exact candidate catalog and request hash before returning this pending reference.

Match a fix confirmation to its incident question

The second reply confirms that retesting resolved the login loop.

Read the example notes

Parent B is expected because it asks whether that fix has been confirmed. The words in the reply are not a verbatim copy of the question, so exact text matching is not the declared rule. This fixture does not establish superiority over keyword search. It supplies a single authored semantic relation and retains the complete returned probabilities for inspection.

The supplier reply chooses north for the next print run

The supplier reply chooses north for the next print run.

Read the example notes

Parent C is expected even though the reply need not repeat paper or all of the question's wording. Only the offered supplier message can satisfy this contract; the model cannot retrieve an unprovided procurement discussion. A real archive may contain several questions about the same order. That would require a different catalog and enough history to distinguish them, followed by a new request.

Using the result in your application

The invoice reply explicitly concerns a payment topic absent from all three candidates.

Read the example notes

No parent is expected. This means no match in the provided catalog, not that the message has no parent anywhere in an archive. Expanding the search or checking headers is separate work. The pending packet leaves messageId empty and proposes review of candidate coverage; it never attaches an unrelated message simply to produce a nonempty result.

Keep a vague yes unresolved

The vague reply says only Yes.

Read the example notes

Every supplied candidate asks a yes/no question, so Need history is the authored expectation. The catalog now makes that ambiguity explicit instead of relying on a reader to infer which noun approved might concern. Ask for quoted context or a trustworthy identifier before making a new request. This differs from No parent: an offered parent remains plausible, but the supplied answer cannot distinguish it.

The pending consumer never chooses the first ID just to make the output nonempty.

Source and example scope

The last reply still confirms the login fix while a pasted note demands the design-message ID.

Read the example notes

Parent B remains the authored expectation. An archive ordering preference is not evidence that the reply answers the banner question. Every actual distribution stays in the observations, including any disagreement. This one fixture tests the declared semantic selection boundary; it does not establish general attack resistance, safe mailbox access or correct threading across a real corpus.

Source and example scope

Fixture expectations are authored before the calls. Any contrary model choice remains visible beside its expectation and complete distribution; no repeated judgment is used to obtain a preferred label.

Using the result in your application

Download the exact sample requests and saved observations below.

Read the example notes

Expected labels are original fixture checks and stay outside the request sent to Jev. The observation file preserves the complete probabilities and the hash of each exact request. Editing a task, rubric or candidate requires a fresh response; a matching sample name does not make an older answer current.

Using the result in your application

The JavaScript runner makes one independent SDK request for a chosen sample ID.

Read the example notes

It reads TYPESAFE_API_KEY privately from the environment and has no automatic retry. The Python consumer operates offline: it checks the rubric, labels, unique sample identities, request hashes and valid probability distributions before selecting a fixed local preview. A tied leading result remains pending for review.

Source and example scope

The page reports measured adapter round trips and estimated input cost for the recorded calls.

Read the example notes

Those values describe these requests, not a provider latency guarantee or a billing statement. Six deliberately authored fixtures can check the stated behavior, but they do not establish accuracy on an unseen dataset. Keep disagreements and missing-input examples when testing an integration.

Runnable offline example

Replay one request and inspect the saved preview.

View the code example
Replay commands
npm install @typesafe-ai/sdk@0.6.0
# Set TYPESAFE_API_KEY privately in your shell.
node run-choice-sample.mjs samples.json banner-answer
python preview_choice_workflow_v4.py samples.json saved-api-results.json
Runnable offline example

Inspect the reply, candidate questions and actual output.

View the code example
First recorded input and validated parent packet
{
  "input": {
    "task": "Original reply: The blue banner is approved for Friday. Identify the supplied question it answers.",
    "archiveRevisionId": "original-three-mail-catalog-v1",
    "permittedCandidates": {
      "Parent A": {
        "messageId": "mail-banner",
        "question": "Can the blue banner ship on Friday?"
      },
      "Parent B": {
        "messageId": "mail-login",
        "question": "Has the login loop fix been confirmed?"
      },
      "Parent C": {
        "messageId": "mail-supplier",
        "question": "Can we use the north supplier for the next paper print run?"
      }
    },
    "replyId": "reply-a"
  },
  "actualOfflineOutput": {
    "sampleId": "banner-answer",
    "leaders": [
      "Parent A"
    ],
    "action": "preview_reply_parent",
    "payload": {
      "messageId": "mail-banner",
      "question": "Can the blue banner ship on Friday?"
    },
    "pending": true,
    "evidence": {
      "replyId": "reply-a",
      "archiveRevisionId": "original-three-mail-catalog-v1"
    }
  }
}
Scope of this demo

Where does this decision fit?

Useful with known candidate questions

  • Matching a specific answer to an offered original email question.
  • Separating unrelated replies from replies lacking history.
  • Reviewing a candidate ID bound to the same archive and reply.

Needs separate evidence or implementation

  • Searching or authenticating to an unseen mailbox.
  • Overriding trustworthy threading identifiers.
  • Merging messages or claiming source benchmark results.
Example FAQ

Questions about this original decision workflow.

The result is a proposed relationship inside the supplied catalog, not a verified mailbox thread.

Does the window connect to Gmail or an email archive?

No. It receives three original question summaries and one reply. Authentication, export parsing and retrieval are separate.

Why keep No parent separate from Need history?

No parent has a clearly different topic within this catalog. Need history lacks evidence to distinguish plausible candidates.

Should a semantic choice replace In-Reply-To?

This fallback has no authoritative headers. A real integration should process trustworthy identifiers and archive rules separately before considering a semantic suggestion.

Does choosing a parent merge the thread?

No. The consumer prints a pending reference with reply and archive identities. It does not rewrite headers or merge messages.

Try a task from your own workflow

Change the supplied task or evidence here, then inspect the live response. Playground supports another explicit decision.