A pair of cadets built a tool that watches who puts what into space. It draws every launch as a line off a spinning Earth: a bending arc for an ordinary launch — nothing to see, it went where it said it would — and a straight spear shooting off the edge for the ones that don’t say where they’re going. One bit. Arc or spear. Boring or look here.
One weekend the board lit up, and a spear shot off a launch. “That’s new,” one cadet said. The next day, another spear. It felt like a tell — like the tool had caught someone hiding something. But it just didn’t feel right, and they couldn’t say why. So before they presented it as their senior project, they brought it to Commander Thorpe and asked him to look at the code.
He clicked around for a minute. Then he laughed. The spear wasn’t firing on secrecy. It was firing on altitude. The board below is real — ten actual launches. Pick a wiring, click a launch, and read the panel. Then ask the only question that matters: does the picture match what the panel actually says?
🐧 NULL clicked the one launch with no destination, watched the bright spears fire on everything but it, and marked the gap: the loudest alarm was pointed at the radio, and the quiet line was the one keeping a secret.
The cadets’ spear lined up with a genuinely secret launch one time — a Chinese mission that happened to be both high-orbit and classified. That single overlap made the tool look like a secrecy detector. It wasn’t. It was an altitude detector that got lucky on one case and stayed silent on the launch that was actually hiding its destination.
This is the trap the whole node is built to teach: a tool that confirms what you expected, on the one case you checked, earns trust it didn’t deserve. The fix wasn’t to reorder some code — it was to decide what question the alarm is even asking before wiring it. “How high?” is not “where is it going?” is not “what won’t they tell us?” Three different alarms. The cadets shipped the first and read it as the third.
And the deepest cut: the spear’s direction was never real. The code leans every line the same way to have somewhere to draw. Only one bit — spear or arc — ever carried information. They’d been reading an arrow that didn’t point at anything.
● Real. The ten launches on the board are actual missions from June 2026, with their real vehicles, sites, dates and orbit labels as public launch trackers carried them — including TJSW-26A from Wenchang to a geostationary transfer orbit (a disclosed path, a classified payload), and NROL-179 from Vandenberg with its orbit listed only as Unknown. VICTUS HAZE was a real responsive-space mission flown on very short notice to practice rendezvous-and-proximity operations; Project Starfall was a real reentry-capsule demonstration. Sirius SXM-11 is a satellite-radio bird bound for the same transfer orbit class as TJSW — which is exactly why an altitude-wired alarm can’t tell them apart.
● Real. The tool behavior shown here mirrors actual code: a spear keyed to orbit-name keywords (so “geostationary transfer” reads as high and fires), an “unknown” flag that checked for a dash and missed the literal word Unknown, and an ascent line whose heading is a fixed cosmetic lean rather than a real trajectory.
◐ Mine. Commander Apollo Thorpe and the two cadets are authored OPA characters; the weekend, the dialogue, and the “senior project” framing are a story wrapped around a real find. The globe, the arcs and the spears here are an illustrative teaching render — not SGP4, not a propagator. Pad positions are schematic.
◐ Mine — interpretation, not fact. Any reading of these launches as one connected contest is inference. The agencies involved do not narrate motive, and in particular the U.S. responsive-space program does not name another country. The lab teaches a way of reading, not a verdict.
Pairs with the live Sky Sentinel (what’s up there now) and SpacePulse (who’s launching). Built to teach, not to scare.