Requester instruction limits bind workers

The idea

A request's own ban on child tasks or decision tasks binds every worker and the escalation ladder. Text can only add a limit, and only an option the platform wrote can lift it.

The problem
The ladder opened a decision task that the request had forbidden.
Why it matters
Workers keep to the scope the requester set.
Where it stands
In production as of

Recorded evidence

  • Production · Both bans read from a reopen note
  • Production · AGT-68 reads both bans

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

  • Intent card with a hold rule

    Each request shows the requester what the organization understood and plans to do. Work waits only for high risk, a named approval, an ask-first setting or an open question.

  • Questions reach people last

    A judge answers a worker's question from earlier answers on record, or sends it back. Only seven kinds of decision reach a person: a customer release, spend over the ceiling, outside credentials, outside contact, a policy exception, reversing a person's decision, and legal matters.

  • The closed list

    Only seven decisions reach a person (customer release, spend over the ceiling, outside credentials, outside contact, policy exception, reversing a person's decision, legal matter), detected from structure; the rest settle inside the org on record.

    Recorded walkthrough

  • 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.

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.