Open· Last updated

Jev migration guide

Migration means moving decisions off a mega-prompt or a frozen classifier onto Jev questions — not moving off TypeSafe’s undocumented “v0 API” (there isn’t a second public evaluation route in the reference we used).

Unofficial. docs.typesafe.ai.

From prompt-only

Extract enums → Choice criteria. Extract yes/no → Noul. Keep drafts on the LLM. Dual-run and compare actions.

From a trained classifier

Keep it if volume is huge and labels frozen. Otherwise: labels-in-request. See vs classifiers.

Between doors

Rewrite model ids and boolean vs noul. Never lift-and-shift JSON.

Shadow mode

For two weeks, write Jev’s action next to the old prompt’s action. Do not act on Jev. Measure disagreement. Only then allow Jev to act on the high-agreement, low-stakes slice.

Door migrations are schema migrations. Boolean vs Noul has already bitten people — see the channel matrix.

What this page does not claim

FAQ

Big-bang auto-act? No. Shadow mode, then review-heavy, then narrow auto.

Downgrade path? Keep the old prompt behind a flag for a sprint.

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: versioning guide, vs prompt only systems, implementation checklist. Canonical: https://docs.typesafe.ai.

Sources

Public TypeSafe or adjacent documentation only. No private claims.