Jev document intake evidence

Check a document submission against its evidence checklist

Provide the requirements and submission notes. Compare required parts that are present, explicitly absent or only mentioned before passing the packet to a reviewer.

Does the supplied submission establish the required parts?Live API
Try an example

Original input for the Required evidence present outcome. Edit the evidence to send a new request.

Source: API-collected workflow inspiration; original demonstration below

Source and example scope

This is an original synthetic demonstration adapted from the cited workflow discussion. It does not reproduce the source application or verify its performance, adoption or security claims.

Compare checklist requirements with submission notes.

Decision rules and labels
Required evidence presentRequired part missingReference unresolvedChecklist unclearNeed 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 reference to an attachment does not prove it is available.

Reference unresolved keeps a mentioned but unconfirmed reviewer note separate from an explicitly missing note. That distinction tells an intake reviewer whether to verify an attachment or request a new document.

The optional-budget fixture checks the actual checklist. An absent optional part does not become a missing requirement because its name appears in the submission notes.

This text review does not open attachments, extract their contents, assess legal validity or approve a commercial document. File existence and readability should come from ordinary application checks.

This is an original synthetic demonstration adapted from the cited workflow discussion. It does not reproduce the source application or verify its performance, adoption or security claims.

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 document intake checklist.

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

    Add the information to check

    Provide the requirements and submission notes.

  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 Required evidence present, Required part missing, Reference unresolved, Checklist unclear, 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 Required part missing, Checklist unclear, 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
Both parts presentRequired evidence present98.0%
Reviewer note absentRequired part missing99.0%
Attachment mentioned onlyReference unresolved99.0%
Undefined requirementChecklist unclear89.0%
Optional part not requiredRequired evidence present99.0%
No checklistRequired part missing71.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. 5 of 6 results matched the authored fixture expectations. For No checklist, the expectation was Need evidence; the observed choice was Required part missing.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

  • Reviewing required versus optional intake evidence
  • Preserving unresolved attachment references
  • Replaying the exact synthetic requests and inspecting their distributions

Outside this demonstration

  • Pretending to open attachments from text notes
  • Approving a legal or commercial document
  • Treating six fixture expectations as measured production accuracy
Example FAQ

Questions about document intake evidence.

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

Does Required evidence present approve the submission?

No. It checks presence under the supplied checklist. Correctness, authenticity and substantive review are separate.

Should the model check whether a file exists?

No. Ordinary code should check file presence and access. The model interprets those verified notes against the semantic checklist.

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 document intake evidence input

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