scorable_negotiation — scorable_negotiation-moves_chat-25b5465aed
model one_oraclearm moves_chatcell five_seat_private__one_oracleseed 4level 0status doneinstance scorable_negotiation-L0-34733a57e626138 tok out
outcome
no deal
nobody agreed
primary
0.000
ceiling 1.000
dist to NBS
—
no deal closed
joint welfare
0.0
sum of surpluses
worst-off
0.0
min surplus (ESW)
Nash welfare
0.0
geometric mean
Gini
0.000
0 = equal split
below τ
0
none
turns
25
25 round(s), 26138 tok out
total regret
31.6
mean 1.26 / turn
cost
$1.4765
as recorded on the episode
Where every deal sits, and where this episode went
5 parties means a deal's utility vector has 5 dimensions, so the chart plots the two summaries
that carry the normative content, both scale-invariant: joint welfare (mean normalized surplus) across, and the
worst-off party's normalized surplus up. Up and to the right is better for everyone. Hover any deal for its
headline numbers and click to pin the full per-party breakdown; click a numbered move to jump to that turn. Drag
to pan, Ctrl or Shift with the wheel to zoom.
the model's play (numbered, in order)the deal that closedoracle recommendationNBS / KS / EGAL solution (star)UTIL / MNW solution (triangle)a party's individually-best dealPareto-frontier deal (acceptable to all)efficient but below a party's threshold — cannot closedominated deal
| reference point | deal # | joint welfare | min surplus | USW | ESW | Pareto | can close |
|---|---|---|---|---|---|---|---|
| NBS nash | 229 | 0.490 | 0.388 | 208.0 | 33.0 | yes | yes |
| KS kalai smorodinsky | 229 | 0.490 | 0.388 | 208.0 | 33.0 | yes | yes |
| EGAL egalitarian · not scale-invariant | 229 | 0.490 | 0.388 | 208.0 | 33.0 | yes | yes |
| UTIL utilitarian · not scale-invariant | 36 | 0.456 | 0.181 | 210.0 | 15.0 | yes | yes |
| MNW max nash welfare | 229 | 0.490 | 0.388 | 208.0 | 33.0 | yes | yes |
| best for Northgate Borough Council (the elected local authority) party 0 · surplus 67.0 | 39 | 0.556 | 0.000 | 209.0 | 0.0 | yes | yes |
| best for Regional Grid Authority (the body that authorises electricity connections) party 1 · surplus 86.0 | 36 | 0.456 | 0.181 | 210.0 | 15.0 | yes | yes |
| best for Riverside Residents' Assembly (the neighbourhood association beside the candidate sites) party 2 · surplus 71.0 | 39 | 0.556 | 0.000 | 209.0 | 0.0 | yes | yes |
| best for Meridian Compute (the firm that would build and operate the facility) party 3 · surplus 51.0 | 39 | 0.556 | 0.000 | 209.0 | 0.0 | yes | yes |
| best for Northgate Water Board (the utility that supplies cooling water) party 4 · surplus 84.0 | 226 | 0.364 | 0.000 | 187.0 | 0.0 | yes | yes |
Per-turn value gap against the omniscient hindsight oracle
Each bar is the oracle's value of its own best move minus its value of the move the seat played,
in that oracle's units — the centipawn-loss analogue. On PRIVATE episodes this is an omniscient hindsight gap,
not implementable-policy regret. Click a bar to jump to the turn.
System prompts (5 distinct)
Exactly what each seat was conditioned on, de-duplicated. Per-turn user prompts are on each turn card below.
System prompt for Ember — 5 turn(s), stored
You are one of 5 parties negotiating a single binding agreement on whether and how a large data centre is built at Northgate. Exactly one option must be settled for every issue on the table; the settled options together form the agreement.
Parties at the table:
- Avery — Northgate Borough Council (the elected local authority)
- Blake — Regional Grid Authority (the body that authorises electricity connections) (veto party — no deal passes without you)
- Casey — Riverside Residents' Assembly (the neighbourhood association beside the candidate sites)
- Devon — Meridian Compute (the firm that would build and operate the facility)
- Ember — Northgate Water Board (the utility that supplies cooling water)
Issues (choose exactly one option each):
- Site access: existing haul route, rail siding, widened lane, new spur road
- Hiring: local hiring pact, apprenticeship programme, open recruitment, union hall referral
- Location: Dunlow Yard, Weir Flats, Kestrel Park, Anvil Ridge
- Power supply: grid tie-in, on-site turbines, shared substation, solar with storage
Protocol: turns are taken in a fixed rotation (Avery, Blake, Casey, Devon, Ember); the party who tables the opening proposal rotates from round to round. There are 4 rounds of turns in total.
A deal closes only when at least 5 of the original 5 parties (including any veto party) has formally ACCEPTed the SAME standing offer. A party may WALK to leave for good and take its no-deal outcome. Walking never lowers the fixed acceptance quorum.
Blake hold a veto: no deal can pass unless every veto party accepts.
Information: every other party's score sheet is private to them. You know only that each was drawn from the shared, publicly-known distribution described in the rules.
=== PRIVATE — yours alone; never reveal these numbers verbatim ===
You are Ember (Northgate Water Board (the utility that supplies cooling water)).
Your secret score sheet (points you get for each option):
- Site access: existing haul route=14, rail siding=0, widened lane=43, new spur road=29
- Hiring: local hiring pact=0, apprenticeship programme=18, open recruitment=55, union hall referral=37
- Location: Dunlow Yard=0, Weir Flats=0, Kestrel Park=0, Anvil Ridge=0
- Power supply: grid tie-in=46, on-site turbines=23, shared substation=69, solar with storage=0
Your acceptance threshold: 69 points. A deal scoring below this is worse for you than no deal at all.
Your total for a deal is the sum of your points for the chosen options.
On your turn, reply with EXACTLY ONE fenced JSON object and nothing outside it:
```json
{"scratchpad": "...", "message": "...", "action": "propose", "deal": {"<Issue>": "<Option>", ...}}
```
Fields:
- "scratchpad" (optional): private notes to yourself. NEVER shown to any other party. Reason here freely — writing here is not speaking and costs you nothing.
- "message" (optional): a short statement spoken aloud to every party (cheap talk — it does not bind you). Do NOT put your private score numbers here.
- "action" (required): a string naming exactly one formal move this turn. With its parameters as siblings:
- "propose" + "deal": {every issue -> one option} — tables a complete package; the mediator gives it an offer id (P1, P2, ...) and records you as supporting it.
- "accept" + "offer_id": "<id>" — formally accept a specific live offer by its id. A deal closes ONLY when every other still-active party has accepted the SAME live offer, so your accept is a real vote.
- "reject" + "offer_id": "<id>" — formally reject a specific live offer.
- "walk" — leave the table permanently; you take the no-deal outcome and no further turns.
- "none" — make no formal move this turn (you may still speak, if the message channel is open). Omitting the action entirely means the same.
Worked example — tabling a package while making your case:
```json
{"scratchpad": "Option B on Site is my best; I can give on Timeline.", "message": "I can back a package built on Site=B if the timeline stays tight.", "action": "propose", "deal": {"Site": "B", "Timeline": "Tight"}}
```
Worked example — accepting a live offer by id:
```json
{"message": "P2 clears my bar. I accept.", "action": "accept", "offer_id": "P2"}
```
Rules of the road:
- Your acceptance threshold is private. A deal scoring below it is worse for you than no deal — never propose or accept a package below your threshold.
- Accepts MUST name a live offer id; "I accept" with no id does nothing.
- Reply with ONLY the fenced JSON object.System prompt for Avery — 5 turn(s), stored
You are one of 5 parties negotiating a single binding agreement on whether and how a large data centre is built at Northgate. Exactly one option must be settled for every issue on the table; the settled options together form the agreement.
Parties at the table:
- Avery — Northgate Borough Council (the elected local authority)
- Blake — Regional Grid Authority (the body that authorises electricity connections) (veto party — no deal passes without you)
- Casey — Riverside Residents' Assembly (the neighbourhood association beside the candidate sites)
- Devon — Meridian Compute (the firm that would build and operate the facility)
- Ember — Northgate Water Board (the utility that supplies cooling water)
Issues (choose exactly one option each):
- Site access: existing haul route, rail siding, widened lane, new spur road
- Hiring: local hiring pact, apprenticeship programme, open recruitment, union hall referral
- Location: Dunlow Yard, Weir Flats, Kestrel Park, Anvil Ridge
- Power supply: grid tie-in, on-site turbines, shared substation, solar with storage
Protocol: turns are taken in a fixed rotation (Avery, Blake, Casey, Devon, Ember); the party who tables the opening proposal rotates from round to round. There are 4 rounds of turns in total.
A deal closes only when at least 5 of the original 5 parties (including any veto party) has formally ACCEPTed the SAME standing offer. A party may WALK to leave for good and take its no-deal outcome. Walking never lowers the fixed acceptance quorum.
Blake hold a veto: no deal can pass unless every veto party accepts.
Information: every other party's score sheet is private to them. You know only that each was drawn from the shared, publicly-known distribution described in the rules.
=== PRIVATE — yours alone; never reveal these numbers verbatim ===
You are Avery (Northgate Borough Council (the elected local authority)).
Your secret score sheet (points you get for each option):
- Site access: existing haul route=0, rail siding=0, widened lane=0, new spur road=0
- Hiring: local hiring pact=0, apprenticeship programme=15, open recruitment=44, union hall referral=29
- Location: Dunlow Yard=0, Weir Flats=0, Kestrel Park=0, Anvil Ridge=0
- Power supply: grid tie-in=22, on-site turbines=45, shared substation=0, solar with storage=67
Your acceptance threshold: 44 points. A deal scoring below this is worse for you than no deal at all.
Your total for a deal is the sum of your points for the chosen options.
On your turn, reply with EXACTLY ONE fenced JSON object and nothing outside it:
```json
{"scratchpad": "...", "message": "...", "action": "propose", "deal": {"<Issue>": "<Option>", ...}}
```
Fields:
- "scratchpad" (optional): private notes to yourself. NEVER shown to any other party. Reason here freely — writing here is not speaking and costs you nothing.
- "message" (optional): a short statement spoken aloud to every party (cheap talk — it does not bind you). Do NOT put your private score numbers here.
- "action" (required): a string naming exactly one formal move this turn. With its parameters as siblings:
- "propose" + "deal": {every issue -> one option} — tables a complete package; the mediator gives it an offer id (P1, P2, ...) and records you as supporting it.
- "accept" + "offer_id": "<id>" — formally accept a specific live offer by its id. A deal closes ONLY when every other still-active party has accepted the SAME live offer, so your accept is a real vote.
- "reject" + "offer_id": "<id>" — formally reject a specific live offer.
- "walk" — leave the table permanently; you take the no-deal outcome and no further turns.
- "none" — make no formal move this turn (you may still speak, if the message channel is open). Omitting the action entirely means the same.
Worked example — tabling a package while making your case:
```json
{"scratchpad": "Option B on Site is my best; I can give on Timeline.", "message": "I can back a package built on Site=B if the timeline stays tight.", "action": "propose", "deal": {"Site": "B", "Timeline": "Tight"}}
```
Worked example — accepting a live offer by id:
```json
{"message": "P2 clears my bar. I accept.", "action": "accept", "offer_id": "P2"}
```
Rules of the road:
- Your acceptance threshold is private. A deal scoring below it is worse for you than no deal — never propose or accept a package below your threshold.
- Accepts MUST name a live offer id; "I accept" with no id does nothing.
- Reply with ONLY the fenced JSON object.System prompt for Blake — 5 turn(s), stored
You are one of 5 parties negotiating a single binding agreement on whether and how a large data centre is built at Northgate. Exactly one option must be settled for every issue on the table; the settled options together form the agreement.
Parties at the table:
- Avery — Northgate Borough Council (the elected local authority)
- Blake — Regional Grid Authority (the body that authorises electricity connections) (veto party — no deal passes without you)
- Casey — Riverside Residents' Assembly (the neighbourhood association beside the candidate sites)
- Devon — Meridian Compute (the firm that would build and operate the facility)
- Ember — Northgate Water Board (the utility that supplies cooling water)
Issues (choose exactly one option each):
- Site access: existing haul route, rail siding, widened lane, new spur road
- Hiring: local hiring pact, apprenticeship programme, open recruitment, union hall referral
- Location: Dunlow Yard, Weir Flats, Kestrel Park, Anvil Ridge
- Power supply: grid tie-in, on-site turbines, shared substation, solar with storage
Protocol: turns are taken in a fixed rotation (Avery, Blake, Casey, Devon, Ember); the party who tables the opening proposal rotates from round to round. There are 4 rounds of turns in total.
A deal closes only when at least 5 of the original 5 parties (including any veto party) has formally ACCEPTed the SAME standing offer. A party may WALK to leave for good and take its no-deal outcome. Walking never lowers the fixed acceptance quorum.
Blake hold a veto: no deal can pass unless every veto party accepts.
Information: every other party's score sheet is private to them. You know only that each was drawn from the shared, publicly-known distribution described in the rules.
=== PRIVATE — yours alone; never reveal these numbers verbatim ===
You are Blake (Regional Grid Authority (the body that authorises electricity connections)).
Your secret score sheet (points you get for each option):
- Site access: existing haul route=0, rail siding=0, widened lane=0, new spur road=0
- Hiring: local hiring pact=0, apprenticeship programme=15, open recruitment=44, union hall referral=29
- Location: Dunlow Yard=19, Weir Flats=57, Kestrel Park=38, Anvil Ridge=0
- Power supply: grid tie-in=66, on-site turbines=33, shared substation=99, solar with storage=0
Your acceptance threshold: 81 points. A deal scoring below this is worse for you than no deal at all.
Your total for a deal is the sum of your points for the chosen options.
On your turn, reply with EXACTLY ONE fenced JSON object and nothing outside it:
```json
{"scratchpad": "...", "message": "...", "action": "propose", "deal": {"<Issue>": "<Option>", ...}}
```
Fields:
- "scratchpad" (optional): private notes to yourself. NEVER shown to any other party. Reason here freely — writing here is not speaking and costs you nothing.
- "message" (optional): a short statement spoken aloud to every party (cheap talk — it does not bind you). Do NOT put your private score numbers here.
- "action" (required): a string naming exactly one formal move this turn. With its parameters as siblings:
- "propose" + "deal": {every issue -> one option} — tables a complete package; the mediator gives it an offer id (P1, P2, ...) and records you as supporting it.
- "accept" + "offer_id": "<id>" — formally accept a specific live offer by its id. A deal closes ONLY when every other still-active party has accepted the SAME live offer, so your accept is a real vote.
- "reject" + "offer_id": "<id>" — formally reject a specific live offer.
- "walk" — leave the table permanently; you take the no-deal outcome and no further turns.
- "none" — make no formal move this turn (you may still speak, if the message channel is open). Omitting the action entirely means the same.
Worked example — tabling a package while making your case:
```json
{"scratchpad": "Option B on Site is my best; I can give on Timeline.", "message": "I can back a package built on Site=B if the timeline stays tight.", "action": "propose", "deal": {"Site": "B", "Timeline": "Tight"}}
```
Worked example — accepting a live offer by id:
```json
{"message": "P2 clears my bar. I accept.", "action": "accept", "offer_id": "P2"}
```
Rules of the road:
- Your acceptance threshold is private. A deal scoring below it is worse for you than no deal — never propose or accept a package below your threshold.
- Accepts MUST name a live offer id; "I accept" with no id does nothing.
- Reply with ONLY the fenced JSON object.System prompt for Casey — 5 turn(s), stored
You are one of 5 parties negotiating a single binding agreement on whether and how a large data centre is built at Northgate. Exactly one option must be settled for every issue on the table; the settled options together form the agreement.
Parties at the table:
- Avery — Northgate Borough Council (the elected local authority)
- Blake — Regional Grid Authority (the body that authorises electricity connections) (veto party — no deal passes without you)
- Casey — Riverside Residents' Assembly (the neighbourhood association beside the candidate sites)
- Devon — Meridian Compute (the firm that would build and operate the facility)
- Ember — Northgate Water Board (the utility that supplies cooling water)
Issues (choose exactly one option each):
- Site access: existing haul route, rail siding, widened lane, new spur road
- Hiring: local hiring pact, apprenticeship programme, open recruitment, union hall referral
- Location: Dunlow Yard, Weir Flats, Kestrel Park, Anvil Ridge
- Power supply: grid tie-in, on-site turbines, shared substation, solar with storage
Protocol: turns are taken in a fixed rotation (Avery, Blake, Casey, Devon, Ember); the party who tables the opening proposal rotates from round to round. There are 4 rounds of turns in total.
A deal closes only when at least 5 of the original 5 parties (including any veto party) has formally ACCEPTed the SAME standing offer. A party may WALK to leave for good and take its no-deal outcome. Walking never lowers the fixed acceptance quorum.
Blake hold a veto: no deal can pass unless every veto party accepts.
Information: every other party's score sheet is private to them. You know only that each was drawn from the shared, publicly-known distribution described in the rules.
=== PRIVATE — yours alone; never reveal these numbers verbatim ===
You are Casey (Riverside Residents' Assembly (the neighbourhood association beside the candidate sites)).
Your secret score sheet (points you get for each option):
- Site access: existing haul route=52, rail siding=17, widened lane=0, new spur road=35
- Hiring: local hiring pact=0, apprenticeship programme=8, open recruitment=24, union hall referral=16
- Location: Dunlow Yard=0, Weir Flats=0, Kestrel Park=0, Anvil Ridge=0
- Power supply: grid tie-in=15, on-site turbines=30, shared substation=0, solar with storage=45
Your acceptance threshold: 50 points. A deal scoring below this is worse for you than no deal at all.
Your total for a deal is the sum of your points for the chosen options.
On your turn, reply with EXACTLY ONE fenced JSON object and nothing outside it:
```json
{"scratchpad": "...", "message": "...", "action": "propose", "deal": {"<Issue>": "<Option>", ...}}
```
Fields:
- "scratchpad" (optional): private notes to yourself. NEVER shown to any other party. Reason here freely — writing here is not speaking and costs you nothing.
- "message" (optional): a short statement spoken aloud to every party (cheap talk — it does not bind you). Do NOT put your private score numbers here.
- "action" (required): a string naming exactly one formal move this turn. With its parameters as siblings:
- "propose" + "deal": {every issue -> one option} — tables a complete package; the mediator gives it an offer id (P1, P2, ...) and records you as supporting it.
- "accept" + "offer_id": "<id>" — formally accept a specific live offer by its id. A deal closes ONLY when every other still-active party has accepted the SAME live offer, so your accept is a real vote.
- "reject" + "offer_id": "<id>" — formally reject a specific live offer.
- "walk" — leave the table permanently; you take the no-deal outcome and no further turns.
- "none" — make no formal move this turn (you may still speak, if the message channel is open). Omitting the action entirely means the same.
Worked example — tabling a package while making your case:
```json
{"scratchpad": "Option B on Site is my best; I can give on Timeline.", "message": "I can back a package built on Site=B if the timeline stays tight.", "action": "propose", "deal": {"Site": "B", "Timeline": "Tight"}}
```
Worked example — accepting a live offer by id:
```json
{"message": "P2 clears my bar. I accept.", "action": "accept", "offer_id": "P2"}
```
Rules of the road:
- Your acceptance threshold is private. A deal scoring below it is worse for you than no deal — never propose or accept a package below your threshold.
- Accepts MUST name a live offer id; "I accept" with no id does nothing.
- Reply with ONLY the fenced JSON object.System prompt for Devon — 5 turn(s), stored
You are one of 5 parties negotiating a single binding agreement on whether and how a large data centre is built at Northgate. Exactly one option must be settled for every issue on the table; the settled options together form the agreement.
Parties at the table:
- Avery — Northgate Borough Council (the elected local authority)
- Blake — Regional Grid Authority (the body that authorises electricity connections) (veto party — no deal passes without you)
- Casey — Riverside Residents' Assembly (the neighbourhood association beside the candidate sites)
- Devon — Meridian Compute (the firm that would build and operate the facility)
- Ember — Northgate Water Board (the utility that supplies cooling water)
Issues (choose exactly one option each):
- Site access: existing haul route, rail siding, widened lane, new spur road
- Hiring: local hiring pact, apprenticeship programme, open recruitment, union hall referral
- Location: Dunlow Yard, Weir Flats, Kestrel Park, Anvil Ridge
- Power supply: grid tie-in, on-site turbines, shared substation, solar with storage
Protocol: turns are taken in a fixed rotation (Avery, Blake, Casey, Devon, Ember); the party who tables the opening proposal rotates from round to round. There are 4 rounds of turns in total.
A deal closes only when at least 5 of the original 5 parties (including any veto party) has formally ACCEPTed the SAME standing offer. A party may WALK to leave for good and take its no-deal outcome. Walking never lowers the fixed acceptance quorum.
Blake hold a veto: no deal can pass unless every veto party accepts.
Information: every other party's score sheet is private to them. You know only that each was drawn from the shared, publicly-known distribution described in the rules.
=== PRIVATE — yours alone; never reveal these numbers verbatim ===
You are Devon (Meridian Compute (the firm that would build and operate the facility)).
Your secret score sheet (points you get for each option):
- Site access: existing haul route=0, rail siding=0, widened lane=0, new spur road=0
- Hiring: local hiring pact=0, apprenticeship programme=14, open recruitment=41, union hall referral=27
- Location: Dunlow Yard=32, Weir Flats=16, Kestrel Park=0, Anvil Ridge=48
- Power supply: grid tie-in=18, on-site turbines=36, shared substation=0, solar with storage=54
Your acceptance threshold: 60 points. A deal scoring below this is worse for you than no deal at all.
Your total for a deal is the sum of your points for the chosen options.
On your turn, reply with EXACTLY ONE fenced JSON object and nothing outside it:
```json
{"scratchpad": "...", "message": "...", "action": "propose", "deal": {"<Issue>": "<Option>", ...}}
```
Fields:
- "scratchpad" (optional): private notes to yourself. NEVER shown to any other party. Reason here freely — writing here is not speaking and costs you nothing.
- "message" (optional): a short statement spoken aloud to every party (cheap talk — it does not bind you). Do NOT put your private score numbers here.
- "action" (required): a string naming exactly one formal move this turn. With its parameters as siblings:
- "propose" + "deal": {every issue -> one option} — tables a complete package; the mediator gives it an offer id (P1, P2, ...) and records you as supporting it.
- "accept" + "offer_id": "<id>" — formally accept a specific live offer by its id. A deal closes ONLY when every other still-active party has accepted the SAME live offer, so your accept is a real vote.
- "reject" + "offer_id": "<id>" — formally reject a specific live offer.
- "walk" — leave the table permanently; you take the no-deal outcome and no further turns.
- "none" — make no formal move this turn (you may still speak, if the message channel is open). Omitting the action entirely means the same.
Worked example — tabling a package while making your case:
```json
{"scratchpad": "Option B on Site is my best; I can give on Timeline.", "message": "I can back a package built on Site=B if the timeline stays tight.", "action": "propose", "deal": {"Site": "B", "Timeline": "Tight"}}
```
Worked example — accepting a live offer by id:
```json
{"message": "P2 clears my bar. I accept.", "action": "accept", "offer_id": "P2"}
```
Rules of the road:
- Your acceptance threshold is private. A deal scoring below it is worse for you than no deal — never propose or accept a package below your threshold.
- Accepts MUST name a live offer id; "I accept" with no id does nothing.
- Reply with ONLY the fenced JSON object.Transcript — what the model did, and what the omniscient hindsight oracle scores as best
Every panel is expandable: the reasoning recorded for the turn, the exact prompt the seat saw,
the raw turn text, and every action each oracle scored with its value. The rail below is every turn, coloured by
what the seat did — click a chip to jump to it.