VexJoy Agent
An agent workspace that routes plain-English requests to specialist agents, skills, and workflows, including an optional Jev-powered route.
Added to Jevfast
How it uses Jev
A user invokes /d with a request. Jev classifies it and judges whether the selected route preserves the requested outcome; dispatch proceeds only with an alignment receipt for that proposed intent.
What Jev decides
Validate proposed intent and routeExample answers · not a recorded Jev response · Source ↗
Question 1 · has actionable outcome
YOUR APP
INSTRUCTION
Does the request state an outcome that can be acted on now?
STATE
The state includes the user request, proposed intent, selected agent/skill/pipeline route, attached skills and fan-out agents, plus route validation context. Example selections are illustrative.
JEV · NOUL
YesNo
Question 2 · intent preserves requested outcome
YOUR APP
INSTRUCTION
Does the proposed intent preserve the requested outcome without changing its meaning?
STATE
The state includes the user request, proposed intent, selected agent/skill/pipeline route, attached skills and fan-out agents, plus route validation context. Example selections are illustrative.
JEV · NOUL
YesNo
Question 3 · intent preserves explicit constraints
YOUR APP
INSTRUCTION
Does the proposed intent preserve every explicit constraint, limitation, authorization, and requested scope?
STATE
The state includes the user request, proposed intent, selected agent/skill/pipeline route, attached skills and fan-out agents, plus route validation context. Example selections are illustrative.
JEV · NOUL
YesNo
Question 4 · route supports requested outcome
YOUR APP
INSTRUCTION
Does the selected route avoid conflicting with the requested outcome?
STATE
The state includes the user request, proposed intent, selected agent/skill/pipeline route, attached skills and fan-out agents, plus route validation context. Example selections are illustrative.
JEV · NOUL
YesNo
Question 5 · intent is too narrow
YOUR APP
INSTRUCTION
Does the proposed intent drop a material deliverable, surface, state, or success condition?
STATE
The state includes the user request, proposed intent, selected agent/skill/pipeline route, attached skills and fan-out agents, plus route validation context. Example selections are illustrative.
JEV · NOUL
YesNo
Question 6 · intent adds unrequested work
YOUR APP
INSTRUCTION
Does the proposed intent add a material goal, deliverable, or decision absent from the request?
STATE
The state includes the user request, proposed intent, selected agent/skill/pipeline route, attached skills and fan-out agents, plus route validation context. Example selections are illustrative.
JEV · NOUL
YesNo
Question 7 · route omits material scope
YOUR APP
INSTRUCTION
Is the selected route plainly unable to cover a material part of the request?
STATE
The state includes the user request, proposed intent, selected agent/skill/pipeline route, attached skills and fan-out agents, plus route validation context. Example selections are illustrative.
JEV · NOUL
YesNo
Question 8 · essential clarification needed
YOUR APP
INSTRUCTION
Would execution require the user to resolve an essential ambiguity, contradiction, or reserved choice first?
STATE
The state includes the user request, proposed intent, selected agent/skill/pipeline route, attached skills and fan-out agents, plus route validation context. Example selections are illustrative.
JEV · NOUL
YesNo
Question 9 · can proceed with proposed intent
YOUR APP
INSTRUCTION
Can work proceed because the request is actionable and intent and constraints are preserved?
STATE
The state includes the user request, proposed intent, selected agent/skill/pipeline route, attached skills and fan-out agents, plus route validation context. Example selections are illustrative.
JEV · NOUL
YesNo
App workflow
- Invoke the router
The user submits a plain-English task through /d.
- Classify and verify intent
Jev classifies the request and checks the proposed route's restatement against the requested outcome.
- Dispatch with receipt
The router proceeds only when it has an alignment receipt for the exact proposed intent; judgments are recorded without raw request text.
Why it is interesting
The route is checked against the user's intended outcome before dispatch, and alignment judgments are recorded without retaining raw request text.