Can you diagnose a complex system from incomplete evidence?
SYSTEM FAILURE: BLACKOUT · FACILITY ZERO: The lights are out, pressure sensors disagree, a chemical-process tank is warming, backup ventilation is intermittent and a biological culture system is drifting out of range. Some data packets are delayed. One alarm may be wrong. Your job is to restore the facility without assuming every alert has the same cause.
ACTIVE OBJECTIVESYSTEM FAILURE: BLACKOUT · FACILITY ZERO: The lights are out, pressure sensors disagree, a chemical-process tank is warming, backup ventilation is intermittent and a biological culture system is drifting out of range. Some data packets are delayed. One alarm may be wrong. Your job is to restore the facility without assuming every alert has the same cause.
Optional: pen + paper for rough working if that helps you think.
HOW TO DO IT
Read or listen to the Briefing + Learn.
Do the interactive mission.
Use facts from the reading and maths parts.
Make your choice and save your project step.
Play the weekly game. Finish Check-in.
WORK YOUR WAY
Short bursts are fine. Use Learning Tools for easier reading, read-aloud, less on screen, stronger contrast, no-rush and quieter-screen options.
If you get stuck, look at the example and try again.
SCIENCE SAFETY: The science investigations in this Senior mission are designed as virtual/screen-based activities unless the page clearly says otherwise. Do not improvise mains electricity, heating or chemical experiments at home.
PROJECT NOTE: Your project can stay digital. Physical making is optional unless you choose that format.
MISSION BRIEFING
SYSTEM FAILURE: BLACKOUT · FACILITY ZERO: The lights are out, pressure sensors disagree, a chemical-process tank is warming, backup ventilation is intermittent and a biological culture system is drifting out of range. Some data packets are delayed. One alarm may be wrong. Your job is to restore the facility without assuming every alert has the same cause.
✓Construct and compare competing failure hypotheses from incomplete multi-system evidence.
✓Distinguish correlation, consequence and plausible causal mechanism when failures occur close together in time.
✓Select quantitative evidence and risk reasoning independently to prioritise interventions.
✓Design resilience improvements that reduce single points of failure, improve observability and limit cascading effects.
◈
INTERACTIVE LEARN MODE
No passive video this week.
This mission is deliberately built around its simulator, investigation, decision room or prototype instead of an external video.
Year 8 diagnosis uses HYPOTHESIS → EVIDENCE → MECHANISM → COUNTER-EVIDENCE → PRIORITY → REDESIGN. Do not start with a favourite explanation and force every clue into it. Build at least two plausible hypotheses, identify what each predicts, and test them against the evidence. In a cascading failure, the initiating fault may be electrical while later symptoms appear chemical, biological, thermal or mechanical. Observability matters: delayed or faulty sensors can hide the true sequence. Resilient systems use redundancy, segmentation, fail-safe states, backup pathways and independent monitoring so one fault does not automatically propagate everywhere.
Year 8 diagnosis uses HYPOTHESIS → EVIDENCE → MECHANISM → COUNTER-EVIDENCE → PRIORITY → REDESIGN. Do not start with a favourite explanation and force every clue into it. Build at least two plausible hypotheses, identify what each predicts, and test them against the evidence. In a cascading failure, the initiating fault may be electrical while later symptoms appear chemical, biological, thermal or mechanical. Observability matters: delayed or faulty sensors can hide the true sequence. Resilient systems use redundancy, segmentation, fail-safe states, backup pathways and independent monitoring so one fault does not automatically propagate everywhere.
LEARNING BUILD
Learn it. See it. Try it.
Look at the example. Check another point of view. Then try the task.
Step 1: Choose a starting clueWHAT YOU ALREADY KNOW
Topic knowledge:Integrated Year 8 science and technology: electrical, chemical, biological, pressure, thermal and data systems under cascading failure.
This week’s first target:Construct and compare competing failure hypotheses from incomplete multi-system evidence.
Which clue is a good place to start?
Choose a source that can directly support part of the investigation. More than one source may be useful, but start with evidence that does not outrun its support.
Need more help? See the teaching
TEACH 1 · CORE MODEL
Year 8 diagnosis uses HYPOTHESIS → EVIDENCE → MECHANISM → COUNTER-EVIDENCE → PRIORITY → REDESIGN. Do not start with a favourite explanation and force every clue into it. Build at least two plausible hypotheses, identify what each predicts, and test them against the evidence. In a cascading failure, the initiating fault may be electrical while later symptoms appear chemical, biological, thermal or mechanical. Observability matters: delayed or faulty sensors can hide the true sequence. Resilient systems use redundancy, segmentation, fail-safe states, backup pathways and independent monitoring so one fault does not automatically propagate everywhere.
TEACH 2 · WHAT TO NOTICE
Construct and compare competing failure hypotheses from incomplete multi-system evidence.Distinguish correlation, consequence and plausible causal mechanism when failures occur close together in time.
TEACH 3 · CONNECT + TRANSFER
Select quantitative evidence and risk reasoning independently to prioritise interventions. Design resilience improvements that reduce single points of failure, improve observability and limit cascading effects.
WORKED EXAMPLE · EVIDENCE
GRID EVENT
At 02:14 the facility bus voltage falls sharply. Two critical loads transfer to backup power, while one ventilation controller fails to transfer.
Reasoning: Start with exactly what the source establishes. Connect it to the relevant concept, then stop before the claim becomes broader than the evidence. Now compare it with BIOLOGICAL CULTURE: Culture conditions drift out of range later in the event after temperature control and aeration become unstable. This timing is consistent with a downstream effect.
Why caution still matters:This item is useful context, but context is not the same as direct proof. Combine it with stronger evidence before making a broad conclusion.
WORKED EXAMPLE · MATHS / DATA ROUTE
One pressure sensor reports a 40% drop while an independent sensor reports a 6% drop. How many percentage points apart are the readings?
This week’s maths/data focus:Independently select percentages, rates, pressure/energy calculations, graph evidence and simple probability/risk reasoning.
Name the variable or relationship, keep the units visible, calculate or compare, then interpret the result as evidence about the system. A result can support an explanation without proving every possible cause.
Worked solution:Percentage-point difference is direct subtraction: 40% − 6% = 34 percentage points.Answer check:34 percentage points. Now return the result to the question and state what it means in context.
WE DO · GUIDED PRACTICE
Which source needs the most caution before it is used to support a broad conclusion?
Choose a source that mainly supplies context rather than direct proof of the whole conclusion.
YOU TRY · INDEPENDENT PRACTICE
For System Failure: Blackout, explain one core idea, connect it to one named source or observation and one quantitative/data point from this page, then state an alternative explanation, trade-off or limitation that a strong judgement must consider.
Write at least 30 words. Name the evidence or data you are using and keep the claim inside what it can support.
MISCONCEPTION CHECK
BIOLOGICAL CULTURE:Culture conditions drift out of range later in the event after temperature control and aeration become unstable. This timing is consistent with a downstream effect.
This item is useful context, but context is not the same as direct proof. Combine it with stronger evidence before making a broad conclusion.
HELP
Try: “If ___ changes, the mechanism predicts ___. Evidence ___ supports/challenges that. An alternative explanation is ___. I would test ___ next.”
STRETCH · OPTIONAL
Build the strongest reasonable counter-argument or alternative explanation. Name one additional piece of evidence that could distinguish between the two positions.
SYSTEM FAILURE: BLACKOUT · FACILITY ZERO⏻
BLACKOUT CONTROL
The dashboard is incomplete. Build the hypothesis that survives conflicting evidence.
FACILITY EVENT TIMELINE
02:14Bus voltage drops.02:15*Pressure sensors disagree: −40% vs −6%.02:20Process tank begins warming after ventilation loss.LATERBiological culture drifts out of range.
*Some network packets are delayed 8–12 minutes, so dashboard display order is not automatically causal order.
EVIDENCE ROLE AUDIT
GRID EVENTPRESSURE SENSOR CONFLICTTANK TEMPERATUREBIOLOGICAL DRIFTDELAYED DATA PACKETSVENTILATION CONTROLLER
COMPETING HYPOTHESES
Which hypothesis currently explains the widest evidence set with the fewest unsupported assumptions?
REDUCE UNCERTAINTY
Which diagnostic most directly addresses the contradictory pressure evidence?
DATA ORDER
Why should the network timestamps be audited?
RESILIENCE REDESIGN
Which redesign best reduces propagation from one controller failure?
Classify all six evidence roles, choose the strongest current hypothesis, reduce the pressure uncertainty, audit timestamp order and choose a resilience redesign.
OPEN THE COMPLETE INCIDENT FILE
SOURCE 1
GRID EVENT
At 02:14 the facility bus voltage falls sharply. Two critical loads transfer to backup power, while one ventilation controller fails to transfer.
SOURCE 2
PRESSURE DATA
A pressure sensor reports a sudden 40% drop at 02:15, but a second independent sensor on the same line reports only a 6% drop. The disagreement weakens confidence in the first reading.
SOURCE 3
PROCESS TANK
The tank temperature begins rising six minutes after ventilation fails. No evidence yet shows a chemical runaway; reduced heat removal is a competing explanation.
SOURCE 4
BIOLOGICAL CULTURE
Culture conditions drift out of range later in the event after temperature control and aeration become unstable. This timing is consistent with a downstream effect.
SOURCE 5
DATA NETWORK
Some monitoring packets arrive 8–12 minutes late during the blackout. Timestamp order must therefore be checked before inferring causation from dashboard display order.
SOURCE 6
SINGLE-POINT RISK
The failed ventilation controller has one power-transfer module and no independent fallback path. It is a plausible single point of failure.
INVESTIGATE + ENGLISH · EVIDENCE CASE
Incomplete evidence rewards the hypothesis that survives challenge
Facility Zero goes dark at 02:14, but the dashboard does not provide a perfect story. One pressure sensor reports a dramatic drop while another sensor disagrees. The process tank warms after ventilation fails, which could be consistent with reduced heat removal rather than an internal chemical reaction. Biological conditions drift later, after several supporting systems are already unstable. Meanwhile, delayed data packets mean the order displayed on screen is not necessarily the order events actually occurred. A strong diagnosis therefore compares hypotheses, checks independent evidence and prioritises mechanisms that explain several observations while surviving counter-evidence. The final redesign should not only repair the failed component; it should reduce the ability of one controller or data failure to propagate through the whole facility.
MAKE THE CALL
You can perform two immediate interventions and one diagnostic test. Choose them from backup ventilation transfer, electrical load isolation, process-tank cooling, pressure-line shutdown, culture-system support, independent pressure verification or network timestamp audit. Defend the order using mechanism, consequence, uncertainty and residual risk rather than alarm severity alone.
BUILD YOUR CASE CONCLUSION1. Make the call. 2. Use at least two relevant pieces of evidence. 3. Explain one limitation or uncertainty. 4. Finish with what can responsibly be concluded.Strong structure: My judgement is… The strongest evidence is… However, we still do not know… Therefore…
CASE CONCLUSION: Write 280–360 words as the Facility Zero technical board report. Present two competing hypotheses, identify the stronger one from at least four evidence items, use one quantitative comparison, explain one piece of counter-evidence or uncertainty, prioritise two interventions and propose at least three resilience redesigns across power, monitoring or subsystem isolation.
0/280 words minimum for this writing mission.
CLAIMEVIDENCELIMITATIONCONCLUSION
MATHS + DATA LAB
Check the numbers.
HOW TO SUCCEEDRead the situation first. Estimate what a sensible answer should look like, choose an efficient calculation, then use the feedback to check your reasoning.For data questions, explain what the number shows — and what it does not prove.
One pressure sensor reports a 40% drop while an independent sensor reports a 6% drop. How many percentage points apart are the readings?
Estimate first, then choose the answer.
MISSION 05 · MATHS + DATA LAB
DATA TRAINING
RATIO + RATE · YEAR 8 EXTENSION
6 PROBLEMS
QUICK METHODRATIO + RATE
Find one part or one unit first, then scale up.
GUIDED · Q01–Q03Use the quick method, then check the explanation.
Q01
A 2:3 ratio has 10 in the first part. What is the second part?
2 parts become 10, so each part is 5. Three parts = 15.
Q02
180 km in 3 hours is what average speed?
Rate = distance ÷ time = 180 ÷ 3 = 60 km/h.
Q03
4 notebooks cost $12. Cost per notebook?
$12 ÷ 4 = $3 each.
INDEPENDENT · Q04
Scale 1:100 means 2 cm represents…
2 cm × 100 = 200 cm = 2 m.
INDEPENDENT · Q05
A recipe for 4 uses 300 g. For 8 people?
The number of people doubles, so the quantity doubles to 600 g.
INDEPENDENT · Q06
Which is the better unit rate?
$3 each is the lowest unit price.
OPTIONAL CHALLENGE · OPEN RESPONSE
Two options have different starting fees and unit rates. Describe how you would find the break-even point.
0 words · optional
PROJECT HQ · TERM 3 · PRESENT
PROJECT HQ · PROJECT FILE 09
PRESENT & REFLECT.
Start something real. Build an idea, test it, improve it, and share it. Make your move.
DEFEND your finished Resilient Systems Challenge. Present the model boundary, variables, failure mechanism, evidence trail, competing explanation, redesign, retest and residual risk. Show where the model is useful and where it stops being reliable.
02LEARN
03INVESTIGATE
05DECIDE
07PROJECT
08CHECK-IN