Latest post
The authority boundary: what agents can and cannot do
An agent's authority belongs in a versioned record, not its prompt. See how Synedrix OS uses recommend, approve and execute scopes to bound what agents do.
ReadTip: select any text on this page to bring up the Ask tooltip and question the Synedrix OS assistant about it.
Definition
What Jev is
Jev, from TypeSafe AI, is a System One decision model offered as an API: send it a piece of state and named questions, and it returns one typed answer per question (a label, a score, a yes-or-no probability, or a location in an image) with a confidence, and no generated text.
It needs no hardware of your own, which makes it the fastest way to put a decision model in front of real questions.
Context
What it is normally used for
How Jev is used generally, before Synedrix OS enters the picture.
- Routing requests to the right queue, agent or model without an LLM call
- Checking inputs, tool calls and generated answers before they are used
- Rubric scoring where a probability is more useful than a paragraph
In Synedrix OS
What it owns, and what it does not
Every platform in the stack has a non-overlapping responsibility. The boundary is as much a part of the design as the capability.
Owns
- Nothing in production: called only from LAB-003's isolated environment, and only ever with synthetic or already-public data
Does not own
- Whether any action is permitted
- → Policy Guard and the HITL Gateway; a decision model's confidence is evidence, never permission
- The default decision model, if one is ever adopted
- → Not Jev: a hosted model cannot serve an air-gapped deployment
Rationale
Why Jev
The reference point Laya is measured against
LAB-003 asks both models the same questions on the same decisions. Jev sets the bar; the open question is whether a self-hosted model can reach it.
Never the default
An air-gapped deployment allows no outbound model call, and a hosted model cannot run inside one. So Jev can never be the default decision model for Synedrix OS.
Licensing
Licence position
LICENCE
Proprietary managed service. The model runs only as TypeSafe AI's hosted API. The Python client, typesafe-sdk, is MIT-licensed, confirmed from its package metadata. A hosted, proprietary model cannot serve an air-gapped deployment. Source
Common questions
Jev questions, answered
Short, citable answers drawn from this page.
What role does Jev play in Synedrix OS?
Jev (Decision model, managed API) is mapped to Lab component: no OS layer in Synedrix OS. The managed reference point: the quickest way to measure what a decision model can do, and never the default.
What does Jev own in Synedrix OS?
Jev owns: Nothing in production: called only from LAB-003's isolated environment, and only ever with synthetic or already-public data.
What does Jev not own in Synedrix OS?
Jev does not own: Whether any action is permitted (owned by Policy Guard and the HITL Gateway; a decision model's confidence is evidence, never permission); The default decision model, if one is ever adopted (owned by Not Jev: a hosted model cannot serve an air-gapped deployment).
The full reference page, with the operating model, deployment detail, and links to every canonical specification this platform touches, lives in the documentation repository, which is private while the platform is being built.
Latest post