Jev governance guide
Governance for Jev is change control on questions, model pins, and who can enable auto-act. The model will not govern itself.
Unofficial. Not a GRC product. docs.typesafe.ai.
Minimum viable governance
- Named owner per question pack
- PR review on criteria (TypeSafe skill advice: humans edit)
- Production pin ≠
jev-latest - Dual-control to lower floors
- Quarterly sample of auto-actions
Evidence
Traces + question git history are the workpaper. See evidence templates.
RACI sketch (unofficial)
| Activity | Platform | Product | Risk/Legal | Jev (the model) |
|---|---|---|---|---|
| Edit criteria | R | C | C | — |
| Lower auto floors | A | C | C | — |
| Irreversible side effect | I | A | C | never |
| Vendor DPA | I | I | A | — |
R/A/C/I are yours to assign. The last column is the point.
What this page does not claim
- Not ISO/SOC certification.
FAQ
Does TypeSafe offer a policy console? Public docs emphasize request-shaped criteria, not a BRMS UI.
Who signs? Your control owner. Never Jev.
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: security guide, questions for legal, vs compliance checklists. Canonical: https://docs.typesafe.ai.
Sources
Public TypeSafe or adjacent documentation only. No private claims.