Deterministic first: checks the worker builds

The idea

The worker turns intent into code that the runtime runs every time: acceptance checks, rule checkers, procedure scripts, workflow state machines and stage gates.

The problem
A model can forget, drift or skip a step.
Why it matters
Nothing depends on the model's memory.
Where it stands
In production as of

A step-by-step replay of this idea is not published yet. The library adds one when a recorded run shows it.

  • Acceptance criteria as executable checks

    At plan time, each acceptance criterion maps to a test, script, query, HTTP check or screenshot check. Verification runs all of them in each round.

  • Rules as checks

    A team rule that can be checked gets a checker for a pattern, a name, a structure, a command or a benchmark. The checker runs on the change before a pull request, on each push, before the worker finishes the task, and during verification.

  • Procedures as scripts

    A tool sequence that succeeded on several finished items of one task class becomes a tested template. A person approves its hash, it runs through the gateway, and it is demoted when it fails.

Turn the numbers into shipped work.

Crewshal runs these choices for you: a persistent AI worker with memory and rules, on your Claude and Codex subscriptions.