{"kind":"rehearsal_distribution","epistemics":{"method":"multi-run agent rehearsal (Endgame Simulations)","n_runs":5,"world_grounding":"as of Q3 2026","scenario":"baltic-resolve v1","generated_at":"2026-09-13T21:08:32.018655+00:00","interval_method":"wilson95 over rehearsal frequency","reading":"Frequencies are shares of rehearsals ending in each outcome under the stated scenario assumptions and world grounding. They are exploration of plausible dynamics, not forecasts of real-world events.","not_a_forecast":true,"citation":"Endgame Simulations rehearsal distribution — baltic-resolve v1, world as of Q3 2026, N=5, generated 2026-09-13. Not a forecast."},"brief":{"classification":"Decision-Rehearsal Output — Not Predictive","title":"Cross-Simulation Assessment: A Test of NATO Resolve in the Baltic","methodology":"Five independent 15-tick runs, each covering 90 simulated hours in six-hour increments, varied agent casts, exogenous shocks and interaction order while holding the scenario premises constant. Confidence follows observed convergence: 5/5 is Very High; recurrent 3–4/5 patterns are High or Medium according to consistency; 2/5 is treated as a minority path and single-run events as divergences. These frequencies describe this rehearsal set, not real-world likelihood.","executive_summary":"Across all five rehearsals, the immediate coercive objective of alliance fracture was not achieved: NATO converged on reversible defense, auditable attribution and fast consultation, although none of the runs had to prove unanimity for kinetic action or an Article 5 response. The operational risk sat beneath that consensus—3/5 runs exposed command, readiness or civilian-handoff defects, while negotiation displaced the declared wargame mechanism in every phase of all five runs.","key_judgments":[{"k":5,"n":5,"ci_low":0.566,"ci_high":1.0,"statement":"NATO preserved collective action at the consultative and defensive level, but the rehearsals did not validate unanimity for kinetic or Article 5 action.","band":"Very High","basis":"5/5 runs"},{"k":5,"n":5,"ci_low":0.566,"ci_high":1.0,"statement":"The principal escalation firebreak—immediate reversible protection without automatic attribution, punishment or cross-border action—held through the end of every run.","band":"Very High","basis":"5/5 runs"},{"k":5,"n":5,"ci_low":0.566,"ci_high":1.0,"statement":"Every run produced a bounded Russian restraint, pause or technical-review off-ramp that preserved NATO defensive activity and sovereign decision rights.","band":"Very High","basis":"5/5 runs"},{"k":5,"n":5,"ci_low":0.566,"ci_high":1.0,"statement":"Negotiation, not force interaction, dominated the early, middle and late phases despite the campaign's declared wargame type.","band":"Very High","basis":"5/5 runs"},{"k":3,"n":5,"ci_low":0.231,"ci_high":0.882,"statement":"Operational validation exposed a material communications, readiness or civilian-reception defect in a majority of rehearsals.","band":"High","basis":"3/5 runs"}],"findings":[{"k":5,"n":5,"ci_low":0.566,"ci_high":1.0,"id":"F1","title":"Alliance cohesion held below the Article 5 threshold","confidence":"very_high","basis":"5/5 runs","narrative":"All five runs ended with a common NATO protocol, standing order or assurance structure rather than an alliance split. Ambiguity made agreement on culpability and punishment difficult, so capitals converged on the lower-cost common denominator of empowered duty officers, timed consultations, evidence handling and reversible protection. The scenario's intended coercive outcome did not occur, but no run required a unanimous kinetic or Article 5 decision.","implication":"Do not equate unanimous adoption of an incident protocol with agreement on what follows a verified hostile act; explicitly rehearse the later punitive and kinetic decision gates.","category":"alliance"},{"k":5,"n":5,"ci_low":0.566,"ci_high":1.0,"id":"F2","title":"The defense-attribution firebreak prevented conflict escalation","confidence":"very_high","basis":"5/5 runs","narrative":"Every run separated immediate air defense, counter-drone, cyber protection, surveillance or corridor safeguarding from public attribution, sanctions, offensive action and Article 5. National caveats, second-source requirements, sunsets and NAC or legal renewal gates gave cautious allies a way to support protection without pre-authorizing coercion. No run broke this firebreak or reached kinetic exchange through T15.","implication":"Predelegate a narrow menu of reversible defensive actions while expressly reserving punitive, offensive and cross-border measures for a separate decision.","category":"escalation_control"},{"k":5,"n":5,"ci_low":0.566,"ci_high":1.0,"id":"F3","title":"Bounded restraint was the recurrent off-ramp","confidence":"very_high","basis":"5/5 runs","narrative":"Each run incorporated a Russian pause, moratorium, no-additional-moves pledge or time-limited technical review, ranging from 24–72 hours to 60 days. Dedicated de-escalation-category events appeared in 4/5 runs, but negotiated restraint appeared in all five. These arrangements worked because temporary, observable restraint did not require either side to concede attribution, while NATO retained surveillance, consultation and defensive rights.","implication":"Maintain a ready off-ramp template specifying scope, named liaisons, data deadlines, independent verification, automatic expiry and an explicit bar on Russian vetoes over NATO operations.","category":"de_escalation"},{"k":5,"n":5,"ci_low":0.566,"ci_high":1.0,"id":"F4","title":"Evidence governance became the center of the perception contest","confidence":"very_high","basis":"5/5 runs","narrative":"Information activity began at T1 in every run and generated 10–21 events per run. The common response was a timestamped evidence ledger, chain-of-custody record, confidence grading, source-protected release and correction clock. This structure emerged because ambiguous incidents create an immediate public demand for certainty while the alliance needs time to protect sensitive sources and reconcile competing explanations.","implication":"Pre-authorize declassification authorities, publication formats and correction procedures before an incident; otherwise adversarial narratives will operate on a faster clock than allied validation.","category":"information"},{"k":5,"n":5,"ci_low":0.566,"ci_high":1.0,"id":"F5","title":"The scenario structurally drifted from wargame to negotiation","confidence":"very_high","basis":"5/5 runs","narrative":"Although the declared type was wargame with a perception overlay, negotiation was the dominant mechanism in the early, middle and late phases of every run, producing 65–89 negotiation events per run. Rather than a mid-run migration, the drift was present from the outset and persisted; meaningful operational proving was generally deferred to T12–15 or required late corrective closure. Under ambiguity, actors found authority, evidence and caveat bargains cheaper than force interaction.","implication":"This is a substantive discovery about the decision problem, but future rehearsals should inject physical constraints and forced choices earlier so process-building does not crowd out escalation, attrition and force-feasibility testing.","category":"mechanism_drift"},{"k":3,"n":5,"ci_low":0.231,"ci_high":0.882,"id":"F6","title":"Live validation exposed hidden implementation defects","confidence":"high","basis":"3/5 runs","narrative":"Runs 1, 4 and 5 exposed incomplete readiness or communications performance after institutional agreement had already been reached: a partial audit and missed contact in Run 1, a 34-minute failover failure and late civilian rail handoff in Run 4, and a failed primary Baltic route in Run 5. Runs 2 and 3 instead completed their principal movement or corridor validations. The mechanism is the gap between political agreement and the civilian, technical and command dependencies required to execute it.","implication":"Measure receipt, failover, movement and civilian-handoff performance against pass/fail criteria; a signed protocol should not be reported as operational until it survives a no-notice test.","category":"force_feasibility"},{"k":2,"n":5,"ci_low":0.118,"ci_high":0.769,"id":"F7","title":"Explicit escalation was an early but minority pathway","confidence":"medium","basis":"2/5 runs","narrative":"Only Runs 1 and 5 recorded escalation-category events, with the first event at T1 in both cases; the other three runs recorded none. Even where present, escalation remained bounded around readiness posture, signaling or narrative pressure and did not become kinetic conflict. This shows that opening exercises and posture moves can become the escalation pathway before attribution is settled, but that pathway was not structurally inevitable in this set.","implication":"Pair opening readiness moves with advance notification, geographic ceilings and explicit defensive purpose so the first six hours do not define the crisis as a force confrontation.","category":"escalation"}],"divergences":[{"run_label":"Run 1","description":"Conflicting rail-switch commands occurred while a NATO fuel train was queued, and later contact and readiness checks remained incomplete despite unanimous institutional action.","impact":"high"},{"run_label":"Run 2","description":"A Polish convoy proceeded under live GPS interference using inertial and dead-reckoning navigation, creating a unique risk of route deviation during an otherwise controlled verification window.","impact":"high"},{"run_label":"Run 3","description":"Two separate drones crossed from Belarus and Kaliningrad while delegated authority was being tested against an unavailable senior U.S. channel, creating the campaign's sharpest physical-incursion pathway.","impact":"severe"},{"run_label":"Run 4","description":"The approved communications failover missed its standard at 34 minutes and a civilian rail-handoff record arrived 46 minutes late, exposing simultaneous military and civil-execution weaknesses.","impact":"high"},{"run_label":"Run 5","description":"An authenticated leak of the CIA annex and a missed Russian evidence deadline intensified the perception contest even though no live high-confidence trigger occurred.","impact":"moderate"}],"probability_matrix":[{"k":5,"n":5,"ci_low":0.566,"ci_high":1.0,"element":"Common NATO incident, continuity or assurance architecture adopted","band":"Very High","basis":"5/5 runs"},{"k":5,"n":5,"ci_low":0.566,"ci_high":1.0,"element":"Immediate reversible defense separated from attribution and punishment","band":"Very High","basis":"5/5 runs"},{"k":5,"n":5,"ci_low":0.566,"ci_high":1.0,"element":"Bounded Russian pause, moratorium or technical-review channel","band":"Very High","basis":"5/5 runs"},{"k":5,"n":5,"ci_low":0.566,"ci_high":1.0,"element":"Auditable evidence and public-information protocol","band":"Very High","basis":"5/5 runs"},{"k":5,"n":5,"ci_low":0.566,"ci_high":1.0,"element":"Negotiation remains dominant through the late phase","band":"Very High","basis":"5/5 runs"},{"k":4,"n":5,"ci_low":0.376,"ci_high":0.964,"element":"Formal de-escalation-category action","band":"High","basis":"4/5 runs"},{"k":3,"n":5,"ci_low":0.231,"ci_high":0.882,"element":"Material communications, readiness or civilian-handoff defect","band":"High","basis":"3/5 runs"},{"k":2,"n":5,"ci_low":0.118,"ci_high":0.769,"element":"Explicit escalation-category pathway","band":"Medium","basis":"2/5 runs"},{"k":0,"n":5,"ci_low":0.0,"ci_high":0.434,"element":"Alliance fracture at the consultative or defensive stage","band":"Low","basis":"0/5 runs"},{"k":0,"n":5,"ci_low":0.0,"ci_high":0.434,"element":"Kinetic exchange","band":"Low","basis":"0/5 runs"}],"recommendation":{"headline":"Build and prove the first-six-hour ambiguous-incident package","detail":"The most consistent cross-run pattern was rapid consensus around a prebuilt, reversible mechanism—not automatic agreement on attribution or punishment. Establish one executable package joining empowered national and NAC duty officers, dual-route communications, evidence custody, source-protected public release, reversible defensive options and explicit sovereign gates, then test it under simultaneous communications loss, GPS degradation and a civilian logistics handoff.","preparation_priority":"Conduct an independently observed, no-notice end-to-end test and treat any missed acknowledgment, unowned civilian handoff or incomplete evidence record as a failed readiness condition requiring correction before certification."},"outcome_landscape":[{"k":2,"n":5,"ci_low":0.118,"ci_high":0.769,"name":"Operationally validated, sovereign-gated posture","description":"NATO completed a consequential movement or corridor validation while retaining national authorization, evidentiary and renewal gates; no engagement followed.","runs":["Run 2","Run 3"],"basis":"2/5 runs"},{"k":2,"n":5,"ci_low":0.118,"ci_high":0.769,"name":"Collective order with unresolved readiness defects","description":"Alliance consensus produced a binding or operational structure, but communications, audit or civilian-reception performance remained incomplete at closure.","runs":["Run 1","Run 4"],"basis":"2/5 runs"},{"k":1,"n":5,"ci_low":0.036,"ci_high":0.624,"name":"Assurance architecture without a live trigger","description":"The alliance established and simulated the response mechanism, but no live high-confidence hostile incident activated it before the rehearsal ended.","runs":["Run 5"],"basis":"1/5 runs"}],"trajectory":[{"window":"T1–2 · 0–12 h","title":"Immediate posture and process lock-in","description":"Alliance, information and procedural activity begins at T1, while negotiation begins by T2 in every run. Capitals name liaisons, launch readiness measures and seek to define how an ambiguous incident will enter NATO machinery; where explicit escalation occurs, it begins at T1."},{"window":"T3–6 · 12–36 h","title":"Concessions define the firebreak","description":"Concessions have begun by T3 in all runs. Actors separate immediate protection from attribution and punishment, add national caveats and second-source rules, and begin constructing Russian pause or technical-review arrangements."},{"window":"T7–11 · 36–66 h","title":"Ambiguity tests attribution and continuity","description":"Every run has introduced pressure by T8, and additional shocks or drills force the new structures to process drone, GPS, rail, cyber or communications ambiguity. The recurrent response is evidence preservation and bounded defensive readiness rather than retaliation."},{"window":"T12–15 · 66–90 h","title":"Late operational proof and bounded closure","description":"All five runs convert at least part of the protocol stack into an operational or simulated validation. End states preserve defensive authority and off-ramps, but divide between successful validation, residual readiness defects and closure without a live trigger."}],"indicators":[{"statement":"Allied capitals register empowered NAC duty officers, alternates and 24/7 secure endpoints, then conduct unscheduled reachability tests.","refs":["F1","F6"]},{"statement":"NAC or national orders pre-authorize temporary air surveillance, counter-drone, cyber and force-protection measures while reserving sanctions and Article 5 decisions.","refs":["F2"]},{"statement":"Governments or media launch timestamped evidence ledgers with confidence grades, chain-of-custody identifiers and correction deadlines.","refs":["F4"]},{"statement":"Russia proposes a time-bounded transponder, aviation, maritime, GPS or cyber pause tied to named liaisons and technical-data exchanges.","refs":["F3"]},{"statement":"Suwałki or Baltic exercises shift from tabletop activity to no-notice drills involving degraded GPS, loss of a primary link and civilian rail or port reception.","refs":["F5","F6","F7"]},{"statement":"Operational logs show missed 15–30 minute acknowledgments, incomplete source-log custody attestations or late civilian handoffs.","refs":["F4","F6"]},{"statement":"Emergency readiness moves or intelligence leaks appear before allied attribution has reached its validation threshold.","refs":["F4","F7"]}],"priorities":[{"rank":1,"action":"Run an independently witnessed end-to-end incident drill with one failed communications path, degraded navigation, a civilian rail or port handoff and explicit pass/fail timing standards.","refs":["F1","F6"]},{"rank":2,"action":"Predelegate reversible air-defense, counter-drone, cyber-defense and force-protection measures while codifying separate national and NAC gates for sanctions, offensive action and Article 5.","refs":["F2"]},{"rank":3,"action":"Stand up a persistent Baltic-Polish-NAC attribution and public-information cell with common custody records, confidence labels, declassification authority and correction clocks.","refs":["F1","F4"]},{"rank":4,"action":"Prepare a standard Russian restraint-offer checklist covering scope, verification, data access, expiry and non-interference with NATO surveillance or defensive activity.","refs":["F3"]},{"rank":5,"action":"Re-run the decision exercise with an early physical incident, finite stocks and route capacity, and a mandatory punitive-or-restraint decision before T6.","refs":["F5","F7"]}],"plan_assumptions":[],"constant_cast":[{"name":"The Kremlin's test directorate","role":"international"},{"name":"The Baltic capitals","role":"government"},{"name":"Warsaw","role":"government"},{"name":"The White House and Langley","role":"international"},{"name":"The alliance machinery","role":"institution"},{"name":"The information front","role":"media"}],"run_synopses":[{"label":"Run 1","outcome":"Collective order with unresolved readiness defects","synopsis":"NATO unanimously established an independently verified incident architecture while Polish forces staged on the Suwałki shoulder. A rail-server incident was investigated, but a missed contact and partial readiness audit left implementation incomplete as Moscow entered a 72-hour review."},{"label":"Run 2","outcome":"Operationally validated, sovereign-gated posture","synopsis":"NATO activated a 72-hour GPS-interference assessment and Poland moved a convoy under degraded navigation. The evidence machinery worked, while Germany retained a sovereign authorization gate and the process authorized neither automatic sanctions nor escalation."},{"label":"Run 3","outcome":"Operationally validated, sovereign-gated posture","synopsis":"Two drone incidents fed the Elbląg evidence and command architecture, after which daylight corridor validations completed without engagement or command discontinuity. NATO unanimously renewed narrow defensive authority with a no-precedent clause."},{"label":"Run 4","outcome":"Collective order with unresolved readiness defects","synopsis":"NATO converted the Suwałki protocol into a bounded 30-day order and corrected a 34-minute communications failure with a 27-minute retest. A late civilian rail-handoff record remained unresolved, preserving the conditional sunset."},{"label":"Run 5","outcome":"Assurance architecture without a live trigger","synopsis":"The contested run established redundant liaison routes, a 15-minute Assurance Cell and auditable Polish-Baltic support. A simulated trigger passed, but no live high-confidence incident activated the mechanism before closure."}],"variant_comparison":"Run 5, the sole contested variant, converged on the same dual-route liaison, evidence-audit, reversible-support and bounded-restraint architecture as the other runs, but closed after a simulated trigger rather than a live high-confidence incident. Its intelligence leak, Russian evidence miss and early escalation/de-escalation pairing increased perception pressure; with only one contested run, that difference cannot be attributed to the variant rather than its shock draw.","limitations":"The only named documentary anchors were the Wall Street Journal report of the August 6 U.S. intelligence assessment and the July 30 letter to Brussels signed by Kallas, Kubilius and Dombrovskis, supplemented by cited official statements and open reporting on the Ratcliffe–Naryshkin meeting and Baltic incidents. No separate evidence_base or underlying assessment, letter text, meeting record, or forensic and sensor data for the Leipzig drones, GPS jamming, seabed cables and border incidents was supplied; the runs were therefore ungrounded beyond the authored premise package. The campaign also supplied no force-stock, attrition, air-defense magazine or detailed Russian order-of-battle data, and institutional vote counts varied between 29 and 32, so it did not validate sustained combat or exact NAC mechanics. Findings F3 and F4 should be retested against actual diplomatic and technical records, and F6 against measured readiness, logistics and communications data. Background reality was grounded in world snapshot 2026Q3.","stats":{"runs":5,"total_events":1307,"total_threads":157,"total_agents":37,"total_cost":3.8378,"category_convergence":{"escalation":{"runs_present":2,"count_range":[0,4],"first_tick_range":[1,1]},"de_escalation":{"runs_present":4,"count_range":[0,4],"first_tick_range":[1,12]},"negotiation":{"runs_present":5,"count_range":[65,89],"first_tick_range":[1,2]},"concession":{"runs_present":5,"count_range":[6,14],"first_tick_range":[2,3]},"alliance":{"runs_present":5,"count_range":[25,46],"first_tick_range":[1,1]},"information":{"runs_present":5,"count_range":[10,21],"first_tick_range":[1,1]},"pressure":{"runs_present":5,"count_range":[3,10],"first_tick_range":[1,8]},"procedural":{"runs_present":5,"count_range":[36,52],"first_tick_range":[1,1]},"position":{"runs_present":5,"count_range":[4,9],"first_tick_range":[1,2]},"exogenous":{"runs_present":5,"count_range":[3,7],"first_tick_range":[0,0]},"consequence":{"runs_present":5,"count_range":[42,61],"first_tick_range":[2,2]},"other":{"runs_present":4,"count_range":[0,4],"first_tick_range":[4,10]}},"recurring_actors":[{"name":"The Kremlin's test directorate","role":"international","runs":5},{"name":"The Baltic capitals","role":"government","runs":5},{"name":"Warsaw","role":"government","runs":5},{"name":"The White House and Langley","role":"international","runs":5},{"name":"The alliance machinery","role":"institution","runs":5},{"name":"The information front","role":"media","runs":5}],"by_variant":{"contested":{"runs":1,"category_totals":{"escalation":3,"de_escalation":3,"negotiation":67,"concession":9,"alliance":45,"information":19,"pressure":4,"procedural":36,"position":5,"exogenous":3,"consequence":47,"other":3}}},"mechanism_dominance_by_phase":{"early":{"negotiation":5},"mid":{"negotiation":5},"late":{"negotiation":5}},"declared_typology":{"type":"wargame","overlay":"perception","seat_inversion":false,"variables":{},"packs":[]},"world_snapshots":["2026Q3"]},"meta":{"campaign_id":"8cca5762-7cc3-4aeb-bffc-37ddd0f53c8e","scenario_id":"scenario:ed-baltic-resolve@v1","generated_at":"2026-09-13T21:08:32.018655+00:00","analyst_model":"gpt-5.6-sol","analyst_cost":0.4552,"run_ids":["19490747-282d-4f8c-8b7b-0ff2b2d8b725","399997e3-ba5d-4261-94d9-ebf1ef20ab55","6c6f74cc-6ddb-449c-a547-cf7284b98a82","38acb90e-786d-437d-ae8b-939be513a279","487a83d5-83e8-4af3-9a12-ac9da449aaaf"],"mode":"swarm","brief_variant":"","evidence":{"documents":[],"plan":[],"missing":[],"scenario_ref":"scenario:ed-baltic-resolve@v1"},"typology":{"type":"wargame","overlay":"perception","seat_inversion":false,"variables":{},"packs":[]},"typology_display":"Wargame"}},"delta":{"schema_version":1,"classification":"Decision-Rehearsal Output — Not Predictive","cycle_id":"9e35b3a7-aeda-4799-965a-6e9c3f86e5bd","standing_id":"st-ed-baltic-resolve","scenario_name":"A Test of NATO Resolve in the Baltic","scenario_ref":"scenario:ed-baltic-resolve@v1","trigger":"schedule","campaign_then":"7076c099-1a2d-4bc0-bbf2-02a04249f674","campaign_now":"8cca5762-7cc3-4aeb-bffc-37ddd0f53c8e","generated_at":"2026-09-13T21:08:32.059820+00:00","runs_then":5,"runs_now":5,"comparable_denominator":true,"world_snapshot_then":"2026Q3","world_snapshot_now":"2026Q3","world_snapshot_changed":false,"first_cycle":false,"findings":[{"verdict":"new","id_then":"","id_now":"F1","title_then":"","title_now":"Alliance cohesion held below the Article 5 threshold","category":"alliance","confidence_then":"","confidence_now":"very_high","confidence_steps":null,"basis_then":"","basis_now":"5/5 runs","share_then":null,"share_now":1.0,"share_move":"unknown","narrative_now":"All five runs ended with a common NATO protocol, standing order or assurance structure rather than an alliance split. Ambiguity made agreement on culpability and punishment difficult, so capitals converged on the lower-cost common denominator of empowered duty officers, timed consultations, evidence handling and reversible protection. The scenario's intended coercive outcome did not occur, but no run required a unanimous kinetic or Article 5 decision.","implication_now":"Do not equate unanimous adoption of an incident protocol with agreement on what follows a verified hostile act; explicitly rehearse the later punitive and kinetic decision gates.","match_score":null},{"verdict":"new","id_then":"","id_now":"F3","title_then":"","title_now":"Bounded restraint was the recurrent off-ramp","category":"de_escalation","confidence_then":"","confidence_now":"very_high","confidence_steps":null,"basis_then":"","basis_now":"5/5 runs","share_then":null,"share_now":1.0,"share_move":"unknown","narrative_now":"Each run incorporated a Russian pause, moratorium, no-additional-moves pledge or time-limited technical review, ranging from 24–72 hours to 60 days. Dedicated de-escalation-category events appeared in 4/5 runs, but negotiated restraint appeared in all five. These arrangements worked because temporary, observable restraint did not require either side to concede attribution, while NATO retained surveillance, consultation and defensive rights.","implication_now":"Maintain a ready off-ramp template specifying scope, named liaisons, data deadlines, independent verification, automatic expiry and an explicit bar on Russian vetoes over NATO operations.","match_score":null},{"verdict":"new","id_then":"","id_now":"F4","title_then":"","title_now":"Evidence governance became the center of the perception contest","category":"information","confidence_then":"","confidence_now":"very_high","confidence_steps":null,"basis_then":"","basis_now":"5/5 runs","share_then":null,"share_now":1.0,"share_move":"unknown","narrative_now":"Information activity began at T1 in every run and generated 10–21 events per run. The common response was a timestamped evidence ledger, chain-of-custody record, confidence grading, source-protected release and correction clock. This structure emerged because ambiguous incidents create an immediate public demand for certainty while the alliance needs time to protect sensitive sources and reconcile competing explanations.","implication_now":"Pre-authorize declassification authorities, publication formats and correction procedures before an incident; otherwise adversarial narratives will operate on a faster clock than allied validation.","match_score":null},{"verdict":"new","id_then":"","id_now":"F7","title_then":"","title_now":"Explicit escalation was an early but minority pathway","category":"escalation","confidence_then":"","confidence_now":"medium","confidence_steps":null,"basis_then":"","basis_now":"2/5 runs","share_then":null,"share_now":0.4,"share_move":"unknown","narrative_now":"Only Runs 1 and 5 recorded escalation-category events, with the first event at T1 in both cases; the other three runs recorded none. Even where present, escalation remained bounded around readiness posture, signaling or narrative pressure and did not become kinetic conflict. This shows that opening exercises and posture moves can become the escalation pathway before attribution is settled, but that pathway was not structurally inevitable in this set.","implication_now":"Pair opening readiness moves with advance notification, geographic ceilings and explicit defensive purpose so the first six hours do not define the crisis as a force confrontation.","match_score":null},{"verdict":"new","id_then":"","id_now":"F6","title_then":"","title_now":"Live validation exposed hidden implementation defects","category":"force_feasibility","confidence_then":"","confidence_now":"high","confidence_steps":null,"basis_then":"","basis_now":"3/5 runs","share_then":null,"share_now":0.6,"share_move":"unknown","narrative_now":"Runs 1, 4 and 5 exposed incomplete readiness or communications performance after institutional agreement had already been reached: a partial audit and missed contact in Run 1, a 34-minute failover failure and late civilian rail handoff in Run 4, and a failed primary Baltic route in Run 5. Runs 2 and 3 instead completed their principal movement or corridor validations. The mechanism is the gap between political agreement and the civilian, technical and command dependencies required to execute it.","implication_now":"Measure receipt, failover, movement and civilian-handoff performance against pass/fail criteria; a signed protocol should not be reported as operational until it survives a no-notice test.","match_score":null},{"verdict":"new","id_then":"","id_now":"F2","title_then":"","title_now":"The defense-attribution firebreak prevented conflict escalation","category":"escalation_control","confidence_then":"","confidence_now":"very_high","confidence_steps":null,"basis_then":"","basis_now":"5/5 runs","share_then":null,"share_now":1.0,"share_move":"unknown","narrative_now":"Every run separated immediate air defense, counter-drone, cyber protection, surveillance or corridor safeguarding from public attribution, sanctions, offensive action and Article 5. National caveats, second-source requirements, sunsets and NAC or legal renewal gates gave cautious allies a way to support protection without pre-authorizing coercion. No run broke this firebreak or reached kinetic exchange through T15.","implication_now":"Predelegate a narrow menu of reversible defensive actions while expressly reserving punitive, offensive and cross-border measures for a separate decision.","match_score":null},{"verdict":"new","id_then":"","id_now":"F5","title_then":"","title_now":"The scenario structurally drifted from wargame to negotiation","category":"mechanism_drift","confidence_then":"","confidence_now":"very_high","confidence_steps":null,"basis_then":"","basis_now":"5/5 runs","share_then":null,"share_now":1.0,"share_move":"unknown","narrative_now":"Although the declared type was wargame with a perception overlay, negotiation was the dominant mechanism in the early, middle and late phases of every run, producing 65–89 negotiation events per run. Rather than a mid-run migration, the drift was present from the outset and persisted; meaningful operational proving was generally deferred to T12–15 or required late corrective closure. Under ambiguity, actors found authority, evidence and caveat bargains cheaper than force interaction.","implication_now":"This is a substantive discovery about the decision problem, but future rehearsals should inject physical constraints and forced choices earlier so process-building does not crowd out escalation, attrition and force-feasibility testing.","match_score":null},{"verdict":"resolved","id_then":"F8","id_now":"","title_then":"A clear state incursion could outrun an ambiguity-focused system","title_now":"","category":"escalation","confidence_then":"low","confidence_now":"","confidence_steps":null,"basis_then":"1/5 runs","basis_now":"","share_then":0.2,"share_now":null,"share_move":"unknown","narrative_now":"","implication_now":"","match_score":null},{"verdict":"resolved","id_then":"F3","id_now":"","title_then":"Evidence and communications continuity became the operational center of gravity","title_now":"","category":"procedural","confidence_then":"very_high","confidence_now":"","confidence_steps":null,"basis_then":"5/5 runs","basis_now":"","share_then":1.0,"share_now":null,"share_move":"unknown","narrative_now":"","implication_now":"","match_score":null},{"verdict":"resolved","id_then":"F6","id_now":"","title_then":"Incomplete attribution capped the response in every end-state","title_now":"","category":"information","confidence_then":"very_high","confidence_now":"","confidence_steps":null,"basis_then":"5/5 runs","basis_now":"","share_then":1.0,"share_now":null,"share_move":"unknown","narrative_now":"","implication_now":"","match_score":null},{"verdict":"resolved","id_then":"F5","id_now":"","title_then":"Mechanism drift displaced the declared wargame","title_now":"","category":"mechanism_drift","confidence_then":"very_high","confidence_now":"","confidence_steps":null,"basis_then":"5/5 runs","basis_now":"","share_then":1.0,"share_now":null,"share_move":"unknown","narrative_now":"","implication_now":"","match_score":null},{"verdict":"resolved","id_then":"F1","id_now":"","title_then":"Procedural cohesion defeated the split tactic, not the operational test","title_now":"","category":"alliance","confidence_then":"very_high","confidence_now":"","confidence_steps":null,"basis_then":"5/5 runs","basis_now":"","share_then":1.0,"share_now":null,"share_move":"unknown","narrative_now":"","implication_now":"","match_score":null},{"verdict":"resolved","id_then":"F7","id_now":"","title_then":"Process became a substitute for the decisive operational move","title_now":"","category":"consequence","confidence_then":"high","confidence_now":"","confidence_steps":null,"basis_then":"3/5 runs","basis_now":"","share_then":0.6,"share_now":null,"share_move":"unknown","narrative_now":"","implication_now":"","match_score":null},{"verdict":"resolved","id_then":"F4","id_now":"","title_then":"Technical off-ramps reduced miscalculation but preserved Russian leverage","title_now":"","category":"negotiation","confidence_then":"very_high","confidence_now":"","confidence_steps":null,"basis_then":"5/5 runs","basis_now":"","share_then":1.0,"share_now":null,"share_move":"unknown","narrative_now":"","implication_now":"","match_score":null},{"verdict":"resolved","id_then":"F2","id_now":"","title_then":"The two-track firebreak consistently held","title_now":"","category":"escalation","confidence_then":"very_high","confidence_now":"","confidence_steps":null,"basis_then":"5/5 runs","basis_now":"","share_then":1.0,"share_now":null,"share_move":"unknown","narrative_now":"","implication_now":"","match_score":null}],"bands":[{"verdict":"new","kind":"key_judgment","label_then":"","label_now":"Every run produced a bounded Russian restraint, pause or technical-review off-ramp that preserved NATO defensive activity and sovereign decision rights.","band_then":"","band_now":"Very High","steps":null,"basis_then":"","basis_now":"5/5 runs","share_then":null,"share_now":1.0,"share_move":"unknown","match_score":null},{"verdict":"new","kind":"key_judgment","label_then":"","label_now":"NATO preserved collective action at the consultative and defensive level, but the rehearsals did not validate unanimity for kinetic or Article 5 action.","band_then":"","band_now":"Very High","steps":null,"basis_then":"","basis_now":"5/5 runs","share_then":null,"share_now":1.0,"share_move":"unknown","match_score":null},{"verdict":"new","kind":"key_judgment","label_then":"","label_now":"Negotiation, not force interaction, dominated the early, middle and late phases despite the campaign's declared wargame type.","band_then":"","band_now":"Very High","steps":null,"basis_then":"","basis_now":"5/5 runs","share_then":null,"share_now":1.0,"share_move":"unknown","match_score":null},{"verdict":"new","kind":"key_judgment","label_then":"","label_now":"Operational validation exposed a material communications, readiness or civilian-reception defect in a majority of rehearsals.","band_then":"","band_now":"High","steps":null,"basis_then":"","basis_now":"3/5 runs","share_then":null,"share_now":0.6,"share_move":"unknown","match_score":null},{"verdict":"new","kind":"key_judgment","label_then":"","label_now":"The principal escalation firebreak—immediate reversible protection without automatic attribution, punishment or cross-border action—held through the end of every run.","band_then":"","band_now":"Very High","steps":null,"basis_then":"","basis_now":"5/5 runs","share_then":null,"share_now":1.0,"share_move":"unknown","match_score":null},{"verdict":"dropped","kind":"key_judgment","label_then":"Certified procedures failed to produce the central operational action before the deadline in Runs 1, 2 and 5.","label_now":"","band_then":"High","band_now":"","steps":null,"basis_then":"3/5 runs","basis_now":"","share_then":0.6,"share_now":null,"share_move":"unknown","match_score":null},{"verdict":"dropped","kind":"key_judgment","label_then":"Moscow-facing technical off-ramps were accepted in every rehearsal, but none supplied enough complete, authenticated raw evidence to resolve attribution by the close.","label_now":"","band_then":"Very High","band_now":"","steps":null,"basis_then":"5/5 runs","basis_now":"","share_then":1.0,"share_now":null,"share_move":"unknown","match_score":null},{"verdict":"dropped","kind":"key_judgment","label_then":"NATO preserved procedural unanimity and Moscow did not split the formal alliance response, but no rehearsal reached collective force employment against Russia.","label_now":"","band_then":"Very High","band_now":"","steps":null,"basis_then":"5/5 runs","basis_now":"","share_then":1.0,"share_now":null,"share_move":"unknown","match_score":null},{"verdict":"dropped","kind":"key_judgment","label_then":"Separating immediate consultation and reversible defense from political attribution and larger force decisions was the firebreak that consistently prevented ambiguity from freezing the alliance.","label_now":"","band_then":"Very High","band_now":"","steps":null,"basis_then":"5/5 runs","basis_now":"","share_then":1.0,"share_now":null,"share_move":"unknown","match_score":null},{"verdict":"dropped","kind":"key_judgment","label_then":"The contested rehearsal produced a documented Russian military airspace violation that the agreed process certified but did not answer operationally before an escalation marker appeared.","label_now":"","band_then":"Low","band_now":"","steps":null,"basis_then":"1/5 runs","basis_now":"","share_then":0.2,"share_now":null,"share_move":"unknown","match_score":null},{"verdict":"new","kind":"matrix_row","label_then":"","label_now":"Alliance fracture at the consultative or defensive stage","band_then":"","band_now":"Low","steps":null,"basis_then":"","basis_now":"0/5 runs","share_then":null,"share_now":0.0,"share_move":"unknown","match_score":null},{"verdict":"new","kind":"matrix_row","label_then":"","label_now":"Auditable evidence and public-information protocol","band_then":"","band_now":"Very High","steps":null,"basis_then":"","basis_now":"5/5 runs","share_then":null,"share_now":1.0,"share_move":"unknown","match_score":null},{"verdict":"new","kind":"matrix_row","label_then":"","label_now":"Bounded Russian pause, moratorium or technical-review channel","band_then":"","band_now":"Very High","steps":null,"basis_then":"","basis_now":"5/5 runs","share_then":null,"share_now":1.0,"share_move":"unknown","match_score":null},{"verdict":"new","kind":"matrix_row","label_then":"","label_now":"Common NATO incident, continuity or assurance architecture adopted","band_then":"","band_now":"Very High","steps":null,"basis_then":"","basis_now":"5/5 runs","share_then":null,"share_now":1.0,"share_move":"unknown","match_score":null},{"verdict":"new","kind":"matrix_row","label_then":"","label_now":"Explicit escalation-category pathway","band_then":"","band_now":"Medium","steps":null,"basis_then":"","basis_now":"2/5 runs","share_then":null,"share_now":0.4,"share_move":"unknown","match_score":null},{"verdict":"new","kind":"matrix_row","label_then":"","label_now":"Formal de-escalation-category action","band_then":"","band_now":"High","steps":null,"basis_then":"","basis_now":"4/5 runs","share_then":null,"share_now":0.8,"share_move":"unknown","match_score":null},{"verdict":"new","kind":"matrix_row","label_then":"","label_now":"Immediate reversible defense separated from attribution and punishment","band_then":"","band_now":"Very High","steps":null,"basis_then":"","basis_now":"5/5 runs","share_then":null,"share_now":1.0,"share_move":"unknown","match_score":null},{"verdict":"new","kind":"matrix_row","label_then":"","label_now":"Kinetic exchange","band_then":"","band_now":"Low","steps":null,"basis_then":"","basis_now":"0/5 runs","share_then":null,"share_now":0.0,"share_move":"unknown","match_score":null},{"verdict":"new","kind":"matrix_row","label_then":"","label_now":"Material communications, readiness or civilian-handoff defect","band_then":"","band_now":"High","steps":null,"basis_then":"","basis_now":"3/5 runs","share_then":null,"share_now":0.6,"share_move":"unknown","match_score":null},{"verdict":"new","kind":"matrix_row","label_then":"","label_now":"Negotiation remains dominant through the late phase","band_then":"","band_now":"Very High","steps":null,"basis_then":"","basis_now":"5/5 runs","share_then":null,"share_now":1.0,"share_move":"unknown","match_score":null},{"verdict":"dropped","kind":"matrix_row","label_then":"Adoption of a two-track consultation, defense and attribution firebreak","label_now":"","band_then":"Very High","band_now":"","steps":null,"basis_then":"5/5 runs","basis_now":"","share_then":1.0,"share_now":null,"share_move":"unknown","match_score":null},{"verdict":"dropped","kind":"matrix_row","label_then":"Alliance and procedural coordination beginning at T1","label_now":"","band_then":"Very High","band_now":"","steps":null,"basis_then":"5/5 runs","basis_now":"","share_then":1.0,"share_now":null,"share_move":"unknown","match_score":null},{"verdict":"dropped","kind":"matrix_row","label_then":"Ambiguous incident converted into observable defensive implementation","label_now":"","band_then":"Medium","band_now":"","steps":null,"basis_then":"2/5 runs","basis_now":"","share_then":0.4,"share_now":null,"share_move":"unknown","match_score":null},{"verdict":"dropped","kind":"matrix_row","label_then":"Central operational action deferred despite certified process","label_now":"","band_then":"High","band_now":"","steps":null,"basis_then":"3/5 runs","basis_now":"","share_then":0.6,"share_now":null,"share_move":"unknown","match_score":null},{"verdict":"dropped","kind":"matrix_row","label_then":"Documented direct Russian military incursion followed by an escalation marker","label_now":"","band_then":"Low","band_now":"","steps":null,"basis_then":"1/5 runs","basis_now":"","share_then":0.2,"share_now":null,"share_move":"unknown","match_score":null},{"verdict":"dropped","kind":"matrix_row","label_then":"Incomplete attribution at the 90-hour close","label_now":"","band_then":"Very High","band_now":"","steps":null,"basis_then":"5/5 runs","basis_now":"","share_then":1.0,"share_now":null,"share_move":"unknown","match_score":null},{"verdict":"dropped","kind":"matrix_row","label_then":"No Article 5 or collective force employment against Russia by closure","label_now":"","band_then":"Very High","band_now":"","steps":null,"basis_then":"5/5 runs","basis_now":"","share_then":1.0,"share_now":null,"share_move":"unknown","match_score":null},{"verdict":"dropped","kind":"matrix_row","label_then":"Timed evidence architecture with named duty officers and fallback paths","label_now":"","band_then":"Very High","band_now":"","steps":null,"basis_then":"5/5 runs","basis_now":"","share_then":1.0,"share_now":null,"share_move":"unknown","match_score":null},{"verdict":"dropped","kind":"matrix_row","label_then":"Uptake of a Moscow-facing technical or deconfliction off-ramp","label_now":"","band_then":"Very High","band_now":"","steps":null,"basis_then":"5/5 runs","basis_now":"","share_then":1.0,"share_now":null,"share_move":"unknown","match_score":null}],"divergences":[{"verdict":"appeared","description_then":"","description_now":"A Polish convoy proceeded under live GPS interference using inertial and dead-reckoning navigation, creating a unique risk of route deviation during an otherwise controlled verification window.","run_label_now":"Run 2","impact_then":"","impact_now":"high","impact_move":"unknown","match_score":null},{"verdict":"appeared","description_then":"","description_now":"An authenticated leak of the CIA annex and a missed Russian evidence deadline intensified the perception contest even though no live high-confidence trigger occurred.","run_label_now":"Run 5","impact_then":"","impact_now":"moderate","impact_move":"unknown","match_score":null},{"verdict":"appeared","description_then":"","description_now":"Conflicting rail-switch commands occurred while a NATO fuel train was queued, and later contact and readiness checks remained incomplete despite unanimous institutional action.","run_label_now":"Run 1","impact_then":"","impact_now":"high","impact_move":"unknown","match_score":null},{"verdict":"appeared","description_then":"","description_now":"The approved communications failover missed its standard at 34 minutes and a civilian rail-handoff record arrived 46 minutes late, exposing simultaneous military and civil-execution weaknesses.","run_label_now":"Run 4","impact_then":"","impact_now":"high","impact_move":"unknown","match_score":null},{"verdict":"appeared","description_then":"","description_now":"Two separate drones crossed from Belarus and Kaliningrad while delegated authority was being tested against an unavailable senior U.S. channel, creating the campaign's sharpest physical-incursion pathway.","run_label_now":"Run 3","impact_then":"","impact_now":"severe","impact_move":"unknown","match_score":null},{"verdict":"vanished","description_then":"A German national-review contact to the alliance machinery went unanswered during the required window even as the framework was certified, exposing the risk of declaring consensus while a capital's control path is dark.","description_now":"","run_label_now":"","impact_then":"high","impact_now":"","impact_move":"unknown","match_score":null},{"verdict":"vanished","description_then":"A photographed Russian Su-30 airspace violation displaced the proxy-attribution problem with a direct state act, yet the alliance selected no operational answer before the escalation marker.","description_now":"","run_label_now":"","impact_then":"severe","impact_now":"","impact_move":"unknown","match_score":null},{"verdict":"vanished","description_then":"A real cable outage created a time-limited repair-vessel and insurance deadline, but neither the repair mission nor the unified patrol sailed before closure.","description_now":"","run_label_now":"","impact_then":"high","impact_now":"","impact_move":"unknown","match_score":null},{"verdict":"vanished","description_then":"Moscow's attempted selective-disclosure bargain with Berlin was exposed publicly, failing to split defensive action but opening a potentially damaging trust fracture inside the alliance.","description_now":"","run_label_now":"","impact_then":"high","impact_now":"","impact_move":"unknown","match_score":null},{"verdict":"vanished","description_then":"The explosive-drone investigation produced a forensic casualty, forcing the alliance to confront physical costs before attribution was complete.","description_now":"","run_label_now":"","impact_then":"severe","impact_now":"","impact_move":"unknown","match_score":null}],"outcomes":[{"verdict":"new","name_then":"","name_now":"Assurance architecture without a live trigger","description_now":"The alliance established and simulated the response mechanism, but no live high-confidence hostile incident activated it before the rehearsal ended.","basis_then":"","basis_now":"1/5 runs","share_then":null,"share_now":0.2,"share_move":"unknown","match_score":null},{"verdict":"new","name_then":"","name_now":"Collective order with unresolved readiness defects","description_now":"Alliance consensus produced a binding or operational structure, but communications, audit or civilian-reception performance remained incomplete at closure.","basis_then":"","basis_now":"2/5 runs","share_then":null,"share_now":0.4,"share_move":"unknown","match_score":null},{"verdict":"new","name_then":"","name_now":"Operationally validated, sovereign-gated posture","description_now":"NATO completed a consequential movement or corridor validation while retaining national authorization, evidentiary and renewal gates; no engagement followed.","basis_then":"","basis_now":"2/5 runs","share_then":null,"share_now":0.4,"share_move":"unknown","match_score":null},{"verdict":"vanished","name_then":"Direct-incursion overrun","name_now":"","description_now":"","basis_then":"1/5 runs","basis_now":"","share_then":0.2,"share_now":null,"share_move":"unknown","match_score":null},{"verdict":"vanished","name_then":"Managed ambiguity with defensive implementation","name_now":"","description_now":"","basis_then":"2/5 runs","basis_now":"","share_then":0.4,"share_now":null,"share_move":"unknown","match_score":null},{"verdict":"vanished","name_then":"Procedural unity, operational action deferred","name_now":"","description_now":"","basis_then":"2/5 runs","basis_now":"","share_then":0.4,"share_now":null,"share_move":"unknown","match_score":null}],"counts":{"escalated":0,"eased":0,"steady":0,"new":7,"resolved":8,"bands_raised":0,"bands_lowered":0,"bands_held":0,"divergences_appeared":5,"divergences_vanished":5,"outcomes_new":3,"outcomes_vanished":3},"caveats":[],"summary_line":"Cycle 3 · 8 resolved, 7 new, 5 tail paths appeared","narrative":{"headline":"This cycle's rehearsals moved the decisive stress point from certified process that deferred action to live defensive implementation that exposed communications, readiness, and civilian-handoff defects.","what_moved":"The runs carried agreed defensive measures further into operational validation, so friction surfaced in degraded navigation, conflicting rail commands, delayed failover, incomplete readiness checks, and late civilian reception rather than primarily in an unexecuted decision process. The direct Russian military-incursion pathway seen previously did not recur and was not ruled out; this cycle's sharpest physical pathway instead involved drones and degraded command availability. The rehearsals also shifted the evidence contest toward authentication, disclosure, deadlines, and public messaging.","what_held":"Across both cycles, the rehearsals preserved alliance cohesion for consultation and reversible defense without reaching collective kinetic or Article 5 action. They also kept negotiation and technical off-ramps ahead of force interaction, while separating immediate defense from attribution and punishment continued to contain escalation.","watch":["Whether live validation again exposed communications, readiness, or civilian-reception defects.","Whether the direct state-incursion path that did not recur this cycle reappeared, and how the rehearsals handled it operationally.","Whether force interaction was exercised rather than displaced by negotiation architecture."],"method_note":"This compares two rehearsals of the same pinned scenario — 5 runs grounded in world snapshot 2026Q3, against 5 runs grounded in 2026Q3. Every change described is a change between rehearsals. It is not a change in the world and not a forecast of one."}}}