Native change-proof engine

The idea

One engine finds the change kinds from the diff and the outputs. Each kind needs its own typed proof: a UI recording, a real HTTP exchange, tests, a query, or exact document bytes. Only a person can waive a check, and a waived check shows as not passed.

The problem
A general 'checks passed' did not prove different kinds of change, and skipped checks could look like passes.
Why it matters
Each change shows its own proof. Proof that cannot be made here stays Unverified and neither passes nor blocks.
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.

  • 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

  • Platform proof for each requirement

    Each part of a requirement needs proof that the platform made. A saved document gets an automatic check of its exact revision and bytes. Semantic criteria need a recorded model review.

  • Visual evidence and regressions

    A visible change needs captures, and before-and-after pairs where asked. A service change needs a live check. A comparison fails on anything the change broke against the base.

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.