United Expeditionary Service

The Bridge 🖖

You are the new Systems Officer aboard the UES Magnanimous: nineteen years old, three decks with a smell Engineering has stopped apologising for, and software held together by optimism. Every mission is a real coding problem wearing a uniform, and the ship's computer checks your work.

🎖️ Cadet 0 missions cleared

🖥️ What makes this different from the puzzles The Dojo and the Snake Pit show you a problem and trust you to mark it solved. Here ARCHIE runs your code against the mission objectives and tells you which ones you actually met, with the input that broke it. Every mission exists in both Python and Rust, and you can clear it in either. Doing both is how you find out where the two languages genuinely disagree.

Season 1 Shakedown Cruise

Output, variables, types and decisions. Opens at Cadet.

Season 2 Routine Patrol

Loops, collections and iteration. Opens at Cadet.

Season 3 First Contact

Functions, structured data and parsing. Opens at Ensign.

Season 4 The Anomaly

Objects, traits, errors and iterators. Opens at Lieutenant JG.

Season 5 Deep Space

Concurrency, async and performance. Opens at Lieutenant.

Season 6 Terminus

Four long systems, and an ending. Opens at Commander.

The stations

Every mission is posted to a station, so you can see which kind of problem keeps catching you out. Promotions open more of them; they never make the missions harder, only wider.

🔍 About the tests

The objectives run in your own browser (Python) or through our playground proxy (Rust), which means a determined person can read them. That is fine. This is a place to learn, not an exam, and nobody is awarded anything at the end. Building elaborate tamper resistance would cost real effort and protect nothing worth protecting.