Jev adoption roadmap
This roadmap is your adoption sequence for putting System One into production. It is not TypeSafe’s product roadmap, changelog, or a promise of features from jev.pro. If you want vendor plans, read TypeSafe — we will not invent them. Independent. docs.typesafe.ai.
Independent angle (cover, do not clone)
Win delta: builder adoption stages (shadow → canary → operate) instead of a cloned changelog or “is Jev down” microsite. Status/changelog intent is covered on versioning and monitoring, not here.
Question and context
Teams stall in two places: endless Playground tours, or a big-bang cutover on jev-latest. The path that works looks like any other decision service: contract, pin, harness, shadow, canary, abort.
Core concepts
| Stage | You can demonstrate | You refuse |
|---|---|---|
| Discover | One traced call; you can explain Choice vs Noul | Selling the project as “an LLM” |
| Design | Action space + atomic questions (design checklist) | Mega-oracle Choice |
| Implement | Pinned id, error map, traces (implementation) | Keys in git; door-id mixups |
| Prove | Gold JSONL + policy metrics (evaluation) | Vendor 193× as your slide |
| Shadow | Logs beside the legacy router | Customer-visible change |
| Canary | One low-blast slice auto-acts (launch) | Irreversible without fail-closed |
| Operate | Weekly loop (playbook) | Criteria hotfixes without replay |
Learning sequence for humans: learning path. Org hats: team roles.
Practical approach
Pick one vertical pack from use cases after Discover — not five. Promote the triple (questions@sha, jev-1.13.0, door). If OpenRouter says typesafe/jev-1.13 and first-party says jev-1.13.0, those are different strings; record both.
We will not put dates on TypeSafe releases. Alias moves are theirs. Your roadmap dates are your promotions.
Risks and trade-offs
Publishing an internal “Jev roadmap” that lists hoped vendor features trains the org to wait. Build on public docs only. Replicas and unofficial UIs are not Jev and not endorsed.
What this page does not claim
- Not TypeSafe’s roadmap or changelog.
- Not a delivery timeline from jev.pro.
- Not official.
FAQ
Where is the vendor changelog? SDK changelogs and the models page on TypeSafe. We do not scrape a rival changelog.
Is this a paid Pro roadmap? No. “Pro” means production craft (NARRATIVE.md). There is no jev.pro paid tier on this page.
What if we need a status page? Monitoring guide — canary your door; do not clone “is Jev down.”
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: learning path, playbook, launch checklist. Canonical: https://docs.typesafe.ai.
Sources
Public TypeSafe or adjacent documentation only. No private claims.