Procurement evaluation with Jev
Requesters write “need this vendor, they already know us.” Catalog, bid thresholds, and vendor master still own the buy. Jev scores policy-fit of the justification you paste. It does not raise POs or pick winners.
This unofficial page is the evaluation slice of the procurement path decisions pack. Intent: apply the Jev (TypeSafe System One) decision model to procurement path decisions evaluation. Primary search language: Procurement Jev evaluation. Confirm patterns on docs.typesafe.ai. This site does not sell, issue, or proxy TypeSafe keys. Use a credential you already have from the console or a documented gateway.
Independent angle (cover ≠ clone): Catalog vs bid vs exception as typed questions + policy excerpts — not a clone of a procurement-workflow SaaS sitemap.
Procurement use-case context
Evaluation for procurement path decisions is a frozen harness, not a vibe check and not an opinion-blog “Jev review.” Labels: path gold from buyers, policy-ok gold, and whether sole-source was acceptable. We publish no unofficial accuracy.
Hub: Use cases. Compare, when the other tool is the real job: procurement workflows.
Evaluation inputs
Replay the same contract you ship:
{
"req": { "id": "pr-77", "text": "Only Acme can integrate with our badge system by Friday." },
"policy": { "sole_source": "Sole-source needs a named alternative and a date risk, not brand preference." },
"bands": { "amount_band": "25-50k", "category": "security_hardware" }
}Freeze questions, criteria, and jev-1.13.0. Record the response model.
Decision signals and actions
Score these, not a blog-grade star rating:
- False sole-source on a preference-only canary
- False-hold (requester throughput)
- Agreement after policy-text edits
Pair auto-act errors with handoff rate. If the intake orchestrator never acts, you have not evaluated procurement path decisions — you have evaluated a human queue.
Do not treat a Noul of 0.5 as a “medium” procurement path decisions score — it means yes and no are equally likely. Conjunctions stay in your code.
Guardrails and escalation
Promote a threshold only when the harness says auto-act error ≤ SLA and reviewers still catch the residual. TypeSafe’s confidence-gated examples use a lower bar for recoverable reads than for irreversible actions. Those numbers are illustrations. For procurement path decisions, treat auto_create_po as the high bar (creating a purchase order or awarding a vendor). Tune on labels — see offline evaluation.
Evaluation and rollout notes
After any criteria edit, rerun before production. Cookbook lifts you see on TypeSafe pages are vendor claims — re-measure on your purchase justifications. Pin jev-1.13.0 (the versioned id) after you fit thresholds. jev-latest and the marketing line jev-1.13 can move. Log the response model. TypeSafe’s published list price for jev-1.13 is $0.042 per million input tokens (vendor claim — confirm on the models page); output tokens are free on that same page. Unused distractors still bill as input.
Official Python and JavaScript SDKs read TYPESAFE_API_KEY and retry documented 429/529. This site does not sell, issue, or proxy TypeSafe keys. Use a credential you already have from the console or a documented gateway.
Pack map
| Slice | Page |
|---|---|
| Graph and primitives | decision workflow |
What may enter state |
input contracts |
| What to gather first | evidence collection |
| Atomic rules | policy checks |
| Act / review / abstain | confidence thresholds |
| Reviewer payload | human handoff |
| What to persist | audit trail |
| How it breaks | failure modes |
| Labeled replay | you are here |
| Shadow → canary | production rollout |
FAQ
Will jev.pro publish a leaderboard for this use case? No. Measure on your labels. Vendor cookbook figures stay labeled as vendor claims.
What must stay frozen? Questions, criteria, and the pinned model id. Aliases can move.
Where is the rest of the Procurement pack? Start with Procurement failure modes and Procurement production rollout. Cluster hub: Use cases.
Will Jev pick the cheapest vendor? No. Price compare in code or the bid tool. Jev judges the justification text.
Can we paste three PDF quotes? Not as images. Extract facts you need; keep state small. Unused tokens still bill (vendor claim — confirm models page).
What this page does not claim
- Not a procurement suite or savings calculator.
- Not competition-law advice.
- Not official TypeSafe.
- Official TypeSafe status, or that jev.pro issues API keys.
- That a schema-constrained answer is automatically factually correct.
Disclaimer
This is an independent unofficial site and is not affiliated with TypeSafe AI; official documentation is available at https://docs.typesafe.ai.
Primary documentation: https://docs.typesafe.ai. Hub: Use cases.
Sources
Public TypeSafe or adjacent documentation only. No private claims.