All field notes

Multiplayer goals · Field note 02

Multiplayer AI is shared context around a goal

A team can give every person an AI assistant and still make coordination worse. Each assistant sees a different slice of the work, so each one can be locally convincing and collectively wrong.

01

More agents multiply the context gap

An agent working for one participant may know the latest customer concern. Another may have the delivery plan. A third may still be acting on a decision that changed yesterday. Faster output does not resolve those differences; it lets each version of reality move faster.

The shared problem is not model intelligence. It is maintaining a current understanding of the goal, the decisions around it, and who has actually accepted each commitment.

02

The useful unit is a shared goal, not a shared brain

A multiplayer system should not pool everyone’s private memory. It should create a bounded place where participants deliberately contribute what the group needs: a decision, constraint, source, open question, or proposed commitment.

Each person keeps a private context of their own. The shared space contains only what belongs to the goal. Connected AIs work from that same shared layer and can still distinguish a proposal from an accepted commitment.

  • Private context stays private unless its owner deliberately contributes it.
  • Shared claims point back to evidence and the participant who supplied or confirmed them.
  • Commitments remain proposals until the responsible person accepts them.
  • A changed decision becomes visible to the next person or AI working from the space.
03

What the loop looks like in practice

Imagine a product launch with two founders and the AI tools each already uses. One founder confirms that design review remains Wednesday. The other changes the client promise to Friday. Their shared space now has the current constraint and the current commitment, grounded in the source each participant chose to share.

When either founder—or an approved connected AI—asks what could put Friday at risk, the answer begins from the same evidence. If an agent proposes that someone send a revised prototype, that task remains visibly unaccepted until the person responsible confirms it.

04

Coordination becomes a product loop

A good multiplayer experience grows organically from work that was already useful to one person. Start privately, invite someone when the goal becomes shared, and let each participant bring the AI they already trusts.

The value is not that another agent joined. It is that people and agents can act from one changing understanding without losing the boundary between personal context and shared responsibility.

Try the multiplayer path

Give two people and their AIs one current goal to work from.

Start a shared goal