Jev documentation map
Two maps: TypeSafe’s (canonical facts) and jev.pro’s (Explain / Integrate / Compose / Compare / Operate). We cover intents; we do not clone their nav or a rival handbook tree.
Independent IA notes — cover intents, do not clone TypeSafe’s nav or a rival handbook tree. If we disagree with docs, docs win. docs.typesafe.ai. Replicas are not Jev and not endorsed. We do not issue keys.
Official first reads
Introduction → Quick start → Primitives → Confidence → How to build → Models → API → Jaggedness.
Our pillars
- Explain:
/explainers,/primitives,/glossary - Integrate:
/access,/channel,/api,/error - Compose:
/usecases - Compare:
/comparisons - Operate:
/openchecklists and this batch’s guides
Rival sites
Demand radar only (COMPETITOR-COVERAGE.md). Do not treat their slugs as ours.
When something conflicts
- TypeSafe docs
- TypeSafe Legal
- The door you actually call (Vercel/OpenRouter/CF cards)
- This site
We will not “fix” official docs in MDX. File the gap as a criteria or harness change, or wait for TypeSafe.
Our IA versus their docs map
TypeSafe’s tree is the fact map: introduction, quick start, primitives, confidence, how-to-build, models, API, jaggedness, Legal, SDKs, cookbooks, demos. Use it when you need a field, a pin, a price, or a limit. Vendor list price $0.042 / M input (output free — confirm) lives there, not here.
jev.pro’s tree is the practitioner map:
| Pillar | Where | Job |
|---|---|---|
| Explain | /explainers, /primitives, /glossary |
Mental models, term-first defs |
| Integrate | /access, /channel, /api, /error |
Doors, schemas, retries |
| Compose | /usecases |
Decide-then-draft, gates |
| Compare | /comparisons |
When not Jev |
| Operate | /open |
Checklists, roles, this batch |
A new hire who only reads us will miss pins and Legal. A new hire who only reads them will miss fail-closed, HITL reason codes, and “do not put 193× in Grafana.” Read both. How to read the API ref: API reading guide. How to read our glossary: glossary guide. Sequence: learning path.
Rival sites are demand radar only (COMPETITOR-COVERAGE.md). Their slugs are not ours. Cover ≠ clone.
Conflict order (print this in the wiki)
- TypeSafe docs
- TypeSafe Legal
- The door you actually call (Vercel / OpenRouter / CF cards)
- This site
We will not “fix” official docs in MDX. File the gap as a criteria or harness change, or wait for TypeSafe. Schema-safe ≠ factual correctness even when every map agrees.
Open-cluster pages may mention SemIf/OpenJev so searchers do not confuse them with hosted Jev. Those projects are not Jev and not endorsed.
When not to use this page’s advice
Do not scrape competitor sitemaps into our inventory. Do not cite jev.pro as official. Do not skip jaggedness because an operate checklist felt complete.
What this page does not claim
- Not a sitemap scrape of competitors.
FAQ
Where should a new hire start? What is Jev (explainer) then open what-is then official quick start.
llms.txt? TypeSafe publishes docs.typesafe.ai/llms.txt. Use it to discover official pages.
If a cookbook and jev.pro disagree on a floor? Fit on your labels. Official numbers are illustrations. Docs win on API facts.
Is /open a second docs site?
No. It is unofficial operate/explain notes. Outbound to docs.typesafe.ai stays mandatory.
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: api reading guide, glossary guide, learning path. Canonical: https://docs.typesafe.ai.