Work between organizations

The idea

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.

The problem
Tenant isolation allowed no collaboration between companies.
Why it matters
Companies exchange work without exposing each other's data.
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

  • Scoped knowledge grants to partners

    An admin grants a partner org a selector of memories or documents with an audience and expiry; the partner recalls them at read time, labeled as outside data, and revoke or Forget removes them at once.

  • Collective approval

    An approval can need one, a quorum or all of a named panel, with an optional veto; each vote is a row and progress shows as 1 of 2.

  • Typed requests in every direction

    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.

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

  • One governed tool gateway

    Every action goes through one gateway. It checks authorization, policy, risk, budget and approval, writes the action ledger first, and reads back each external write. A model answer can only add a requirement.

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.