Anna Agent
The decision input is constrained to task-relevant candidate fields, candidate IDs are remapped before sending, and abstention is an explicit option when the evidence does not distinguish a suitable assignee.
Added to Jevfast
How it uses Jev
The harness-service assignee decision path sends a bounded project/task description and up to 20 candidate records to Jev. It asks one Choice question named assignee, offering anonymized candidate IDs plus abstain; the result is checked against that closed set before local candidate IDs are restored. This path supports assignment suggestions, with the app managing decision requests and adoption separately.
What Jev decides
Crew assignee suggestionExample answers · not a recorded Jev response · Source ↗
Question 1 · assignee
YOUR APP
INSTRUCTION
Choose one candidate only when the provided task and candidate fields support that choice; otherwise choose abstain.
STATE
Representative two-candidate input: project_goal “Restore checkout”; task {title: “Fix checkout outage”, description: “Customers cannot place orders”, role_required: “backend”, acceptance_criteria: null}; candidates [{id: “member-a”, role: “backend”, kind: “human”}, {id: “member-b”, role: “backend”, kind: “agent”}]. Provider body remaps these to c1 and c2.
JEV · CHOICE
- c1
- c2
- abstain
App workflow
- Validate and bound input
Validate allowed fields, candidate IDs and kinds, maximum candidate count, and serialized state size.
- Ask Jev
Send project and task context with anonymized candidate IDs and the assignee Choice question.
- Validate response
Accept only a choice among supplied local candidate aliases or abstain, then map the selected alias back to its local candidate.
Why it is interesting
The decision input is constrained to task-relevant candidate fields, candidate IDs are remapped before sending, and abstention is an explicit option when the evidence does not distinguish a suitable assignee.