jevcore
A Jev decision layer for DeepSeek Harness and other MCP hosts, with explicit controls for provider use and data egress.
Added to Jevfast
How it uses Jev
The tools send caller-provided state and typed questions for yes/no, ranking, or claim checks; optional gates classify tool actions or large results. The mock provider is default, and live calls require opt-in.
What Jev decides
Route a support ticketExample answers · not a recorded Jev response · Source ↗
Question 1 · urgent
YOUR APP
INSTRUCTION
Does this convey urgency?
STATE
Documented example state: ticket text says “I was charged twice.”
JEV · NOUL
YesNo
Question 2 · team
YOUR APP
INSTRUCTION
Which team should handle this?
STATE
Documented example state: ticket text says “I was charged twice.”
JEV · CHOICE
- billing
- technical
App workflow
- Configure provider and egress
Start with the offline mock, then opt into live provider and individual features; the plugin reports the fields each enabled feature sends.
- Request a decision
The agent calls ask, rank, or check, or an enabled gate evaluates a matching event; Jev returns a typed answer.
- Apply the policy
The calling tool uses the answer; an undecided gate follows configured behavior, defaulting to ask.
Why it is interesting
The project makes data transmission part of the decision contract: features default off, startup logs enumerate fields sent, and undecided safety checks default to asking.