Escalation routing and reply resume

The idea

A question goes to its addressee wherever they can be reached: a ticket, a pull request, Slack, Teams or a direct message. A reply there resolves it and resumes the item, and an answer given on the platform is posted back.

The problem
Questions sat on a screen that nobody watched.
Why it matters
People answer where they already work, with retries and provenance on each answer.
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.

  • Authority ladder: the owner is the last resort

    A question goes to the asker's manager worker, then the CEO, which decides from the org profile and record; a person gets it only for an owner reason, and their answer becomes a precedent.

  • Evidence-gated questions and settled decisions

    A blocking question is refused until research cites a tool result, and asking again about a settled decision needs new evidence. A decision that arrives after a completion claim sends the work back.

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.