TypeSafe Jev playbook (unofficial)
This playbook is jev.pro’s operate pillar: checklists you can run in a review, not a story-shaped “how to build with System One” essay. TypeSafe’s official narrative remains how to build. We are independent and unofficial. We do not issue API keys.
Path
| Stage | Page | Exit gate |
|---|---|---|
| Design | Design checklist | Action space + atomic questions written |
| Implement | Implementation checklist | Pinned model, traces, error map |
| Launch | Launch checklist | Harness + fail-closed + labeled claims |
| Compose | Intent routing, guardrails, RAG filter | Code owns side effects |
| Compare | vs classifiers, vs agents | You know when not to use Jev |
Operate loop (weekly)
- Re-fetch the channel matrix (model ids, promos, 32k vs 64k cards).
- Diff
response.modelin logs — catch silent alias moves if someone shippedjev-latest. - Sample handoff traces; add misses to the gold file.
- Re-read TypeSafe jaggedness if you changed criteria.
Production gates we will not skip (SEO-GEO)
- English public pages; unofficial disclaimer; outbound https://docs.typesafe.ai
- One intent per URL
- Vendor 40×–200× / $0.042 figures labeled
- No key CTAs
- Cover rival intents, do not clone their slugs or voice
What this playbook is not
Not official TypeSafe. Not a paid “Pro” tier. “Pro” here means production craft (see NARRATIVE.md in the repo).
Hub: Open. Official: docs.typesafe.ai.
Sources
Public TypeSafe or adjacent documentation only. No private claims.