Jev team roles
Roles on jev.pro are hats, not headcount. A five-person team wears several. The point is that someone named owns each failure mode. Independent. Not TypeSafe careers. docs.typesafe.ai.
Independent angle (cover, do not clone)
Win delta: hat-based RACI mapped to Explain/Integrate/Compose/Compare/Operate, plus audience pages. We do not clone a staff-aug landing page or rival “team” IA.
Question and context
Jev does not come with a customer-success squad from this site. Your people still write questions, label gold, and take the heat when an irreversible action ships. Official docs say good questions are snap judgments — that is a product writing skill, not only an ML skill.
Core concepts
| Hat | Typical owner | Writes | Signs |
|---|---|---|---|
| Question author | Product / domain | instructions, criteria |
Snap-test: a knowledgeable human could answer in seconds |
| Policy owner | Risk / counsel / ops | Which actions are irreversible | Fail-closed default |
| Platform owner | Eng | Door, pin, retries, traces | response.model canary |
| Eval owner | Data / QA | Gold JSONL, CI gates | Promote / abort |
| Reviewer | Human queue | Overrides + reason codes | Dual-review on disagreements |
| App owner | Service team | Graph in code | Side effects (CRM, TMS, ATS) |
Audience deep-dives (already on this site): product, platform, operations, data, enterprises, startups.
Practical approach
Put the hats in CODEOWNERS (or equivalent) on the questions module. Do not let a weekend Slack message change production criteria. Agent-skill workflows still need a human reviewer for criteria — treat that as a role, not a chatbot.
Risks and trade-offs
Inventing six new job titles is worse than no roles. If you only name two people, name policy owner and platform owner. Hiring “a Jev engineer” does not remove jaggedness or legal duty.
We do not sell staffing. We do not issue keys.
What this page does not claim
- Not official TypeSafe roles.
- Not salary or hiring-volume data.
- Not a managed service.
FAQ
Who talks to TypeSafe? Your vendor relationship — not jev.pro. We are unofficial.
Can one person wear every hat? Yes at the start. Write the hats down so the second person inherits them.
Where is the operating cadence? Operating model.
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: operating model, success metrics, product teams. Canonical: https://docs.typesafe.ai.
Sources
Public TypeSafe or adjacent documentation only. No private claims.