Skip to main content

Week 7 · Five disciplines · One verified channel

Signal in the Snow

A mountain beacon is almost lost inside the storm. Find its pulse, protect its code, place a relay, define the handshake, and open a channel that never mistakes silence for success.

Reliable communication is a system, not a lucky message.

Wave patterns separate signal from noise. Code checks reveal damage. Terrain controls the path. A shared protocol defines acknowledgment and failure. The final decision connects all four.

Day 1

Monday

20 minutes

Physics · Waves, patterns, and noise

Hear the Hidden Pulse

Distinguish a repeating signal from noise using pattern, timing, and repeated observations rather than loudness alone.

Make

A signal evidence strip

Story handoff: The rescue team confirms a weak repeating pulse. To prevent a copied message from changing as it crosses the storm, the coders need a simple way to detect an error.

Day 2

Tuesday

25 minutes

Coding · Error detection and binary data

Repair the Frostbitten Code

Trace a compact error-detection rule and distinguish detecting an error from correcting it.

Make

A error-check trace

Story handoff: The message can now carry an error check and a request to resend. The team still needs a relay point with line of sight to both the valley receiver and the hidden beacon zone.

Day 3

Wednesday

25 minutes

Geography · Elevation and line of sight

Place the Mountain Relay

Use elevation profiles and practical constraints to choose a relay site without assuming the highest point is automatically best.

Make

A relay-site profile

Story handoff: Lantern Pass gives the rescue message a defensible route. Now every sender and receiver must use the same sequence so silence, damage, and acknowledgment cannot be confused.

Day 4

Thursday

25 minutes

Communication · Protocols and ambiguity

Write the Rescue Handshake

Write an unambiguous communication protocol with ordered states, acknowledgment, timeout, and bounded retries.

Make

A rescue handshake protocol

Story handoff: The rescue network can now tell delivery from silence and corruption. The final council must combine signal evidence, code integrity, geography, and protocol states into one launch decision.

Day 5

Friday

25 minutes

Systems reasoning · Evidence and rescue decisions

Open the Snowbound Channel

Synthesize physical, computational, geographic, and communication evidence into a testable operational decision.

Make

A mountain signal protocol

Story handoff: The first verified acknowledgment returns through the snow. The channel opens not because the storm vanished, but because every uncertainty now has a check, a state, or a stopping rule.

Open the signal console.

Attempts stay on this device. Finished work stays finished, and the family portfolio shows only evidence the learner actually completed here.

Quest progressProgress recorded