Procurement audit trail 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 audit trail slice of the procurement path decisions pack. Intent: apply the Jev (TypeSafe System One) decision model to procurement path decisions audit trail. Primary search language: Procurement Jev audit trail. 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 audit trail for procurement path decisions is a decision trace: replayable inputs, typed answers, floors, and the action the intake orchestrator took. It is not a chat log and not a clone of a SIEM product page.
Hub: Use cases. Compare, when the other tool is the real job: procurement workflows.
Audit Trail inputs
Persist the filtered payload (the contract), not whatever arrived at the edge:
{
"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" }
}Redact secrets before the object hits cold storage.
Decision signals and actions
Minimum fields:
- req.id
- amount + currency
- policy SHA + model pin
- answers
- PR/PO number if created
Also store usage.input_tokens (vendor meter) and the full probabilities map — argmax-only logs cannot explain a close path.
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
If you cannot explain creating a purchase order or awarding a vendor from the trace, you are not ready to auto-act. 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
Traces are the eval warehouse. Replay against path gold from buyers, policy-ok gold, and whether sole-source was acceptable after criteria or alias 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 |
input contracts |
| What to gather first | evidence collection |
| Atomic rules | policy checks |
| Act / review / abstain | confidence thresholds |
| Reviewer payload | human handoff |
| What to persist | you are here |
| How it breaks | failure modes |
| Labeled replay | evaluation |
| Shadow → canary | production rollout |
FAQ
Is the HTTP log enough? No. Persist the filtered state, full probabilities, floors, and downstream action as a decision trace.
May I log raw secrets? Redact in code. Jev will not be your DLP layer.
Where is the rest of the Procurement pack? Start with Procurement human handoff and Procurement evaluation. 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.