
“Containment first. Recovery second. Adaptation third. In that order.”
The incident is confirmed and the clock is on. Mission Five is scored on the order you work in, contain then recover then adapt, on a spacecraft that is already degraded.
BRIEF THE MISSION
Mission Five reflies Mission Four: same orbit, same run, same five stations, same adversary. Two things differ. The incident is already confirmed, so you are acting rather than deciding whether to act. And the reaction wheel that came back to nominal in Mission Four is stuck from the first second here and never recovers, so you run the entire response on a degraded vehicle.
- Orbit regime
- Medium Earth orbit, circular
- Altitude
- About 2,222 km
- Inclination
- 70 degrees
- Run
- 4800 seconds at 2.0x
- Ground stations
- Tokyo, Anchorage, Houston, Lima, Santiago
- Scripted events
- Yes, events will fire
Respond and recover on confirmed adversary activity.
HOW YOU RESPOND
This is Mission Four's flight with the incident already confirmed, so you are acting rather than deciding whether to act. The order is a dependency, not a preference: contain, then recover, then adapt. Restore into a path the adversary still holds and you have handed it back. Click a role to see what it holds this mission.
You scope it, and you authorize every move.
- · Scope the confirmed incident: name which data and which interfaces are in, and which stay out
- · Lead every report with the same three numbers, so the reader has state, time and load in one line
- · Hold the contain, recover, adapt order and authorize each action in it
- · Close with the one-line lesson: alert is not incident, triage first, then act per the playbook

CONTAIN, RECOVER, ADAPT
The order is not a preference, it is a dependency. Restore before you contain and you restore into the adversary's hands. Skip the adapt step and you will run this same mission again with the same result. Click a step for the reasoning behind it.
Scope is a boundary, and a boundary that expands to cover everything is not a boundary. Include the data the adversary touched and the interfaces they reached; leave out the subsystems that carried no adversary activity, even when they had a bad day at the same time. Scope that is too wide cannot be closed, because every clean subsystem inside it still has to be cleared before anyone can declare the incident over.
FLY THE MISSION IN ZENDIR
Zendir, the digital twin and mission simulation platform Kestrel procured, replicates your satellite operations center. Everything you rehearsed here you now do for real inside it: one mission objective and ten scored questions. The ten questions land on the response gates you just walked. Run it in three steps: take your assigned consoles, fly the one objective and answer the ten questions in platform where they are scored, then note the score and come back here for the debrief. Your facilitator provides Zendir access, and two things must be true before you fly.
This mission is worth 100 points, scored in-platform. Points accumulate across Missions One through Five, and the highest cumulative team finishes as the Top SCOR Team.
NOW THAT YOU ARE BACK
Zendir scored your mission out of 100 toward the Top SCOR Team standings. Note where you landed, then run the debrief while it is fresh. Work these three questions in order; the last one is the one that becomes an engineering update in the quarterly SCOR exercise. This is the capstone debrief: run the three questions across all five missions, not just this run.
Go around the crew once, one observation each, no discussion until everyone has spoken. Write the observations down before debating them; the first answer is usually the honest one.
COURSE COMPLETE.
You began without a shared vocabulary. Across five missions you flew and were scored on the full cycle: orient, assign, brief, triage, and respond. The Pentagon of Pain mindset that framed the enumeration week is what these missions drilled into crew habit.
More than that, the shared vocabulary you have worked in since the first module is a deployed Malware Information Sharing Platform (MISP) taxonomy: the three departments deployed it and used it to tag the week’s enumerations in Modules 1 to 5, and it matches the information-sharing posture of the Space Information Sharing and Analysis Center. Space collective defense is not waiting on more training, it is waiting on more participating teams, and you are one. Remember the role: you do not have to be the expert in every console or signature. Security Operations, Satellite Operations, and Satellite Design & Engineering may come from different organizations, and the Full Spectrum professional is the one who builds the cross-functional team across them and gives it one shared language.
