Evoke: route a sentence to installed programs
Jev chooses installed command recipes and closed input values; ordinary code builds a visible execution plan and enforces confirmation rules.
The public Jev adapter and current capability documentation were inspected on October 1, 2026. Each installed reflex declares its inputs and effects. Jev selects recipes and input candidates, while code controls execution, clarification, and confirmation. The working CLI and SDK operate on a single machine; the distributed multi-machine examples are explicitly future illustrations. No benchmark or autonomous-execution claim is asserted here.
# evoke **Software, by reflex.** Natural-language commands for small programs you install. A reflex is a small program you install and ask for in your words. Type one sentence, and `evoke` reads it against every reflex you installed. It picks the ones the sentence asks for and fills their inputs from your words or your own lists. It shows the plan before anything runs. It runs when it is sure enough for what the program changes, asks when something is missing or unclear, and always asks before anything that cannot be undone. **Built to an exceptional standard.** Three rules define it, and [QUALITY.md](QUALITY.md) shows how each is kept. - **Every detail is measured.** Tests check how `evoke` decides, case by case, and what it prints, word for word. - **Every boundary is clear.** Each part has one job. The core that decides never touches a file or the network. - **Nothing is added on a hunch.** Every feature is studied, and its options weighed, before it is built. <p align="center"><a href="https://evoke.build/film.html"><img src="assets/film.jpg" alt="Software, by reflex. A film about where evoke is going." width="640"></a></p> ## Where evoke is going Take back control. Keep the intelligence. Every system people act through ships reflexes: small programs with a manifest anyone can read. You state a goal in one sentence, and `evoke` turns it into a plan across those reflexes, one you can read before anything runs. Lookups fire together. Changes wait their turn. Every value comes from a closed source, every step carries its probability, and each step that cannot be undone waits for the person it belongs to. Then the plan crosses machines. Each step runs where its program, its keys and its approver live. Every call is signed, every machine checks it against its own
