← Research

Behavioral envelopes (work in progress)

Work in progress. A framework we are developing for checking whether an agent acting for a person stays within what the organization and the person accept. Diagrams and terms will change.

Defining behavioral envelopes: Provider | Organization | Individual

Suppose an agent books a work trip for a person and handles what comes up along the way. Each envelope wants something different. Here are four things the agent could be asked to do.

  1. 1An economy flight on the person's preferred airline, with a window seat

    Provider: allows · Travel policy: allows · Person: wants

    Inside all three envelopes, so the agent acts.

  2. 2Business class

    Provider: allows · Travel policy: forbids · Person: wants

    Stop and escalate. What the person wants does not override the travel policy.

  3. 3The cheapest fare, a red-eye flight

    Provider: allows · Travel policy: allows · Person: does not want

    Ask the person first.

  4. 4The airline loses the bag. File the claim for more than was in it

    Provider: refuses (fraud) · Travel policy: forbids · Person: wants

    Stop. The travel policy forbids false claims, so this holds whichever model is running. The provider's refusal is a backstop.

The three envelopes overlap, and they can pull in different directions.

ProviderOrganizationIndividualacceptable1234
Provider
What the model will not do, no matter what anyone allows. This includes safety and legal limits, such as no fraud. These limits can differ from one model to the next, so they work as a backstop. An organization may allow something that the model still refuses to do.
Organization
The rules of the organization where the agent works. Here, that means the travel and expense policy, such as economy only and honest claims.
Individual
What the person wants and expects from the agent. These are their preferences, such as a window seat and no red-eye flights.

Acting on someone's behalf means acting where all three overlap. The person's say-so does not let an action go outside the other two.

If an outcome is inside both the organization's and the person's envelopes, the agent acts. If the organization allows it but the person does not want it, the agent asks the person first. If the person wants it but the organization does not allow it, the agent stops and escalates. If neither does, the agent stops. No one can approve a false claim. The organization's policy forbids it, so the agent stops whichever model is running. The provider's refusal is a backstop, not a substitute for that rule.

So what does it really mean to work on someone's behalf?

The walkthrough below takes one ordinary request through these envelopes, step by step.

Walkthrough: a maintenance manager asks an agent to delay an inspection

Prerequisite, outside the flow: the agent acts for the organization and the maintenance manager, with authority from each.

  1. 1The requestThe manager asks the agent to delay the inspection. The request includes an implied mission to do it within the organization's policy and the manager's preferences.
  2. 2Allowed?Is this manager allowed to ask for a delay, and is the agent allowed to do it for them? If not, the agent declines or hands the task to a person.
  3. 3Organization policyWould this be the 3rd delay or more? If not, the agent submits it. If so, the officer must approve it, and filing without the officer's approval breaks the rule.
  4. 4Manager's preferenceThe manager wants to be asked before the request goes to the officer. Going straight to the officer is allowed by the organization, but not by this manager.
  5. 5Where it endsAfter being asked, the manager either sends the delay to the officer, who approves or declines it, or has the maintenance done now. If the manager says to skip the officer and file anyway, that breaks the rule. The agent stops and tells the manager.
1The request 2Allowed? 3Org policy 4Manager's preference 5Where it ends provider floor: the model refuses (nothing in this case reaches it) ORGANIZATION'S ENVELOPE OUTSIDE THE ORG'S ENVELOPE MANAGER'S ENVELOPE specification / preference PERSON ONLY THE REQUEST The manager asks the agent: delay the inspection. It would be the 3rd delay. THE MISSION, STATED Submit the delay request within the org's policy and within the manager's preferences. The request never says this; it is always implied. Allowed? Would this be the 3rd delay or more? no: decline, or hand to a person yes no yes straight to the officer ask the manager first the manager decides delay it officer decides approves declines do it now manager says: skip the officer yes, but files without the officer or recategorizes it to dodge the count breaks the approval rule breaks the same rule Filed; no officer needed Auto-escalated, manager not asked Delay filed Stays due; no delay Maintenance done now Agent stops; tells the manager Breaks the rule: filed with no officer approval
Read the drawing from left to right. Solid lines stay inside the organization's envelope. Dashed red lines cross outside it. Scroll sideways to see all of it.