This run is about how negotiated agreements are actually made — drafting, bracketed text, coalitions, and the arithmetic of consensus. It takes no side on any policy question, because the mechanics are the interesting part and they are the same regardless of the subject.
You are a junior member of a delegation at a three-day multilateral summit. The subject is a technical standard with real consequences and no natural constituency. Nobody at home is watching closely, which is both a freedom and a trap.
No trivia and no right answers — a narrative run about how a negotiated agreement is really assembled.
Four archetypes, four starting hands. Your pick sets the stats you begin with — not the ones you end with.
Seven decisions, each one nudging skill, wealth, reputation, and wellbeing. No take-backs.
Your choices resolve into one of six outcomes — and an honest read on what that pattern costs.
Each archetype begins with a different balance of strengths. Your pick sets the stats you start with — not the ones you end with.
Below is the whole run — every chapter, every option, and where each one leads. Press Play this run above to take it as a game instead, with stats that move as you choose and an ending scored from how you played.
The chair circulates a draft the night before. It runs to nine pages and roughly a third of it is in square brackets — the convention for language nobody has agreed yet.
Your delegation's position is clear on two brackets and silent on the other eleven.
Formal sessions are for the record. The actual work happens in the corridor, where a mid-sized delegation suggests they could move on your priority bracket if you were flexible on a definition you have no strong view about.
You have no mandate to trade anything.
Overnight guidance arrives from your capital. It is firmer than the room will bear and was plainly written by someone who has not seen the draft.
Following it literally means blocking a text that seventy other delegations can accept.
A journalist has the draft. A story runs describing one bracketed option — clearly labelled as an option in the text — as though it were an agreed decision.
Two delegations harden publicly within the hour. The room is now performing for cameras.
A delegation of two people is being steamrolled. They have a legitimate technical objection and no capacity to draft an alternative at three in the morning.
Their objection is not your problem. Consensus, however, includes them.
Final hours. What is achievable is a diluted agreement with a review clause. What is not achievable is the strong version.
The choice is a weak agreement now, or no agreement and a resumed session in eighteen months with a different set of governments.
You write the account that your capital will read and that the next delegation will inherit. There is a version that makes this trip sound like a success and a version that is useful.
They are not the same document.
No ending is the “best” one — only the one your decisions earned.
You read the room before you spoke in it.
Brackets mapped to blockers, red lines asked for directly, single issues assembled into packages, and a review date fought for when the text softened. Almost none of it happened in a formal session. That is where multilateral outcomes are actually decided.
You spent your capital on other people's problems.
You drafted for a delegation of two at three in the morning, paired them with a sponsor who had capacity, and corrected the record when a leak hardened positions. None of it advanced your own brackets directly. All of it is why people took your calls in the next round.
You changed the instruction instead of bending it.
When the guidance from home did not fit the room, you asked for a call and had the mandate widened properly rather than interpreting generously and hoping. It cost twenty minutes and it is the difference between flexibility and personal exposure.
The next delegation inherited a map.
Concessions named, reliable counterparts recorded, the broken instruction process flagged. Reporting honestly is the least rewarded act in this entire run and the one that compounds — because the alternative is a successor walking into a trade they were told never happened.
You made commitments you could not carry.
Agreed in principle without a mandate, interpreted instructions generously, briefed a journalist to shape the story. Each was a reasonable attempt to keep things moving. Together they put a junior official personally on the hook for a negotiation their capital had not authorised.
A weak text, a firm date, and a useful report.
Homework done, no commitments beyond your mandate, the instruction fixed properly, the leak defused procedurally, a small delegation helped, and consensus preserved with a review date and an honest account home. Nobody will call it a breakthrough. It is what a working system looks like.
This is a fictional multilateral meeting. It does not describe a real summit, government, official, negotiation or policy proposal. The draft text, leak, instructions and outcomes are storytelling devices. A score cannot judge diplomatic competence, predict an agreement, or tell a participant how to represent a government or organisation.
The useful part of the run is procedural literacy. A reader can notice that a text has a forum, a mandate, participants, rules and a decision method before assuming that all negotiations work alike. The United Nations materials linked below explain particular treaty and General Assembly contexts. They do not mean that every international body uses consensus, brackets, review clauses or the same delegation roles. The applicable rules of procedure and mandate control in a real forum.
The corridor chapter is not a licence to bypass accountability or formal process. Informal discussion can help delegates understand positions and draft options, but authority to make commitments comes from the relevant mandate and instructions. The scenario simplifies that tension so it can show a choice; real delegations may involve legal, political, technical and public responsibilities that do not fit a game.
Likewise, a package deal is not inherently more legitimate than a single issue. It can create movement, but it can also conceal trade-offs or exclude affected voices. A review clause can preserve a future opportunity, but only if the body has authority and resources to conduct the review. The game asks readers to see these mechanisms, not to treat them as tricks.
Use the page as a reading guide: identify the forum, the decision rule, the text's status, who has authority to speak, and where the official record is kept. Those questions make international procedure more understandable without taking a position on the underlying policy. The sources below are public procedural references, not diplomatic, legal or political advice.
A stalled text does not always require a larger package deal. Depending on the forum and mandate, participants may clarify one disputed term, separate issues into different records, ask for technical work, preserve competing positions, or defer a question through an authorised review process. None of those devices is automatically available or desirable. The alternative worth testing is the one the actual rules permit and affected participants can examine, not the one that creates the most dramatic fictional compromise.
Choose a public agreement or meeting record and identify its forum, mandate, participants, decision rule, draft status and official source. Note which points are explicit in the record and which are inference. Do not treat a bracket, a hallway conversation or a review clause as having one universal meaning; check the rules that govern that body. This exercise is for reading public procedure, not for advising a delegation or interpreting a live negotiation.
Ask which institution owns the process, what authority the participants have, whether the text is a proposal or an adopted record, and how decisions are formally made. Ask where the official text and rules can be read. Those questions prevent a reader from treating a procedural phrase as self-explanatory. They do not reveal private positions, resolve an interpretation or provide diplomatic advice about a real negotiation.
Use the authored links below to examine the main trade-off from another angle.
The mechanics here are deliberately ordinary, because that is what they are. Square brackets mark language nobody has agreed. Consensus means the smallest delegation in the room has the same veto as the largest. Almost nothing is settled in formal session — the formal session ratifies what the corridor produced.
Two patterns decide most outcomes. The first is that packages close where single issues stall: a bracket traded alone looks like a loss, and the same bracket inside a package looks like a deal. The second is that the review clause is usually worth more than the text it sits under, because a firm date converts a weak agreement into a scheduled second attempt — and "in due course" converts it into nothing.
This run takes no position on any policy. It is about the machinery, which is public, well documented, and considerably more interesting than the coverage suggests.
This is a non-partisan narrative simulation about the mechanics of multilateral negotiation. It describes no real summit, government or official, takes no position on any policy question, and the stat effects are storytelling devices rather than predictions. Procedures vary by forum and treaty body.