Typed requests in every direction

The idea

Workers and people ask each other typed questions (review, information, decision, help, handoff) peer to peer, up or down, with due times, defaults, redirects and an inbox.

The problem
Peers had no typed channel; questions went back to the requester.
Why it matters
Questions settle inside the organization.
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.

Where it lives in the product

  • Define deeply before building

    Before building, the worker defines what, why, for whom and how. It checks fit, knowledge and authority, and answers its own questions with research and with colleagues.

  • Employees ask for resources

    An employee asks its manager for headcount, budget, a tool, a model or access with evidence; a queue full for 3 days raises a headcount request by itself.

  • Work between organizations

    Two orgs connect only after both owners accept; one gateway employee per side sends and receives typed partner requests, partner text is data, cost policy applies and either side can revoke.

  • CEO front door over a worker hierarchy

    The operator talks to one CEO worker; department heads and workers sit below it, and each level's budget and tool limits bind its whole subtree.

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