Jev procurement shortlist match

Classify a purchase brief as goods, service or rental

Match a purchase brief to supplied fictional printer goods, maintenance and rental categories. Compare mixed or conflicting scopes without presenting the shortlist as official procurement codes.

procurement shortlist matchLive API
Try an example

The deliverable is ownership of equipment.

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.

Match the main purchased deliverable to the supplied fictional shortlist.

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

Procurement classification depends on the purchased deliverable. Similar equipment names can describe a goods purchase, a rental or a maintenance service, so the shortlist needs usable descriptions rather than bare code numbers.

The identifiers here are fictional teaching labels. An operational CPV workflow needs the relevant official vocabulary, the full procurement scope and review by the responsible person.

The source author describes Jev choosing among a supplied procurement-code shortlist. This original example demonstrates that selection pattern without copying the application, choosing a supplier or claiming legal classification accuracy.

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 procurement brief classification.

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

    Add the information to check

    Match a purchase brief to supplied fictional printer goods, maintenance and rental categories.

  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 G, M, R, Mixed, 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
Buy the equipmentG100%
Maintain existing devicesM100%
Rent for an eventR100%
Two equal deliverablesMixed98.0%
Vague purchaseReview99.0%
Contradictory ownershipR59.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 Contradictory ownership, the expectation was Review; the observed choice was R.Verified

Understand the results

Procurement brief classification: 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

  • Prototyping the shortlist-selection step of a procurement assistant.
  • Testing whether ownership and deliverable terms distinguish similar descriptions.
  • Keeping mixed purchases and incomplete briefs visible for review.

Outside this demonstration

  • Treating fictional labels as official procurement codes.
  • Using the result to award a contract or establish legal compliance.
Example FAQ

Using this example

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

Are G, M and R actual CPV codes?

No. They are deliberately fictional IDs for this demonstration. Use an authoritative code list and competent review for a real procurement classification.

Why not always choose the closest description?

A vague or equally mixed purchase may not support one category. Keeping Mixed and Review prevents the interface from presenting an arbitrary shortlist choice as resolved.

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.