Use cases· Last updated

Procurement decision workflow 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 decision workflow slice of the procurement path decisions pack. Intent: apply the Jev (TypeSafe System One) decision model to procurement path decisions decision workflow. Primary search language: Procurement Jev decision workflow. 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

Procurement path decisions is a workflow, not a chat. Assemble a narrow state, ask the primitives below, and let the intake orchestrator branch. TypeSafe’s docs say a good question is a snap decision a knowledgeable person could make in a few seconds — not an open-ended analysis of the purchase justification.

Hub: Use cases. Compare, when the other tool is the real job: procurement workflows.

Decision Workflow inputs

Keep only fields the questions name:

{
  "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" }
}

Point instructions at req.text, policy.sole_source, bands.category. Drop full RFP PDF / scans; vendor pricing tables for Jev to “add up”.

Decision signals and actions

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?

All of these share state and run in parallel. Code owns the graph:

def proc_route(ans, amount_cents):
    path = ans["path"]
    if path.confidence < FLOOR or path.choice == "other":
        return "buyer_review"
    if amount_cents >= BID_FLOOR:  # code
        return "force_bid"
    if path.choice == "sole_source" and ans["policy_ok"].noul < T_OK:
        return "need_better_justification"
    return f"path:{path.choice}"

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

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.

Low confidence, path == other, or a policy miss → human or safe default; do not create a PO or award a vendor.

Evaluation and rollout notes

Shadow: Buyers assign path as today; log Jev beside the PR.

Canary: Auto-hold weak sole-source justifications only.

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 you are here
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 evaluation
Shadow → canary production rollout

FAQ

Does Jev execute the intake orchestrator action? No. It returns typed answers. Your intake orchestrator code calls queues, models, or humans.

Why several questions in one request? TypeSafe’s fan-out pattern: extra questions are cheap versus another HTTP call. Path + justification_quality + policy_ok in one call. Award scoring of a shortlist is a later pack with different criteria — do not overload this Choice.

Where is the rest of the Procurement pack? Start with Procurement input contracts and Procurement confidence thresholds. 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

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.