Jev evidence templates
If someone asks “why did we auto-close this?”, the evidence bundle is your answer. Jev will not write a narrative exhibit. This page is an independent field-guide note for workpaper fields — not a TypeSafe playbook and not a court kit.
This page is for builders crossing from curious to production-minded Jev use. jev.pro is an independent unofficial field guide — not affiliated with TypeSafe AI. Cover intents; do not clone rival IA. Confirm facts on docs.typesafe.ai. We do not sell keys.
Open-cluster pages are independent field-guide notes. Replicas and third-party interfaces mentioned anywhere on jev.pro are not Jev and not endorsed.
Bundle fields
Preserve this list; it is the minimum replay pack:
- Ticket / object id
- Filtered state hash (not necessarily raw PII)
- Question pack SHA + text
- Model id from response
- Door
- Probabilities JSON
- Action + actor (service vs human)
- Timestamp
That pack is a decision trace you own. TypeSafe returns typed answers; your service decides what to persist. If you omit probabilities, you cannot audit abstain bands or explain why a 0.51 / 0.49 Choice looked like a confident winner in a screenshot.
Hash the state you sent
If you must not retain raw PII, store a hash of the exact filtered JSON plus the question SHA. You can still prove what was judged without keeping the email body forever — if counsel agrees. Hash what you POSTed, not a later-edited ticket. First-party evaluation is POST /v1/systemone; the body you hashed should match that call.
A Playground screenshot is insufficient. You need ids and SHAs. The evidence bundle glossary term is the name for this object, not a vendor product.
Retention
Your legal hold, not TypeSafe’s. Minimize what you stored in state to begin with. Do not treat hosted logs as your archive. Do not assume a marketplace door keeps the same payload you sent. Door id belongs in the row so a reviewer does not compare a boolean from one channel to a Noul from another.
Pair this template with governance: who may change criteria, who may lower floors, who signs the workpaper. For builders wiring the client, see the implementation checklist. For ship gates, see the launch checklist.
When this template is the wrong tool
Do not use an evidence bundle as a substitute for a SIEM, a case-management system, or a medical record. Do not dump unfiltered CRM into the bundle “for completeness.” Do not claim the hosted model learned from the override you stored — see the feedback guide. If you are replacing a mega-prompt, the migration guide is about actions, not exhibits.
Named failure modes that fight traces live on anti-patterns (the unauditable irreversible). When to use Jev is the scope test; this page assumes you already decided Jev is in-scope.
What this page does not claim
- Not a court-ready kit.
- Not official TypeSafe evidence guidance.
- Schema-safe answers are not factual correctness.
FAQ
Is a Playground screenshot enough?
No. You need object ids, question SHA, model id, and the probabilities JSON.
Can I omit probabilities?
Then you cannot audit abstain bands or dual-queue decisions.
Who owns retention?
Your legal hold. TypeSafe is not your archive.
Disclaimer
This is an independent unofficial site and is not affiliated with TypeSafe AI; official documentation is available at https://docs.typesafe.ai. Never treat jev.pro as TypeSafe official documentation. We do not sell, issue, or proxy API keys.
Open-cluster pages are independent field-guide notes. Replicas and third-party interfaces mentioned anywhere on jev.pro are not Jev and not endorsed. Hub: Open. Siblings: glossary evidence bundle, governance guide, glossary decision trace. Canonical: https://docs.typesafe.ai.