A solicitor-approved send in eve

A send_enquiries tool that takes the whole list for a matter, waits for approval on every call, lets anyone deny but only a verified solicitor approve, re-checks the requester's access in execute and sends through a fake outbox that refuses a repeated idempotency key. A development-only signed token stands in for real sign-in, so both paths can be tried locally.

Back to the exercise

Before you start

Before you start:Install Claude Code Node.js, pnpm and TypeScript Durable agents with eve Get an OpenRouter key Local models with Ollama

This exercise calls a model. Run it either way

Any model through OpenRouterOne key for Claude, GPT, Gemini, Llama and more. Pay per token, with a credit limit.A local open-source modelFree and private with Ollama. Weaker on hard tasks.

Which should I pick? →

The checkpoint is three separate controls, and the exercise is about keeping them separate. The request policy (always()) decides that every call waits for a person. The response policy decides who may answer: anyone may deny, only a principal whose verified role is solicitor may approve. execute then does what approval can't: it checks that the requester is on the matter, and it sends with an idempotency key that the outbox enforces. The decision that matters most is where the role comes from: route auth, never the message or the tool input. Locally that's a signed development token that only eve dev accepts.

Answers Lesson 5: Human approval for high-stakes actions

Step-by-step answer

Core 60–90 min8 steps