Coder: skills 9, 1; coordination 0.75. Writer: 1, 9; 0.75. Coordinator: 1, 1; 0.97.
A model of coordination in multi-agent systems, whether the agents are human, artificial or a mix. The formula is the worked example from Imas, Koh and Legg, “Organizing Intelligence” (2026). They apply it to firms and the economy, but nothing in it is specific to firms: it describes any team that divides work and has to coordinate. Build a team from coders, writers, coordinators and AI copies, then see how output per member changes as the team grows.
Coder: skills 9, 1; coordination 0.75. Writer: 1, 9; 0.75. Coordinator: 1, 1; 0.97.
Teams of 1 to 16 copies of one model pick and solve items from a shared board with no communication (run 16 November 2026, four groups per point). The fitted exponent is how output grows with team size, which is what ȳ* is in the formula above for a large team. “Use in model” sets an all-AI team to that value.
Items are independent, so the best possible is 1 at every size and the exponent cannot pass 1. The blue line is the formula's coordination term at your team's current ȳ*: move the coordination slider to fit a measured line.
Valuable items unlock for everyone after three agents research their family. A fixed cost shared by all lets output per agent rise with team size, if the team divides the research.
Limits: the allocation task measures only losses, so it shows how close a team gets to the threshold of 1, not whether it can cross it. Reading its exponent as ȳ* is a modelling choice: the paper's friction is attention split among colleagues who talk; here it is collisions among agents who cannot. Four groups per point, two models from one provider, trivial items.
Dividing work helps, then levels off. Coordination helps or hurts depending on whether ȳ* is above or below 1. Their product is the scale effect.
Competence L is the harmonic mean of the team's average coding and writing skill, so the weaker skill holds it back. Curves join skill pairs with equal L.
The formula, the three human types, φ = 7/4, the AI rental cost of 1 per copy and the deep-market price of 0.3 are the paper's (Section 2). The authors call this functional form “a little ‘ad hoc’”; their general model replaces it with a scaling exponent γ. The human cases here reproduce their numbers: 5.0 per coder at size 6, 13.8 for a coder–writer team, 13.0 at size 7 with a coordinator. Where the paper says “firm” and “worker”, this page says “team” and “member”.
The paper calls its unit a firm and uses the model to study market structure and wages. The model itself has no ownership, contracts or liability in it, only members with skills, a size and a coordination cost. So this page reads it as a model of teams: a software team, a swarm of AI agents, or people and agents working together.
The page computes one team at a time. It does not solve the paper's market equilibrium, so it shows revenue per member, not how pay is split between types. The paper's AI-regime figures fix a coordination of 1.60 for the supercooperative case; the task skill of 5 used for that preset is my choice.
The job-board section is not from the paper. It is Steve Phelps's experiment of 16 November 2026 (harnesses job_board.py and job_board_research.py); the exponents are fitted on five team sizes up to 16.
Source for the model: arXiv 2611.05417.