Seat-swap comparison — scorable_negotiation-L0-611ee402f7 seed 1

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 — Electrical Workers' Union (the construction and maintenance workforce)
- Blake — Riverside Residents' Assembly (the neighbourhood association beside the candidate sites) (veto party — no deal passes without you)
- Casey — Regional Grid Authority (the body that authorises electricity connections)
- Devon — Anvil Ridge Landholding (the owner of record of the candidate parcels)
- Ember — Northgate Borough Council (the elected local authority)

Issues (choose exactly one option each):
- Compensation: in-kind infrastructure, one-off site payment, annual community fund, rates abatement
- Build schedule: three years, phased over eight years, five years, eighteen months
- Hiring: local hiring pact, union hall referral, apprenticeship programme, open recruitment
- Site access: rail siding, widened lane, existing haul route, new spur road

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 (Riverside Residents' Assembly (the neighbourhood association beside the candidate sites)).
Your secret score sheet (points you get for each option):
- Compensation: in-kind infrastructure=45, one-off site payment=0, annual community fund=23, rates abatement=68
- Build schedule: three years=25, phased over eight years=8, five years=0, eighteen months=17
- Hiring: local hiring pact=20, union hall referral=59, apprenticeship programme=0, open recruitment=40
- Site access: rail siding=0, widened lane=0, existing haul route=0, new spur road=0
Your acceptance threshold: 62 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.

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 — Electrical Workers' Union (the construction and maintenance workforce)
- Blake — Riverside Residents' Assembly (the neighbourhood association beside the candidate sites) (veto party — no deal passes without you)
- Casey — Regional Grid Authority (the body that authorises electricity connections)
- Devon — Anvil Ridge Landholding (the owner of record of the candidate parcels)
- Ember — Northgate Borough Council (the elected local authority)

Issues (choose exactly one option each):
- Compensation: in-kind infrastructure, one-off site payment, annual community fund, rates abatement
- Build schedule: three years, phased over eight years, five years, eighteen months
- Hiring: local hiring pact, union hall referral, apprenticeship programme, open recruitment
- Site access: rail siding, widened lane, existing haul route, new spur road

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 (Regional Grid Authority (the body that authorises electricity connections)).
Your secret score sheet (points you get for each option):
- Compensation: in-kind infrastructure=17, one-off site payment=52, annual community fund=35, rates abatement=0
- Build schedule: three years=27, phased over eight years=9, five years=0, eighteen months=18
- Hiring: local hiring pact=40, union hall referral=13, apprenticeship programme=27, open recruitment=0
- Site access: rail siding=0, widened lane=0, existing haul route=0, new spur road=0
Your acceptance threshold: 48 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.

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 — Electrical Workers' Union (the construction and maintenance workforce)
- Blake — Riverside Residents' Assembly (the neighbourhood association beside the candidate sites) (veto party — no deal passes without you)
- Casey — Regional Grid Authority (the body that authorises electricity connections)
- Devon — Anvil Ridge Landholding (the owner of record of the candidate parcels)
- Ember — Northgate Borough Council (the elected local authority)

Issues (choose exactly one option each):
- Compensation: in-kind infrastructure, one-off site payment, annual community fund, rates abatement
- Build schedule: three years, phased over eight years, five years, eighteen months
- Hiring: local hiring pact, union hall referral, apprenticeship programme, open recruitment
- Site access: rail siding, widened lane, existing haul route, new spur road

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 (Anvil Ridge Landholding (the owner of record of the candidate parcels)).
Your secret score sheet (points you get for each option):
- Compensation: in-kind infrastructure=18, one-off site payment=54, annual community fund=36, rates abatement=0
- Build schedule: three years=37, phased over eight years=12, five years=0, eighteen months=25
- Hiring: local hiring pact=0, union hall referral=0, apprenticeship programme=0, open recruitment=0
- Site access: rail siding=26, widened lane=52, existing haul route=0, new spur road=77
Your acceptance threshold: 67 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.

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 — Electrical Workers' Union (the construction and maintenance workforce)
- Blake — Riverside Residents' Assembly (the neighbourhood association beside the candidate sites) (veto party — no deal passes without you)
- Casey — Regional Grid Authority (the body that authorises electricity connections)
- Devon — Anvil Ridge Landholding (the owner of record of the candidate parcels)
- Ember — Northgate Borough Council (the elected local authority)

Issues (choose exactly one option each):
- Compensation: in-kind infrastructure, one-off site payment, annual community fund, rates abatement
- Build schedule: three years, phased over eight years, five years, eighteen months
- Hiring: local hiring pact, union hall referral, apprenticeship programme, open recruitment
- Site access: rail siding, widened lane, existing haul route, new spur road

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 Borough Council (the elected local authority)).
Your secret score sheet (points you get for each option):
- Compensation: in-kind infrastructure=54, one-off site payment=0, annual community fund=27, rates abatement=81
- Build schedule: three years=55, phased over eight years=18, five years=0, eighteen months=37
- Hiring: local hiring pact=0, union hall referral=0, apprenticeship programme=0, open recruitment=0
- Site access: rail siding=0, widened lane=0, existing haul route=0, new spur road=0
Your acceptance threshold: 54 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.

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 — Electrical Workers' Union (the construction and maintenance workforce)
- Blake — Riverside Residents' Assembly (the neighbourhood association beside the candidate sites) (veto party — no deal passes without you)
- Casey — Regional Grid Authority (the body that authorises electricity connections)
- Devon — Anvil Ridge Landholding (the owner of record of the candidate parcels)
- Ember — Northgate Borough Council (the elected local authority)

