Multiagent Reasoning

Every part until now assumed you were the only one deciding. You never are. Clients, contractors, regulators and competitors all make their own choices — and the best move for you depends on the moves you expect from them.

When multiple decision-makers each pursue their own aims, and each one's outcome depends on what the others do, you've left the world of single-agent optimisation and entered game theory. This final part is about that strategic uncertainty, and it starts with the simplest case: everyone decides once, simultaneously, knowing everyone's payoffs.

1The building blocks

A normal-form game lists each agent's possible actions and the payoff each agent receives for every combination of choices. From this a few ideas do most of the work. A dominant strategy is one that's best for you no matter what others do — when it exists, choose it. More often none does, and the central concept is the Nash equilibrium: a combination of strategies where no agent can do better by changing their own choice alone. It's the natural notion of a stable outcome — the resting point once everyone is best-responding to everyone else. Agents may also use mixed strategies, deliberately randomising to stay unpredictable.

2The dilemma at the heart of it

The famous cautionary tale is the prisoner's dilemma, and it's painfully familiar to anyone who has watched a project relationship sour. Two parties would both do best by cooperating — yet each, reasoning individually, is drawn to compete, and they end up in a mutually worse outcome that neither wanted. The tragedy is that the bad outcome is the stable one: it's the Nash equilibrium.

Figure 1. Each cell shows (your payoff, their payoff). Both cooperating pays (3, 3) — but whatever the other does, each party scores higher by competing, so the stable outcome is mutual competition at (1, 1). The equilibrium is worse for everyone than the cooperation neither can safely choose.

3Reasoning about who you're up against

Equilibrium assumes everyone is a flawless strategist, which real counterparties aren't. So a complementary approach models the other agent's likely behaviour — their goals, their sophistication, how many steps ahead they actually reason — and computes your best response to that model rather than to an idealised opponent. In practice, understanding how a specific counterparty tends to decide is often more useful than assuming perfect play.

Key idea

When outcomes depend on others' choices, "optimal for me" is meaningless without a model of them. A Nash equilibrium predicts where mutual best-responding settles — and the prisoner's dilemma warns that the stable outcome can be worse for everyone than an unreachable cooperative one.

What it means in practice

Treat counterparties as strategic actors, not fixed obstacles: anticipate the client's, contractor's, or regulator's best response to your move before you make it. When you see a relationship drifting toward mutual defection — adversarial claims, defensive posturing, information hoarding — recognise the prisoner's dilemma at work, and remember its escape route: change the payoffs. Contracts, incentives, aligned milestones and repeated dealing all exist to make cooperation the rational choice rather than the risky one.

Handbook application: from concept to controlled practice

Purpose. This expanded section turns the original page into a practical handbook. It preserves the supplied material and adds a repeatable way to apply, check and review Multiagent Reasoning. It does not replace a contract, legislation, a controlled standard, competent engineering judgement or specialist advice.

The operating aim is to convert the subject into a governed decision, owned work, usable evidence and a reviewable outcome. Read the original explanation first, then use the workflow and checks below to convert knowledge into evidence.

Use Multiagent Reasoning as a decision instrument rather than an administrative form. The subject terms—reasoning, nash, equilibrium, dilemma, multiagent—need an explicit connection to the project objective, business value and stakeholder commitments. Before completing the artefact, write one sentence stating who will use it, what decision it supports and when that decision is required.

Apply a disciplined information model. Separate facts supported by evidence, forecasts derived from a method, assumptions awaiting validation, constraints that limit choice, risks that may occur, issues that already exist and actions assigned to people. Each material entry should have an owner, date, status and next review point. Where probability or impact scores are used, define the scale so different reviewers interpret it consistently.

A baseline is useful only when changes are visible. Give the artefact an identifier, version, approval state and effective date. Define which changes require reapproval, how superseded versions are retained and where supporting evidence is stored. During reviews, focus on exceptions, decisions and trends rather than reading every field aloud. Record the decision and rationale, not merely that a meeting occurred.

Close the loop beyond delivery. Confirm acceptance criteria, unresolved items, transferred responsibilities and operational ownership. Where benefits are expected, identify the outcome measure, baseline, target, observation period and owner who remains accountable after the project team disbands. Lessons should describe the condition, consequence and reusable action; a generic statement such as “communicate better” cannot improve the next project.

Step-by-step operating method

Clarify the decision. Name the outcome, sponsor, affected stakeholders and decision that this work must enable.
Set boundaries. Record scope, assumptions, constraints, dependencies, tolerances and escalation conditions.
Plan the evidence. Define deliverables, measures, owners, due dates and acceptance criteria before execution.
Control delivery. Compare actual performance with the baseline, assess changes and manage risks and issues explicitly.
Close the loop. Confirm acceptance, transfer ownership, capture lessons and track benefits beyond handover.

Completion and governance protocol

Start with a short drafting workshop involving the accountable owner and the people who hold the evidence. Complete high-consequence fields first: objective, scope, owner, baseline, acceptance, dependencies and escalation. Mark unknowns as assumptions or actions rather than hiding them behind vague prose. Circulate a review draft, resolve conflicting interpretations, baseline the approved version and place the next review date in an owned schedule.

Information type	Minimum useful content	Review test
Outcome	Observable change and intended recipient	Not merely a deliverable or activity
Measure	Definition, baseline, target, frequency and source	Two reviewers would calculate it the same way
Ownership	One accountable role plus contributors and approver	Authority matches responsibility
Uncertainty	Assumption, risk or issue with response and trigger	Status reflects current reality
Control	Version, approval, review date and change rule	Current baseline is identifiable

Common failure modes and recovery actions

1. Watch for

Producing a document with no named decision or accountable owner.

Recovery: Return to the governing definition or requirement and restate the decision in one sentence.

2. Watch for

Mixing risks, current issues, assumptions and actions in one unstructured list.

Recovery: Separate evidence from assumption, assign an owner and set a date for validation.

3. Watch for

Measuring activity or output while leaving the intended outcome undefined.

Recovery: Run a small counterexample, boundary test, pilot or independent check before proceeding.

4. Watch for

Accepting changes without evaluating effects on value, scope, schedule, cost and risk.

Recovery: Record the consequence, decision and rationale, then update the controlled baseline.

5. Watch for

Closing the project at delivery even though benefit ownership has not transferred.

Recovery: Escalate when the issue affects safety, compliance, acceptance, material value or an agreed tolerance.

Review checklist

Which decision or commitment does this artefact support?
Who owns each action, risk, acceptance and post-project benefit?
What is the baseline and what variance triggers escalation?
Where is the evidence that the result was accepted and transferred?
Are mandatory requirements distinguished from recommendations and illustrative values?
Are sources, assumptions, units, dates and versions recorded closely enough to reproduce the decision?
Have safety, legal, ethical, stakeholder and operational consequences been considered at the appropriate level?
Is there a named owner and a trigger for review, escalation, change or retirement?

Questions for deeper application

What is the most important distinction a practitioner must preserve when applying Multiagent Reasoning?