CubeSTEM Digital Twin
A grade-aware map of the eight-track CubeSat mission learning journey (orientation through AI / ML autonomy)— pathways, tracks, outcomes, and honest software readiness.
This page is a teacher planning map and student pathway guide. It does not claim official curriculum alignment, accreditation, or mandated standards mapping. Content is software-first with teaching-grade models where activities are implemented.
Suggested pathways
These are level-aware suggestions, not requirements. Each card lists focus skills and a recommended track entry; open the learn hub to filter by learning level.
Younger learners and first exposure
Start with mission story, satellite parts, and simple observation. Suggested pathway only—not a mandated sequence.
4 activities match this pathway filter in the mission model.
Focus skills
Uses orientation activities with all-level framing; teachers should shorten or scaffold as needed.
Grades roughly aligned with middle STEM
Suggested start: orientation plus launch-to-orbit and contact-window thinking. Software-ready Track 1 labs are available today.
6 activities match this pathway filter in the mission model.
Focus skills
Track 1 interactive pages are teaching-grade models, not operational orbit propagators.
Secondary STEM and mission electives
Extend through mission design, budgets, communication concepts, and attitude topics with explicit trade-offs.
41 activities match this pathway filter in the mission model.
Focus skills
Tracks 0–7 ship as polished mini-courses with interactive activity pages. Track 7 AI/ML Autonomy uses deterministic teaching classifiers only — not certified AI, not flight software, not real satellite commands, not real onboard autonomy.
Introductory CubeSat / systems courses
Suggested emphasis on requirements, mission design, coverage, budgets, ADCS reasoning, and anomaly-style thinking.
35 activities match this pathway filter in the mission model.
Focus skills
Full depth uses the whole track list; additional path entries may remain concept-only or future-module where `missionLearningPath` marks them—check readiness labels on this map.
Educators sequencing lessons
Use outcomes, time estimates, readiness, and maturity labels to pick lessons and classroom flow.
41 activities match this pathway filter in the mission model.
Focus skills
Lesson packs and timing presets are browser-local planning aids only—no class roster, LMS sync, cloud sync, automated grading, or visibility into student answers unless learners share evidence manually.
Pilots, workshops, commercial reviewers
Focus on known-good browser routes, product story, and honest capability boundaries.
37 activities match this pathway filter in the mission model.
Focus skills
Pair with `/twin`, `/twin/demo`, and `/twin/hardware` for the full pilot picture.
Mission journey
Order and titles come from the live mission learning model. Counts show how many activities sit in each simulator-readiness and maturity bucket per track.
Understand what a CubeSat mission is and why digital simulation helps before hardware.
Simulator readiness
Activity maturity
Understand how satellites reach orbit and how altitude, speed, and contact windows work.
Simulator readiness
Activity maturity
Choose a mission objective, connect payload to subsystem needs, and define success criteria.
Simulator readiness
Activity maturity
Learn how power, energy, thermal limits, and finite mass/volume constrain what a CubeSat mission can do — with honest teaching-grade models.
Simulator readiness
Activity maturity
Understand line of sight, contact time, simplified link margin trade-offs, and command/telemetry flow — with honest teaching-grade models (not RF certification, not real satellite command).
Simulator readiness
Activity maturity
Understand why pointing matters, run ADCS experiments, and interpret control evidence.
Simulator readiness
Activity maturity
Read dashboards, replay runs, interpret subsystem health, and complete a mission debrief.
Simulator readiness
Activity maturity
Explore data-driven fault detection and autonomous decision concepts for advanced learners.
Simulator readiness
Activity maturity
Each track below links to its dedicated overview route when registered in the learning route model; otherwise the learn hub is used so reviewers never hit a dead 404.
Simulator readiness describes software attachment today. Activity maturity describes pedagogical / pilot status. They are complementary, not identical.
Learning outcome map
One card per activity for readability on phones. Desktop users can still scan quickly by track group. STEM links and evidence counts come from the mission model.
What is a CubeSat Mission?
Open →Student can explain what a CubeSat is, why missions need planning, and what a mission objective means in plain language.
Subsystem Detective
Open →Student can identify major CubeSat subsystems, explain each subsystem’s role, and justify which subsystem is involved when a mission clue or symptom appears.
Mission / Subsystem Trade-off
Open →Student can explain how a mission objective changes subsystem priorities and justify at least one engineering trade-off using evidence.
Digital Twin Before Hardware
Open →Student can explain what a digital twin is, give one learning benefit, and name one honest limit of today’s CubeSTEM twin.
From Launch to Orbit
Open →Student explains orbit as continuous free fall: gravity plus sideways velocity, not “no gravity.”
Orbit Speed and Altitude
Open →Student can estimate how period and speed change when altitude changes and compare two LEO cases.
Low Earth Orbit vs Higher Orbit
Open →Student can describe at least two trade-offs between LEO and GEO (or MEO) for a CubeSat-class mission.
Ground Track and Coverage
Open →Student can explain ground track, inclination, and why revisits happen faster in LEO than in distant orbits.
Contact Window Basics
Open →Student can explain line-of-sight, why passes are brief, and how that limits downlink time.
Choose a Mission Objective
Open →Student can state a clear mission objective and explain how it drives system requirements.
Payload Drives the Mission
Open →Student can explain how a chosen payload determines power, pointing, data, and thermal requirements.
Payload Data Generation
Open →Student can estimate data volume from a payload and relate it to downlink constraints.
Mission Success Criteria
Open →Student can write a set of mission success criteria and explain how they connect to telemetry evidence.
Power Budget Basics
Open →Student can compare average and peak bus power, explain duty-cycle effects, and read a simple margin result (safe / warning / overloaded).
Day / Night Energy Balance
Open →Student can relate sunlight vs eclipse time, average load, and stored energy to a remaining-reserve warning (teaching estimate).
Thermal Hot / Cold Case
Open →Student can explain when a simplified model flags hot or cold risk and what an engineer would check first (teaching-grade).
Mass / Volume / Resource Trade-off
Open →Student can allocate limited resources, interpret warnings, and justify a chosen strategy with evidence (teaching exercise).
Solar Power Generation
Page upcomingStudent can explain what determines how much solar power a CubeSat receives and why eclipse is a problem.
Data Budget and Downlink Limit
Page upcomingStudent can explain what data utilization means and what happens when data generation exceeds downlink capacity.
Risk Flags and Engineering Decisions
Page upcomingStudent can read mission risk flags, explain their severity, and propose at least one mitigation per flag.
Line-of-Sight Communication
Open →Student can explain why ground-station contact depends on satellite visibility above the horizon and on a minimum elevation angle.
Data Rate × Contact Time
Open →Student can compute a teaching-grade data budget (data rate × contact time × passes) and identify when payload data exceeds available downlink.
Link Margin Trade-off
Open →Student can read a teaching-grade margin badge (safe / weak / failed) and explain one trade-off and one improvement (teaching-grade only).
Command / Telemetry Flow
Open →Student can explain what gets sent first when contact time is short and what happens to lost packets in a teaching priority queue (no real radio).
Why Pointing Matters
Open →Student can explain why attitude control is needed and what pointing error means.
Attitude Hold Basics
Open →Student can describe the target angle, actual angle, and error trend from a real simulator run.
Step Response to +10 Degrees
Open →Student can measure overshoot and settling time from a step response chart and relate them to controller tuning.
Contact Window Pointing
Open →Student can explain the pointing requirement for a contact window and observe it in the simulator.
Gentle vs Aggressive Control
Open →Student can compare settling time, overshoot, and wheel effort for gentle and aggressive control settings.
Power-Aware Attitude Control
Open →Student can explain how a power-limited scenario changes controller behaviour and mission safety.
Daylight vs Eclipse Response
Open →Student can explain why eclipse changes power availability for control and what the system must do differently.
Telemetry Dashboard Basics
Open →Student can identify at least four telemetry channels and explain what each one measures.
Subsystem Interpretation Walkthrough
Open →Student can interpret each telemetry subsystem channel and explain its mission-level significance.
Replay and Mission Debrief
Open →Student can replay a run, identify key events in the telemetry, and write a short mission debrief statement.
Telemetry Trust and Stale Data
Open →Student can identify stale telemetry, explain its risk, and describe a mitigation strategy.
Mission-Based STEM Capstone
Open →Student can complete a full mission journey and produce an evidence-based report connecting all tracks.
What Does Autonomy Mean?
Open →Student can describe three levels of spacecraft autonomy, explain what each level is allowed to do, and state why human-in-the-loop review matters even in the highest autonomy mode.
Features, Labels and Training Data
Open →Student can define feature and label, select useful features from telemetry, assign a correct label to a given example, and explain how a biased dataset degrades classifier performance.
Anomaly Classifier
Open →Student can run a classifier on a telemetry example, interpret the predicted class and confidence score, identify the key contributing features, and explain the difference between rule-based and ML-based detection.
Confidence and False Alarms
Open →Student can explain the trade-off between sensitivity and false alarm rate, read a confusion matrix, and justify a sensitivity setting based on mission risk tolerance.
Human-in-the-Loop Decision
Open →Student can review telemetry evidence cards, apply a safety rule check to a proposed action, choose an appropriate response, and write a one-paragraph decision debrief.
| Track | Activity | Readiness | Maturity | Time |
|---|---|---|---|---|
| Orientation | What is a CubeSat Mission? | Implemented | Pilot Ready | 15–20 min |
| Orientation | Subsystem Detective | Implemented | Pilot Ready | 35–45 min |
| Orientation | Mission / Subsystem Trade-off | Implemented | Pilot Ready | 40–50 min |
| Orientation | Digital Twin Before Hardware | Implemented | Pilot Ready | 15–20 min |
| Launch, Gravity & Orbit Basics | From Launch to Orbit | Implemented | Pilot Ready | 20–25 min |
| Launch, Gravity & Orbit Basics | Orbit Speed and Altitude | Implemented | Pilot Ready | 25–30 min |
| Launch, Gravity & Orbit Basics | Low Earth Orbit vs Higher Orbit | Implemented | Pilot Ready | 20–25 min |
| Launch, Gravity & Orbit Basics | Ground Track and Coverage | Implemented | Pilot Ready | 20–25 min |
| Launch, Gravity & Orbit Basics | Contact Window Basics | Implemented | Pilot Ready | 20 min |
| Mission Design & Payload Thinking | Choose a Mission Objective | Partial / teaching | Pilot Ready | 20–25 min |
| Mission Design & Payload Thinking | Payload Drives the Mission | Partial / teaching | Concept Ready | 25–30 min |
| Mission Design & Payload Thinking | Payload Data Generation | Partial / teaching | Concept Ready | 25–30 min |
| Mission Design & Payload Thinking | Mission Success Criteria | Partial / teaching | Concept Ready | 30–40 min |
| Power / Thermal / Budgets | Power Budget Basics | Implemented | Pilot Ready | 25–35 min |
| Power / Thermal / Budgets | Day / Night Energy Balance | Implemented | Pilot Ready | 25–35 min |
| Power / Thermal / Budgets | Thermal Hot / Cold Case | Implemented | Pilot Ready | 20–30 min |
| Power / Thermal / Budgets | Mass / Volume / Resource Trade-off | Implemented | Pilot Ready | 25–35 min |
| Power / Thermal / Budgets | Solar Power Generation | Partial / teaching | Pilot Ready | 20–25 min |
| Power / Thermal / Budgets | Data Budget and Downlink Limit | Partial / teaching | Pilot Ready | 20–25 min |
| Power / Thermal / Budgets | Risk Flags and Engineering Decisions | Partial / teaching | Pilot Ready | 30–40 min |
| Communication / Ground Link | Line-of-Sight Communication | Implemented | Pilot Ready | 20–25 min |
| Communication / Ground Link | Data Rate × Contact Time | Implemented | Pilot Ready | 20–25 min |
| Communication / Ground Link | Link Margin Trade-off | Implemented | Pilot Ready | 25–30 min |
| Communication / Ground Link | Command / Telemetry Flow | Implemented | Pilot Ready | 20–30 min |
| Attitude Control & Pointing | Why Pointing Matters | Partial / teaching | Concept Ready | 15–20 min |
| Attitude Control & Pointing | Attitude Hold Basics | Implemented | Pilot Ready | 25–30 min |
| Attitude Control & Pointing | Step Response to +10 Degrees | Implemented | Pilot Ready | 25–30 min |
| Attitude Control & Pointing | Contact Window Pointing | Implemented | Pilot Ready | 25–30 min |
| Attitude Control & Pointing | Gentle vs Aggressive Control | Implemented | Pilot Ready | 30–35 min |
| Attitude Control & Pointing | Power-Aware Attitude Control | Implemented | Pilot Ready | 30–35 min |
| Attitude Control & Pointing | Daylight vs Eclipse Response | Implemented | Pilot Ready | 30–35 min |
| Telemetry, Evidence & Operations | Telemetry Dashboard Basics | Implemented | Pilot Ready | 20–25 min |
| Telemetry, Evidence & Operations | Subsystem Interpretation Walkthrough | Implemented | Pilot Ready | 35–40 min |
| Telemetry, Evidence & Operations | Replay and Mission Debrief | Implemented | Pilot Ready | 25–30 min |
| Telemetry, Evidence & Operations | Telemetry Trust and Stale Data | Implemented | Pilot Ready | 25–30 min |
| Telemetry, Evidence & Operations | Mission-Based STEM Capstone | Partial / teaching | Pilot Ready | 50–60 min |
| AI / ML & Autonomy | What Does Autonomy Mean? | Implemented | Pilot Ready | 20–25 min |
| AI / ML & Autonomy | Features, Labels and Training Data | Implemented | Pilot Ready | 30–35 min |
| AI / ML & Autonomy | Anomaly Classifier | Implemented | Pilot Ready | 25–30 min |
| AI / ML & Autonomy | Confidence and False Alarms | Implemented | Pilot Ready | 30–35 min |
| AI / ML & Autonomy | Human-in-the-Loop Decision | Implemented | Pilot Ready | 35–40 min |
Continue here
Links go to real routes only. Adjust pacing for your classroom or pilot charter.
Product preview: Preview standard activity shell — reusable layout foundation for future activities; Activity 00.1 is the yardstick reference implementation.
Start with the orientation mission builder, follow the eight-track arc through Track 7, then revisit the curriculum map or demo pack to consolidate evidence.
Use Teacher Mode for Tracks 0–7 lesson packs, timing presets, and facilitation prompts—then return here for outcomes, readiness labels, and sequencing.
Run Demo Pack timed scripts for schools or reviewers; pair Track 0–1 entries with the hardware boundary story when asked.
Check product depth from landing through learn and hardware boundaries—no backend claims, honest simulator labels.
Capability boundary