Behest: contracts first, AI second

Hi all,

Behest is a workflow for AI-written code: a human writes and approves the contract (examples, properties, declared effects), the AI implements it, and the contract is frozen by hash so it can’t be edited behind your back. Open questions go into an OPEN.md and the AI has to ask.

A second implementation is compared against the first on random input. Each disagreement points to a missing example. On two Elixir libraries this found real bugs within minutes.

It ships as Claude skills (Erlang and Elixir first, now also Go, Rust, Python, Java, Julia) with a heuristic effects scan: send, spawn, ets, io, time, random, state.

Repo: GitHub - ayarodionov/Behest · GitHub

I’d value opinions from people who think about OTP protocols and effects more than I do.