Review threads and CI on the exact head

The idea

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.

The problem
Agents ignored comments, or finished on a stale or red head.
Why it matters
The worker answers review and CI on the commit that was checked.
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.

  • Engineer pipeline with stage shares

    Work follows an engineer's pipeline, and each stage gets a share of the time and cost. Review is one plan review and one holistic diff review, within about 10% of spend.

  • Work review instead of code review

    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.

  • Internal knowledge first, then specialists

    A worker needs internal evidence before its first web search or question: a knowledge or memory read, a colleague's answer, or a recorded miss. After that it can consult read-only specialist sub-runs, search the web and, with approval, ask an outside expert.

  • Revert proof

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

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.