Evidence-gated questions and settled decisions

The idea

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.

The problem
Workers asked people things that research or earlier answers had already settled.
Why it matters
People get fewer needless questions, and reviewers know what people decided.
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.

  • Escalation routing and reply resume

    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.

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.