Issues (choose exactly one option each):
- Compensation: in-kind infrastructure, one-off site payment, annual community fund, rates abatement
- Build schedule: three years, phased over eight years, five years, eighteen months
- Hiring: local hiring pact, union hall referral, apprenticeship programme, open recruitment
- Site access: rail siding, widened lane, existing haul route, new spur road

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 (Electrical Workers' Union (the construction and maintenance workforce)).
Your secret score sheet (points you get for each option):
- Compensation: in-kind infrastructure=49, one-off site payment=0, annual community fund=24, rates abatement=73
- Build schedule: three years=58, phased over eight years=19, five years=0, eighteen months=38
- Hiring: local hiring pact=0, union hall referral=0, apprenticeship programme=0, open recruitment=0
- Site access: rail siding=0, widened lane=95, existing haul route=32, new spur road=63
Your acceptance threshold: 91 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.

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 — Electrical Workers' Union (the construction and maintenance workforce)
- Blake — Riverside Residents' Assembly (the neighbourhood association beside the candidate sites) (veto party — no deal passes without you)
- Casey — Regional Grid Authority (the body that authorises electricity connections)
- Devon — Anvil Ridge Landholding (the owner of record of the candidate parcels)
- Ember — Northgate Borough Council (the elected local authority)

Issues (choose exactly one option each):
- Compensation: in-kind infrastructure, one-off site payment, annual community fund, rates abatement
- Build schedule: three years, phased over eight years, five years, eighteen months
- Hiring: local hiring pact, union hall referral, apprenticeship programme, open recruitment
- Site access: rail siding, widened lane, existing haul route, new spur road

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 (Riverside Residents' Assembly (the neighbourhood association beside the candidate sites)).
Your secret score sheet (points you get for each option):
- Compensation: in-kind infrastructure=45, one-off site payment=0, annual community fund=23, rates abatement=68
- Build schedule: three years=25, phased over eight years=8, five years=0, eighteen months=17
- Hiring: local hiring pact=20, union hall referral=59, apprenticeship programme=0, open recruitment=40
- Site access: rail siding=0, widened lane=0, existing haul route=0, new spur road=0
Your acceptance threshold: 62 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.

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 — Electrical Workers' Union (the construction and maintenance workforce)
- Blake — Riverside Residents' Assembly (the neighbourhood association beside the candidate sites) (veto party — no deal passes without you)
- Casey — Regional Grid Authority (the body that authorises electricity connections)
- Devon — Anvil Ridge Landholding (the owner of record of the candidate parcels)
- Ember — Northgate Borough Council (the elected local authority)

Issues (choose exactly one option each):
- Compensation: in-kind infrastructure, one-off site payment, annual community fund, rates abatement
- Build schedule: three years, phased over eight years, five years, eighteen months
- Hiring: local hiring pact, union hall referral, apprenticeship programme, open recruitment
- Site access: rail siding, widened lane, existing haul route, new spur road

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 (Regional Grid Authority (the body that authorises electricity connections)).
Your secret score sheet (points you get for each option):
- Compensation: in-kind infrastructure=17, one-off site payment=52, annual community fund=35, rates abatement=0
- Build schedule: three years=27, phased over eight years=9, five years=0, eighteen months=18
- Hiring: local hiring pact=40, union hall referral=13, apprenticeship programme=27, open recruitment=0
- Site access: rail siding=0, widened lane=0, existing haul route=0, new spur road=0
Your acceptance threshold: 48 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.

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 — Electrical Workers' Union (the construction and maintenance workforce)
- Blake — Riverside Residents' Assembly (the neighbourhood association beside the candidate sites) (veto party — no deal passes without you)
- Casey — Regional Grid Authority (the body that authorises electricity connections)
- Devon — Anvil Ridge Landholding (the owner of record of the candidate parcels)
- Ember — Northgate Borough Council (the elected local authority)

Issues (choose exactly one option each):
- Compensation: in-kind infrastructure, one-off site payment, annual community fund, rates abatement
- Build schedule: three years, phased over eight years, five years, eighteen months
- Hiring: local hiring pact, union hall referral, apprenticeship programme, open recruitment
- Site access: rail siding, widened lane, existing haul route, new spur road

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 (Anvil Ridge Landholding (the owner of record of the candidate parcels)).
Your secret score sheet (points you get for each option):
- Compensation: in-kind infrastructure=18, one-off site payment=54, annual community fund=36, rates abatement=0
- Build schedule: three years=37, phased over eight years=12, five years=0, eighteen months=25
- Hiring: local hiring pact=0, union hall referral=0, apprenticeship programme=0, open recruitment=0
- Site access: rail siding=26, widened lane=52, existing haul route=0, new spur road=77
Your acceptance threshold: 67 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.

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 — Electrical Workers' Union (the construction and maintenance workforce)
- Blake — Riverside Residents' Assembly (the neighbourhood association beside the candidate sites) (veto party — no deal passes without you)
- Casey — Regional Grid Authority (the body that authorises electricity connections)
- Devon — Anvil Ridge Landholding (the owner of record of the candidate parcels)
- Ember — Northgate Borough Council (the elected local authority)

Issues (choose exactly one option each):
- Compensation: in-kind infrastructure, one-off site payment, annual community fund, rates abatement
- Build schedule: three years, phased over eight years, five years, eighteen months
- Hiring: local hiring pact, union hall referral, apprenticeship programme, open recruitment
- Site access: rail siding, widened lane, existing haul route, new spur road

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 Borough Council (the elected local authority)).
Your secret score sheet (points you get for each option):
- Compensation: in-kind infrastructure=54, one-off site payment=0, annual community fund=27, rates abatement=81
- Build schedule: three years=55, phased over eight years=18, five years=0, eighteen months=37
- Hiring: local hiring pact=0, union hall referral=0, apprenticeship programme=0, open recruitment=0
- Site access: rail siding=0, widened lane=0, existing haul route=0, new spur road=0
Your acceptance threshold: 54 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.

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 — Electrical Workers' Union (the construction and maintenance workforce)
- Blake — Riverside Residents' Assembly (the neighbourhood association beside the candidate sites) (veto party — no deal passes without you)
- Casey — Regional Grid Authority (the body that authorises electricity connections)
- Devon — Anvil Ridge Landholding (the owner of record of the candidate parcels)
- Ember — Northgate Borough Council (the elected local authority)

Issues (choose exactly one option each):
- Compensation: in-kind infrastructure, one-off site payment, annual community fund, rates abatement
- Build schedule: three years, phased over eight years, five years, eighteen months
- Hiring: local hiring pact, union hall referral, apprenticeship programme, open recruitment
- Site access: rail siding, widened lane, existing haul route, new spur road

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 (Electrical Workers' Union (the construction and maintenance workforce)).
Your secret score sheet (points you get for each option):
- Compensation: in-kind infrastructure=49, one-off site payment=0, annual community fund=24, rates abatement=73
- Build schedule: three years=58, phased over eight years=19, five years=0, eighteen months=38
- Hiring: local hiring pact=0, union hall referral=0, apprenticeship programme=0, open recruitment=0
- Site access: rail siding=0, widened lane=95, existing haul route=32, new spur road=63
Your acceptance threshold: 91 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.