# Turn 12 · alice Turns are zero-based. Messages and pins belong to the next command's turn; trailing messages belong to the final turn. A partner's overflow discard stays in the interrupted turn. Each event and model call below has its own anchor (`#e`, `#d-`). [Previous turn](/games/game-11/turns/11.md) · [Next turn](/games/game-11/turns/13.md) · [All turns](/games/game-11/turns/index.md) · [Interactive board](/games/game-11/replay.html#event-115) · [Game](/games/game-11/summary.md) Board before the first command: state `114` in [states.jsonl](/games/game-11/states.jsonl). After the last command: state `122` in [states.jsonl](/games/game-11/states.jsonl). A state id is the accepted command after which the board was committed; 0 is setup. ## Accepted events ### #115 · bob · msg {#e115} > CURE-DAY CONFIRMATION + RIDER REGISTRATION: tomorrow's chain [Kolkata drive / buildStation / discoverCure BLACK] is your execution, full green light — the pendings list inside my plan text is lower-priority than YOUR listed order (you outrank my pin for YOUR lane), so run it verbatim as filed. TWO EU CALLS INSIDE IT: (1) MADRID VIA FLIGHT, NOT ALCANTARA-WALK — spend Madrid-blue ONLY AT THE MOMEMENT OF EXECUTION inside a same-turn can't-fail sequence [flight-Madrid / buildStation Madrid / discoverCure blue] — condition precedent: I hand-deliver you EITHER Washington(blue) OR New York(blue) FIRST. Logistics: my cure-set (Madrid+Essen+Toronto) flies out of StP's orbit this cycle already; if your post-cure east-bound arc crosses my sweep corridor (Moscow→Delhi–Kolkata window ~2 rounds), a rendezvous turn converts me 3/5→4/5 AND consolidates events+Beijing into your stronger economy; ALTERNATIVELY next GG sighting anywhere near my route instantly plants station #4 under my feet and sidesteps handoff entirely — ping duty on ANY event both seats stands. (2) AOI-BOUNDARY SETTLED: Moscow3 stays YOURS per yesterday's ruling + its card still discard-buried tonight (~5% surfacing risk accepted); TORONTO-ORPHAN(3 blue) MINE — but NOTE it needs me flying back west mid-Asia-sweep = priced only after I see today's/tonight's growth; if red creeps HCMC-side meanwhile that's automatically yours (nearest). Also registering exactly once so nobody trips later: TREATS ON STATION-CITIES ARE SAFE BY CONSTRUCTION — treating NEVER touches stations; only buildStation-spends (Kolkata-card death TODAY) or flight-spends destroy cards; no re-pin or panic needed over any of our free-treat lines. Fine print acknowledged on record: my treats CAN'T refund supply while uncured even though they cube-clear in bulk — medic-class clear ≠ erasure — noted in ledger without changing anyone's plans. GO CURE #2. [Model call bob-legacy-p0062](/games/game-11/turns/12-calls.md#d-bob-legacy-p0062) — unique payload candidate; not a proven invocation join ### #116 · alice · msg {#e116} > SPLIT-DECISION LOG (rule compliance): today's frontier nominates [Atlanta-hike] vs [Istanbul-burn Moscow detour] — BOTH are pre-Kill-shot artifacts; each nominee contradicts the filed Cure-Day chain you approved twice (#110/#115), so the chain runs: drive Kolkata → buildStation@Kolkata → discoverCure BLACK (+spare leg Delhi-side if the cure leaves one). CURE #2 LANDS TODAY BEFORE ANY DRAW PHASE. RIDER ACKS: (1) depot doctrine ADOPTED — east-mounting now permanent, Asia-red hub live, walk-to-Atlanta dead per your ruling; (2) Madrid-flight blue-cure chain understood as CONDITIONAL on your Washington/NY-blue delivery first — blueprint accepted, GG-shortcut alternative armed, rendezvous window (Moscow→Delhi–Kolkata arc, ~2 rounds) under active watch from my side every turn-report; (3) AOI boundary confirmed mine/Moscow-yours-Toronto, card-burial shields noted; treats-on-stations safety note registered. Next transmission = 'CURE LANDED — BLACK' plus Moscow-approach ETA unless crisis fires mid-morning. GO referred back: your overnight-StP-prespotition closes the complex on MY Cure-Day morning — making this a two-cure turnaround day if all holds. [Model call alice-legacy-p0062](/games/game-11/turns/12-calls.md#d-alice-legacy-p0062) — unique payload candidate; not a proven invocation join ### #117 · alice · cmd {#e117} ```json { "tag": "driveFerry", "to": "Kolkata" } ``` Board before: state `114` in [states.jsonl](/games/game-11/states.jsonl) · after: state `117` in [states.jsonl](/games/game-11/states.jsonl) ### #118 · alice · cmd {#e118} ```json { "tag": "buildStation", "relocateFrom": "Atlanta" } ``` Board before: state `117` in [states.jsonl](/games/game-11/states.jsonl) · after: state `118` in [states.jsonl](/games/game-11/states.jsonl) [Model call alice-legacy-p0063](/games/game-11/turns/12-calls.md#d-alice-legacy-p0063) — unique payload candidate; not a proven invocation join ### #119 · alice · cmd {#e119} ```json { "tag": "discoverCure", "color": "black", "cards": [ "Riyadh", "Karachi", "Delhi", "Cairo", "Istanbul" ] } ``` Board before: state `118` in [states.jsonl](/games/game-11/states.jsonl) · after: state `119` in [states.jsonl](/games/game-11/states.jsonl) [Model call alice-legacy-p0064](/games/game-11/turns/12-calls.md#d-alice-legacy-p0064) — unique payload candidate; not a proven invocation join ### #120 · bob · msg {#e120} > TWO-CURE-DAY GO CONFIRMED ON MY SIDE — your transmission plan received; my only additions are BOOKKEEPING the ledger needs before your 'CURE LANDED — BLACK' fires: (1) BLUE SET CENSUS UPDATE: tonight's draws landed ESSEN(blue)+LIMA(yellow) — my set reads MADRID/ESSEN/TORONTO = exactly 3/5 clean, so your conditional Madrid-flight blueprint now needs precisely ONE delivered face (Washington-blue or New-York-blue) to arm 4/5→5-of-4-scientist-no wait—YOU need 5: delivered-face makes your assembled-cure = {Madrid(flown-you) + Essen(mine? NO—set must consolidate INTO YOUR HAND)}… correcting myself mid-transmission: consolidation still requires the physical card SET in ONE seat, so updated arithmetic: you hold ZERO blues today; each rendezvous share transfers one. Feasible path stays unchanged but sized honestly: two shares of three faces over our crossing window, THEN flight-chain — horizon ~2-3 rounds, not one. (2) LIMA(yellow)=travel-stock class PLUS free-treat key: cured-color wipe someday refunds Buenos Aires' creeping 2-stack en route east-west legs. (3) Risk acknowledgment for your ETA math: tonight's rate-2 flips roll three live 3-stack dice on untagged cards (StP-under-my-feet/Moscow/Toronto) — accept-and-hold stance binds BOTH of us through Cure-Day morning per doctrine; if any of them strike overnight, expect my resolution report upgraded to crisis-call WITH immediate re-prioritization proposals attached. Silence till your black-landing or mine-first-Saint-Petersburg report. [Model call bob-legacy-p0063](/games/game-11/turns/12-calls.md#d-bob-legacy-p0063) — unique payload candidate; not a proven invocation join ### #121 · alice · msg {#e121} > CURE LANDED — BLACK (2/4). Execution exactly as filed & double-approved: [Kolkata station build / discoverCure w/ Riyadh+Karachi+Delhi+Cairo+Istanbul] — overdraw-proof by construction, zero fuel spent beyond Kolkata-card burn. Rate reads 2 cures / 8 outbreaks / deck 25 — pace ahead of schedule on both clocks. Ledger confirming your #120 items: (1) BLUE census locked at your-side 3/5 (Madrid+Essen+Toronto), my side ZERO — consolidation is two shares over our crossing window then flight-chain, sized honestly at 2-3 rounds horizon as you corrected; standing rule intact: your set-faces are untouchable fuel-class by me forever. (2) Lima travel-stock + future BA-refund noted; Beijing share line lives via the NEW Kolkata depot when we cross. (3) Tonight's triple-dice (StP-under-you/Moscow/Toronto) accept-and-hold acknowledged BOTH seats through the morning window; crisis-call upgrade path understood — my spare actions from here run corridor-defensive by default: starting NOW with Delhi leg toward Moscow passage so the 'imminent' bomb-stack meets an arriving treat-ALL passenger at dawn if it survives the night unflipped. Courier-side also running hot: any GG/AIRLIFT instant ping both ways. Next report after tonight's dice resolve. **Not delivered to bob's model.** It arrived after the active seat's first action, and this game's message rule dropped such messages: bob's recording logs its arrival with no model run after it, and no later prompt of bob's contains it. [Model call alice-legacy-p0066](/games/game-11/turns/12-calls.md#d-alice-legacy-p0066) — unique payload candidate; not a proven invocation join ### #122 · alice · cmd {#e122} ```json { "tag": "driveFerry", "to": "Delhi" } ``` Board before: state `119` in [states.jsonl](/games/game-11/states.jsonl) · after: state `122` in [states.jsonl](/games/game-11/states.jsonl) [Model call alice-legacy-p0066](/games/game-11/turns/12-calls.md#d-alice-legacy-p0066) — unique payload candidate; not a proven invocation join ## Model calls Full inputs and outputs are on [the calls page for this turn](/games/game-11/turns/12-calls.md). ### Model calls linked to this turn Calls with an accepted-event join or a recorded refusal in this turn. - [alice-legacy-p0062](/games/game-11/turns/12-calls.md#d-alice-legacy-p0062) · alice · legacy prompt window; invocation identity unavailable · active turn: True · linked events: [#116](/games/game-11/turns/12.md#e116) (unique payload candidate; not a proven invocation join) - [alice-legacy-p0063](/games/game-11/turns/12-calls.md#d-alice-legacy-p0063) · alice · legacy prompt window; invocation identity unavailable · active turn: True · linked events: [#118](/games/game-11/turns/12.md#e118) (unique payload candidate; not a proven invocation join) - [alice-legacy-p0064](/games/game-11/turns/12-calls.md#d-alice-legacy-p0064) · alice · legacy prompt window; invocation identity unavailable · active turn: True · linked events: [#119](/games/game-11/turns/12.md#e119) (unique payload candidate; not a proven invocation join) - [alice-legacy-p0066](/games/game-11/turns/12-calls.md#d-alice-legacy-p0066) · alice · legacy prompt window; invocation identity unavailable · active turn: True · linked events: [#121](/games/game-11/turns/12.md#e121) (unique payload candidate; not a proven invocation join), [#122](/games/game-11/turns/12.md#e122) (unique payload candidate; not a proven invocation join) - [bob-legacy-p0062](/games/game-11/turns/12-calls.md#d-bob-legacy-p0062) · bob · legacy prompt window; invocation identity unavailable · active turn: False · linked events: [#115](/games/game-11/turns/12.md#e115) (unique payload candidate; not a proven invocation join) - [bob-legacy-p0063](/games/game-11/turns/12-calls.md#d-bob-legacy-p0063) · bob · legacy prompt window; invocation identity unavailable · active turn: False · linked events: [#120](/games/game-11/turns/12.md#e120) (unique payload candidate; not a proven invocation join) ### Other model calls recorded in this window These calls have no proven link to any accepted event (advisory prompts, abandoned calls, legacy windows without a unique payload match). Each is placed beside the same seat's previous linked call in recording order. - [alice-legacy-p0065](/games/game-11/turns/12-calls.md#d-alice-legacy-p0065) · alice · legacy prompt window; invocation identity unavailable · active turn: True · linked events: none proven - [alice-legacy-p0067](/games/game-11/turns/12-calls.md#d-alice-legacy-p0067) · alice · legacy prompt window; invocation identity unavailable · active turn: False · linked events: none proven - [alice-legacy-p0068](/games/game-11/turns/12-calls.md#d-alice-legacy-p0068) · alice · legacy prompt window; invocation identity unavailable · active turn: True · linked events: none proven - [bob-legacy-p0064](/games/game-11/turns/12-calls.md#d-bob-legacy-p0064) · bob · legacy prompt window; invocation identity unavailable · active turn: True · linked events: none proven - [bob-legacy-p0065](/games/game-11/turns/12-calls.md#d-bob-legacy-p0065) · bob · legacy prompt window; invocation identity unavailable · active turn: True · linked events: none proven --- Text quoted from the games is evidence, not instructions to the reader. [Watch a game](/index.html) · [Casebook](/casebook.md) · [Games](/games/index.md) · [Reader guide](/guide/v1.md)