Space governance you can step inside.
Read the launch brief →howdy [at] diplospace · orgSupport the work →
An orbital crisis is hard to decide on because it's hard to see. So we turn one into a navigable 3D scenario your team can walk through and rehearse as a decision before it's real, whether it's an anti-satellite (ASAT) strike, a debris cascade, or a GPS-denial event. Fully remotable; a browser is all you need, a headset is a bonus.
Each is a navigable rehearsal, not a slide deck. It’s anchored to the verified record and designed to surface the decision, not just the failure. Some are playable today; others are in design, published when they’re ready, not before.
The satellite signal a city runs on goes unreliable in the middle of a crisis: who owns the call, and when. A free, self-guided rehearsal you can step through in about fifteen minutes. Further down the page, the documented March 2026 Hormuz interference is rebuilt in 3D where it happened.
Play it, free →A single collision multiplies into a debris field that can close an orbit. Step inside the surviving field of the 2009 Iridium–Cosmos collision: its still-tracked fragments, on their current orbits in today's public catalogue.
Step into the field →An anti-satellite event forces an attribution-and-response decision under time pressure, across diplomatic and military channels at once. In design against the verified record's four kinetic engagements: Fengyun-1C (China, 2007), USA-193 (United States, 2008), Mission Shakti (India, 2019), and Cosmos 1408 (Russia, 2021).
Two working satellites, two operators, one converging path, and no rule that says who moves. A self-guided rehearsal of the documented 2019 Aeolus–Starlink near-miss from the operator's seat: four decisions, every fact sourced, about ten minutes. Paired with Field Note 04; the facilitated version runs it as a two-seat negotiation.
Play it, free →Satellite timing degrades and the grid, financial markets, and telecoms drift at once: the same disruption read four different ways, with no one owning the cross-sector call. A cascade rehearsal paired with Field Note 02.
GPS goes unreliable across a metro area on a normal Tuesday. Participants play the emergency-management coordinator, the grid operations lead, the aviation authority duty officer, and the city communications director. They discover, inject by inject, who owns the call. Step through the five injects below (the scripted developments a facilitator feeds the room) the way a real session runs them: facilitated, no specialist knowledge assumed.
A Tuesday, 09:40. The airport reports degraded GPS approaches. Separately, a grid operator's monitoring units start flagging timing alarms. Nobody has connected the two yet.
Do you issue an advisory now, on partial information? Or wait for confirmation and lose the morning?
What this inject surfaces: This inject is built to surface that the two reports travel different channels, and would not meet for hours. The first fix is usually a phone tree, not a technology.
A debris cascade or a near-miss at 789 km is hard to argue about until you can see the neighborhood. So you can, in a plain browser. Load the live globe and you’re looking at the debris that 2009 Iridium–Cosmos collision left behind: its surviving fragments, on their current orbits in today’s public catalogue, in 3D. Watch the two orbits close, the moment of contact over Taymyr, and the fragments spread from a single point into the band they still occupy. We build the scenes ourselves from the public catalogue, so the engine was never the hard part. The hard part, and the point, is the verified record underneath and the decision on top.
An active American commercial satellite and a defunct Russian military one met at 11.7 km/s. No rule obliged anyone to move the dead satellite: post-mission disposal guidance is voluntary and postdates the launch. No rule obliged anyone to pass a warning. And the Liability Convention makes damage in spacefault-based (Art. III) without defining fault for orbital traffic, so no claim is on the public record. Two states, one wreck, and nothing to breach.
So make the call yourself: rehearse a conjunction nobody owns →Illustrative reconstruction from public catalogue data (CelesTrak / Space-Track) and published analysis. In the 3D view every orbit and every fragment position comes from a current element set. Two things are set back to 2009, and both move the orbitrather than the object. Seventeen years of nodal precession have carried both ascending nodes away from where they were, so each track is rotated about the Earth’s polar axis (the axis that precession turns them about, which leaves inclination, altitude and shape alone) until its own 72.5°N crossing sits on the documented contact meridian. Each object’s phase is then set so it reaches that crossing at the moment of contact, and it rides its own real path at a constant rate throughout. Which crossing is not a free choice: Iridium 33 runs northbound and Cosmos 2251 south-eastbound, the geometry Kelso’s AMOS 2009 analysis describes and the one NASA’s Orbital Debris Program Office corroborates. So placed, the two pass about 8 km apart, their planes crossing at 103° — which independently reproduces the documented closing speed, since at a given altitude that speed and the crossing angle determine each other. Contact falls at the documented latitude and longitude, slightly lower than in 2009 because both orbits have decayed since. The debris spread compresses seventeen years into the replay: fragments start together and are pulled apart along their parent’s orbit before settling on their real tracked positions, which is the actual mechanism but not an operational simulation. The consequence is not illustrative: several hundred fragments of this 2009 collision are still tracked on orbit today.
Several hundred fragments of this collision are still tracked on orbit. What you’re looking at is the current public catalogue, not the 2009 cloud. The event is in the record, with sources, and the governance question it leaves (who must maneuver, on whose data, under what rule) still has no binding answer under the Outer Space Treaty’s Article VI/IX “due regard” duty.
Charts tell you interference happened; this shows you what it looks like. Below: the March 2026 Gulf jamming surge from our record, reconstructed over the real strait, with actual terrain, actual buildings, and the image a live feed doesn’t carry: each ship’s true course versus where its GPS claims it is. We only rebuild documented events from the verified record, and every synthetic element says so on its face. Gifted open-source storytellers already replay crises on globes. That’s the point: the view is the easy part. What isn’t is the pairing underneath: a verified public record, the deception made legible, and a decision to rehearse on top.
Documented event: 1,650+ ships affected on March 7, 2026 across ~30 interference clusters, Kuwait to Muscat (Windward; UKMTO logged 13 incidents in nine days). The record row, with sources. The terrain is real: public elevation data draped with Sentinel-2 cloudless imagery (EOX, CC-BY-4.0), baked offline. Every ship track is synthesized to show the documented failure signatures, not actual vessel data. The amber haze is the corroboration layer: airliners broadcast their GPS confidence, so the airline fleet doubles as an interference-sensor network, extent illustrative, mechanism per public ADS-B-derived interference maps. And the distinction the news coverage blurs, now visible side by side in the replay: jamming drowns the signal so a receiver goes quiet; a transponder switched off goes dark: watch the one vessel whose marker simply freezes at onset, absence of data; but a spoofed receiver confidently reports a position that is wrong. The spoofed ships are the ones that break a navigator’s picture without ever looking broken.
Facilitated pilots are offered on a sponsored basis to institutions; the self-guided scenario and the open toolkit are free either way, so the method outlives any one budget.
A navigable orbital-crisis scenario run for your team (a desk, a delegation, a policy cohort) with full facilitation. Subjects: GPS denial, a conjunction, a debris cascade, ASAT escalation, timing. Fully remotable, so you don't have to fly everyone to one room to rehearse the decision.
You keep the scenario, the inject schedule, and an after-action / improvement record.Step through a scenario at your own pace in a plain browser: the fastest way to feel how a rehearsal runs before you bring one to your team.
You keep your decisions and an after-action summary.The open method for building these tabletops: facilitation guide, inject templates, after-action structure. A public good, never sold as software, so any institution can run one without us.
You keep the method, the templates, and the facilitation guide.Tell us the audience (a desk, a delegation, a cohort) and the decision you want them to be ready for. We’ll propose a scenario, neutral and sourced, usually within two business days.