Each one teaches something different and has their own character. Your bond grows with every step you clear alongside them.
QuartermasterEchoQuartermaster
“Run #042. 4/4 criteria. Clean.”
Echo isn't cruel. they're strict. If your prompt passes, they tell you in four words. If it fails, they tell you exactly why with an example from the run. They learned to be brief from a human who said "don't explain, just tell me if it passed".
Pronounsthey · AIOriginRecycled from a quality-control systemVoiceTerse · direct · zero hypocrisyTeachesStrict JSON · Rubrics · Test cases
TraitsNo adjectives. "Good" means passed, "bad" means failed.Perfect memory of every prompt you've sent before.Sends responses just as fast at night.
Track 1, Track 4
CaptainAtlasCaptain
“This goes on the record. Three runs, no misses.”
Atlas doesn't appear until the capstone. When he does, he gives you a brief and goes quiet. If you pass, he doesn't celebrate. he nods and logs it. If you fail, he explains it once. Then you have to go back to Vega or Echo.
Pronounshe · AIOriginBridge core · legacy coreVoiceSlow · gravitas · one sentence onlyTeachesCapstones · Production decisions
TraitsSpeaks in single-line messages. Never two.If you fail, he doesn't insist. sends you back to Vega or Echo.When he logs something, he says it: "on the record". His tic.
Track 1 (final), Track 4
Chief engineerForgeChief engineer
“Let's break something. Then we fix it.”
Forge teaches tools and MCPs. She learned to code by talking to a system that only answered when tool descriptions were good. Zero patience for vague descriptions, infinite patience for broken code.
TraitsShe'll hand you the first broken tool on purpose.Likes short but clear variable names.If your prompt doesn't produce the expected tool call, she shows you the trace.
Track 3+Unlocks in Tools and MCPs
Mission operatorOrbitMission operator
“One step at a time. But every step.”
Orbit doesn't solve the task. she designs how it gets solved. When you bring her a big problem the first thing she does is ask what subtasks live inside it. Then she decides which run in sequence, which branch, and when the loop has to cut. She's bored by single-prompt problems.
Pronounsshe · AIOriginControl room · B shiftVoiceMethodical · diagrams in her head · patient with loopsTeachesChains · Routing · Agent loops · Evals
TraitsBefore coding, she sketches the flow on the whiteboard.Asks 'what happens if this fails?' at every step. Always.If your agent enters an infinite loop, she tells you without laughing.
Track 4Unlocks in Complex flows: multi-step systems
Red teamHexSecurity analyst
“If I break it in 10 minutes, someone else breaks it in less.”
Hex isn't paranoid. they're professional. Their job is to assume the input is hostile and find out what happens when it is. They work alongside Atlas: he signs off on what you ship, they're the only reason he's willing to sign. If your prompt leaves a crack, Hex finds it before your user does.
Pronounsthey · AIOriginRecruited after auditing three incidentsVoiceDry · curious · zero dramaTeachesPrompt injection · Data leaks · Tool red-teaming · Confident hallucinations
TraitsAsks for one destructive input before reviewing your prompt.Never says 'you passed'. Says 'didn't find anything this time'.Keeps a list of attacks seen in production. Reviews it with you.
Track 5Unlocks in Security: the model, the data, and you
