Work review instead of code review

The idea

Other employees verify a pushed commit in a fresh checkout, check and release the candidate, and watch production with rollback. Code writes 'ready' only when every stamp is current. A rule set picks each repository's review mode from its indicators.

The problem
Human code review is slow, and a builder that checks its own work proves little.
Why it matters
Each stamp holds the evidence for one commit, and a new commit voids the later stamps.
Where it stands
Partly built as of

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

  • Main-line CI watch

    The build stage owner reads the CI result of each watched branch head through the gateway. A red head opens one urgent incident, and a green head records the recovery time.

  • Independent verifier

    The platform checks an AI worker's pull request in its own container, out of the worker's reach, and approves it only when a new test fails without the fix.

    Recorded walkthrough

  • Nine-stage lifecycle; the builder never judges itself

    Each item records which stages apply (context, architecture, design, spec, tests, build, standards, verification, delivery), why, who decided and which gate enforces each. A verdict from the builder's own context counts as Unverified.

  • Review threads and CI on the exact head

    Each actionable PR comment becomes a plan step that stays open until answered. Red CI on the exact head sends the work back. A merge is compared with what was verified.

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.