Procurement input contracts 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 input contracts slice of the procurement path decisions pack. Intent: apply the Jev (TypeSafe System One) decision model to procurement path decisions input contracts. Primary search language: Procurement Jev input contracts. 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
An input contract is the allow-list of fields you will ever POST for procurement path decisions. It is a decision contract for the purchase justification: if a field is not named in instructions, it should not be in state. That is how you beat noisy “dump the object” integrations — the rival-intent failure mode — without cloning anyone’s IA.
Hub: Use cases. Compare, when the other tool is the real job: procurement workflows.
Input Contracts inputs
Documented System One inputs: state (string, object, or array of text) and a questions map. English is the primary training language. Images, audio, and video are not accepted.
Allow for procurement path decisions:
{
"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" }
}Bind paths: req.text, policy.sole_source, bands.category.
Refuse at the wrapper (do not send):
- full RFP PDF / scans
- vendor pricing tables for Jev to “add up”
- the entire vendor master as unused tokens
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.
Decision signals and actions
The contract exists so each primitive stays atomic:
| Id | Type | Job |
|---|---|---|
path |
Choice | catalog / bid / sole_source / reject / other |
justification_quality |
Score | preference-only → documented constraint |
policy_ok |
Noul | Justification meets policy.sole_source? |
If a new CRM field appears, either add a question that names it or drop it. Do not “just include it.” 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
Contracts are a guardrail: missing required text → do not call Jev (or ask a Noul “is enough information present?”). That is cheaper than a confident wrong path. 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
Version the contract (field list + criteria git SHA) next to the pinned model. Replay path gold from buyers, policy-ok gold, and whether sole-source was acceptable when either changes. 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 |
you are here |
| 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 | evaluation |
| Shadow → canary | production rollout |
FAQ
What happens if I send the whole warehouse row?
jev-1.13 loses accuracy as distractors grow (official jaggedness note). Drop full RFP PDF / scans. 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.
Can I send images of the artifact? No. State is text (string, object, or array of text). Transcribe first.
Where is the rest of the Procurement pack? Start with Procurement decision workflow and Procurement evidence collection. 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.