shipwithjev

Catalog / Robotics & devices

0562GitHub

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-build/evokeREADME ↗
# 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 

Also filed under Robotics & devices

  1. 0608

    Jev Driver: Jev behind the wheel

    I put Jev behind the wheel. A small vision model in your browser describes the road. Jev, TypeSafe’s fast, cheap classifier, decides what to do. Does it stop for a child? A dog? A teddy bear? Drop them on the road and find out: https://t.co/ccWsmPEZaF

    @mrza_ch · Robotics & devices

  2. 0601

    Machine fault diagnosis with Jev

    Replays real compressor telemetry through an emulated Modbus device, spots anomalies in plain code, then asks Jev which fault from the manual explains them.

    Michele Lacorte · Robotics & devices

  3. 0501

    Jev-controlled traffic light

    I made Jev control a traffic light using 𝘯𝘦𝘢𝘳 𝘳𝘦𝘢𝘭-𝘵𝘪𝘮𝘦 𝘵𝘳𝘢𝘧𝘧𝘪𝘤 𝘧𝘦𝘦𝘥𝘴, obviously a simulation. It cost me less than a cent to run, and the best part was watching it decide to do nothing when it wasn't sure. Wrote an article about it! Link in reply 👇

    @notifykamalraj · Robotics & devices · < $0.01 total

  4. 0452

    Smart-home assistant fast path

    An open-source Alexa-like assistant calls Jev before its LLM to identify device-control requests, choose the device and action, and switch hardware immediately.

    u/unbenannt1 · Robotics & devices