The envy-graph procedure (also called the envy-cycles procedure) is a procedure for fair item allocation. It can be used by several people who want to divide among them several discrete items, such as heirlooms, sweets, or seats in a class.

Ideally, we would like the allocation to be envy-free (EF). i.e., to give each agent a bundle that he/she prefers over the bundles of all other agents. However, the items are discrete and cannot be cut, so an envy-free assignment might be impossible (for example, consider a single item and two agents). The envy-graph procedure aims to achieve the "next-best" option -- envy-freeness up to at most a single good (EF1): it finds an allocation in which the envy of every person towards every other person is bounded by the maximum marginal utility it derives from a single item. In other words, for every two people i and j, there exists an item such that, if that item is removed, i does not envy j.

Envy-graph procedure

The procedure was presented by Lipton and Markakis and Mossel and Saberi and it is also described in .

Envy-graph procedure

Assumptions

The envy-graph procedure assumes that each person has a cardinal utility function on bundles of items. This utility function has to be monotone (the utility of a set is at least as large as the utility of its subsets). However, it does not have to be additive. I.e, the items are not assumed to be independent goods.

Envy-graph procedure

The agents do not have to actually report their cardinal utility: it is sufficient that they know how to rank bundles.

The procedure

Order the items arbitrarily. While there are unassigned items: Ensure that there is an unenvied agent - an agent that no other agent envies. Give the next item to the unenvied agent. In step 2, if there is no unenvied agent, it means that there is a directed cycle in the envy graph - a directed graph in which each agent points to all agents he envies. Cycles can be removed by cyclic exchange of bundles. After all cycles are removed, the envy-graph must have a node with no incoming edges; this node represents an unenvied agent.

The resulting allocation is not necessarily EF, but it is envy-free except one item. This is true not only in the final allocation but also in each intermediate allocation: since an item is always given to an unenvied agent, the envy of all other agents after that allocation is at most a single item.

Run-time analysis

Suppose there are m items. Each allocation of an item adds to the envy-graph at most n-1 edges. Hence, at most edges are added overall. Each cycle-removal removes at least two edges. Hence, we need to run the cycle-removal step at most times. Finding a cycle can be done in time using e.g. depth-first search. All in all, the run-time is .

Examples

In these examples the preferences go from 1-3 where the higher the number the higher the preference. Also a, b and c are people while X, Y and Z are objects.

1) With 3 people and 3 objects, every possible allocation will be a different result. This case happens when each of the three people have the same preferences. There are six different ways to allocate the objects:

In the beginning because no one has anything then all of them are unenvied agents and this is the same in all the cases. In case of a tie, we break ties between unenvied agents in lexicographic order.