Jev. Rethinking AI guardrails.

Jev accepts context and questions defined in natural language, then returns typed decisions and probability distributions. Multiple independent questions can be evaluated in parallel within one request. Software gets separate signals it can use to apply policy.

Classification is not new. The interesting combination is flexible criteria, structured outputs and an emphasis on speed. For guardrails, that could make more frequent, focused checks practical. The architectural opportunity is to move control closer to each employee action, with enough context to make a useful decision and little enough delay to preserve the experience.

A structured distribution gives policy code more to work with than a single label. Different checks can have different thresholds, reflecting the consequences of a missed violation or an unnecessary block. Ambiguous results can trigger deeper evaluation. The security team still defines the action; the model supplies a signal. This makes the trade-offs explicit and gives teams something concrete to evaluate against their own policies.

I see the strongest architecture as a combination of specialised controls. Deterministic detectors handle known patterns and explicit restrictions. Contextual models answer bounded questions about meaning. Policy code applies the decision, and enforcement must remain reliable when a model is uncertain or unavailable. Each layer has a defined job, and the protection system must be tested as a whole.

Privacy belongs in that architecture from the start. A guardrail may inspect precisely the information it is protecting. Processing location, access, retention and training use are engineering requirements. Any model considered for that role needs a secure deployment path and data-handling arrangements that meet customer requirements. A faster decision has value only within a protection system customers can trust.