Acceptance criteria as executable checks

The idea

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.

The problem
Someone can claim a criterion written in prose is met when nothing ran.
Why it matters
Work cannot be done while a check fails or did not run.
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.

  • Revert proof

    A new or changed test must fail when the fix is reverted.

  • Completion truth gates

    New tests must run here or have a trace for each assertion. Claimed behaviour must be tested, and the same bug elsewhere fixed or ruled out. Planned changes must exist, steps tick only on evidence, and spend over budget needs a recorded decision.

  • A receipt for every task

    Every finished task gets a sealed receipt: what was done, which checks ran and how they ended, the time and the cost, built from records the platform already keeps.

    Recorded walkthrough

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.