Ticket moves and completion reports

The idea

The runtime moves the source ticket at the events that the team's workflow names, never back or sideways. It posts one template report (outcome, evidence, caveats, what needs a person) to each place that asked.

The problem
Tickets moved outside the team's workflow, and people had to open the platform to see outcomes.
Why it matters
Tickets follow the team's process, and the outcome reaches the place the request came from, once.
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

  • Rulebook mined from history

    Commits, PRs, reviews, tickets, tests, CI and code are mined into rule candidates with evidence and scope. Accepted rules become checks, tested first against past changes. A rule that catches nothing in 90 days goes to its author to retire or keep.

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.