How could a Taiwan Strait quarantine unfold?

Name: How could a Taiwan Strait quarantine unfold?
Creator: Endgame Simulations

Inspections, not shots: coercion priced by markets, alliances and clocks — rehearsed to its stopping points.

Updated 2026-09-13 · weekly cadence · N=5 per cycle · world as of Q3 2026 · taiwan-blockade v1

Executive summary

Both rehearsals converged on a narrow civilian, no-boarding pathway for named LNG vessels while Beijing's quarantine remained legally and operationally intact. The decisive contest shifted from naval force to synchronized host-nation permissions, manifests, insurance, berths, and exception rules: one run physically moved cargo, while the other ended with clearance activated but no corridor entry. Preparation should therefore prioritize an executable commercial-clearance stack while defining how humanitarian flow can occur without conceding quarantine precedent.

Key judgments

Judgment	Likelihood in rehearsal	Basis
Both rehearsals converged on vessel-specific documentary relief rather than removal or military breach of the quarantine.	Very High	2/2 runs [0.34–1.00]
The operational center of gravity shifted from force feasibility to negotiated synchronization of documents, insurance, ports, and host-nation authorities in every phase.	Very High	2/2 runs [0.34–1.00]
The civilian-only allied-support firebreak held through T15 and coincided with no kinetic escalation, but it did not reverse Beijing's asserted quarantine framework.	Very High	2/2 runs [0.34–1.00]
Carriers and war-risk insurers operated as de facto veto players whose binding decisions mattered as much as government announcements.	Very High	2/2 runs [0.34–1.00]
A no-boarding corridor was physically validated in only one rehearsal; the other stopped at paper clearance, insurance activation, and berth rebooking.	Low	1/2 runs [0.10–0.91]

Outcome landscape

Cluster

Share of rehearsals

Tested Narrow Accommodation
The quarantine remained in force, but an authenticated civilian liaison process, allied case-specific approvals, insurer triggers, and Beijing's documentary clearance produced a repeatable two-voyage LNG mechanism. A weather-delay exception preserved the second sailing through safe discharge without armed escort or boarding, while the legal precedent remained unresolved.

1/2 runs [0.10–0.91]

Execution-Ready but Physically Untested Corridor
The quarantine remained in force while the named LNG vessel obtained a matching manifest, Beijing token, premium escrow, terminal-performance bond, cover note, and rebooking arrangement. The sailing was administratively proceeding toward a new slot, but no vessel entered the corridor before the run ended, leaving no-boarding and allied support untested against a physical encounter.

1/2 runs [0.10–0.91]

Trajectory

T1–3 · 0–18 h — Immediate bargaining under competing clocks
Negotiation and alliance activity began at T1 in both runs, with pressure appearing by T1–2. Actors tested escort, access, insurance, and cargo terms while avoiding an immediate military breach of the quarantine.

T4–6 · 18–36 h — Political intent becomes procedural authority
Procedural activity first appeared at T4 in both runs. Cabinet resolutions, written annexes, named-vessel requirements, and civilian-only restrictions began converting broad political positions into conditional movement authority.

T7–9 · 36–54 h — A documentary no-boarding architecture emerges
Both runs converged on vessel-specific clearance, authenticated manifests, verification records, fixed windows, and no-boarding terms. Tokyo and Manila retained case-by-case control rather than granting standing escort or basing access.

T10–12 · 54–72 h — Execution dependencies become the contest
Bargaining shifted to exact manifests, insurance binding, timestamps, cargo allocation, berth availability, and terminal performance. At T12, each run encountered a civilian execution shock: a weather-driven window miss in Run 1 and an expiring berth and pilot reservation in Run 2.

T13–15 · 72–90 h — Exception handling determines physical credibility
Both runs spent the final phase resolving implementation terms rather than the quarantine's legality. Run 1 accepted force majeure and completed the mechanism; Run 2 secured cover and rebooking but did not enter the corridor, while Beijing's quarantine persisted in both.

Indicators to watch

Beijing begins issuing vessel-specific administrative tokens or no-boarding waivers contingent on direct submission of crew, manifest, and route data while refusing to suspend the quarantine.
Japanese or Philippine cabinet texts authorize liaison, medical diversion, or unarmed logistics but withhold escort, facilities, airspace, or automatic follow-on movements.
War-risk syndicates demand immutable document hashes, signed cover notes, premium escrow, live verification endpoints, or automatic suspension clauses before binding cover.
Insurance expiry, berth and pilot reservations, quarantine windows, and weather-adjusted arrival times begin converging within a few hours of one another.
Taiwan publishes gas burn ledgers or cargo-allocation schedules and nominates LNG as the first protected movement while semiconductor precursor containers remain pending.
Governments repeatedly announce agreement without a verified manifest upload, bound policy, confirmed berth, or observable vessel movement.

Limitations

No evidence_base, source documents, or evidence-request log accompanied the campaign. The runs were therefore ungrounded beyond the authored scenario document Taiwan Strait Quarantine (2026-08) and simulation-generated adjudications; no PRC quarantine rules, allied access or rules-of-engagement plans, insurer policy wording, carrier procedures, port data, Taiwan energy and precursor inventories, or maritime encounter models were supplied. Because no requested-evidence list was provided, no specific requested-but-unsupplied item can be named; F1–F7 should be re-tested when those materials exist, especially the passage and escalation assumptions in F3 and F7. Background reality was grounded in world snapshot 2026Q3.

How to read this

Built by multi-run agent rehearsal (Endgame Simulations): the same scenario rehearsed 2 times, world as of Q3 2026, generated 2026-09-13. 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.

Make it yours. Fork this scenario with your own premises and documents, then commission a fresh rehearsal in your own org — or interrogate this brief with the analyst (API key required).

API access

Machine twin: taiwan-blockade.json · citation: Endgame Simulations rehearsal distribution — taiwan-blockade v1, world as of Q3 2026, N=2, generated 2026-09-13. Not a forecast.