COSMO · STUDY + TEACHING DECK

Discrete Math

July 19, 2026

A question worth sharing

Error-Correcting Codes

Add structured redundancy so corrupted messages can be detected or corrected.

ThinkCompareExplain

Today’s route

A question becomes an explanation.

Try

Enter through a problem. A partial attempt counts.

Connect

Use codeword, Hamming distance, parity check to name what you notice.

Convince

Build an argument a partner can check.

The goal is a method someone else can use.

The opener

Start with a question.

Opening problem

What is the Hamming distance between 101101 and 111001?

Think · 2 min

Sketch, test a small case, or make a first guess.

Pair · 3 min

Compare methods. Find one thing you agree on and one question.

Be ready to share your route, even if it is unfinished.

Compare before checking

Put two attempts in conversation.

Explain

Tell a partner how you started. Let them finish before responding.

Question

Which step feels certain? Which step still needs evidence?

Build

Combine one useful idea from each attempt into a new route.

Can you explain your partner’s method in your own words?

Board conversation

Notice before naming.

Look for structure

Try a small case and record every step.
Separate what changes from what stays fixed.
State the pattern in a sentence before naming the theorem.

Make a conjecture

We think ___ because ___. A case that might break this is ___.

What changed? What stayed the same?

Useful language

Now the language has a job.

codeword

allowed transmitted string

Hamming distance

number of differing positions

parity check

constraint used to detect errors

Use one of these words to explain something you already noticed.

The core idea

Keep the idea. Explain the conditions.

t=\left\lfloor\frac{d_{\min}-1}{2}\right\rfloor

The idea

Add structured redundancy so corrupted messages can be detected or corrected.

What to remember

Redundancy becomes useful when its geometry separates valid messages.

What information does this method keep?

Worked example

One route, one decision at a time

The problem

Use an even parity bit for message 1011.

Predict each next step

The message contains three 1s.
Even parity requires an even total.
Append parity bit 1.
The transmitted word is 10111.

Which step needs a reason, not just a calculation?

See the structure

The structure behind error-correcting codes

t=\left\lfloor\frac{d_{\min}-1}{2}\right\rfloor

A code of minimum Hamming distance d guarantees correction of at most t changed bits.

Read the representation

Add structured redundancy so corrupted messages can be detected or corrected.

Look together

Point to the part that explains the relationship. Change one input and predict what changes.

What can you see here that was harder to see in words?

Two approaches

Compare the reasoning.

Structural method

Name the objects and conditions.
Use a reusable relationship.
Explain why the method must work.

Brute force

May help with a small test case.
Can hide the general reason.
Becomes unreliable when the scale grows.

Which route can you justify? What would you test first?

Reasoning clinic

Find the step that needs repair.

Investigate these concerns

May help with a small test case.
Can hide the general reason.
Becomes unreliable when the scale grows.

Repair together

Name the missing condition. Try a small counterexample. Rewrite one step so it is justified.

A useful correction explains why the original step fails.

Work together

Investigate error-correcting codes

Your shared task

Students design small codebooks, introduce errors, and test nearest-codeword decoding.

Explore

4 min - test cases

Compare

5 min - form a rule

Defend

4 min - defend the rule

Everyone should be able to explain the group’s final claim.

Share → connect

What did the room discover?

Bring your evidence

Share a conjecture, a useful example, or a route that changed.

Connections to investigate

Redundancy becomes useful when its geometry separates valid messages.
A complete solution names the condition that makes the method valid.
A counterexample is useful when it exposes a missing condition.

Which observation explains the mechanism?

Try → explain → check

Your turn to build the route

The problem

How many errors can a code with minimum distance 5 correct?

Predict each next step

Correction balls of radius t must not overlap.
Require 2t < 5.
The largest integer t is 2.
The code corrects two errors.

Which step needs a reason, not just a calculation?

Convince a skeptic

Turn a pattern into a proof.

The claim

A code with minimum distance d detects up to d-1 errors and corrects floor((d-1)/2).

Build the argument

Detection fails only if corruption reaches another codeword.
At least d changes are needed for that.
Unique correction requires disjoint radius-t balls, so 2t<d.

What does each step rely on? Where are the conditions used?

Stretch together

Take the idea somewhere new.

Transfer challenge

Create four binary codewords of length 3 with pairwise distance at least 2.

Choose a route

Name the objects, the conditions, and a relationship that might help. Start with one test case.

What transfers from the earlier example? What is different?

Peer review

Check the argument together.

Restate

Explain the other person’s route before evaluating it.

Test

Try a small case or boundary case. Does every step still make sense?

Revise

Fix an assumption, add a reason, or find a second method.

Where did your thinking change?

Beyond this problem

Where might this idea help?

A connection

Error-correcting codes protect storage, communication, QR codes, and deep-space signals.

Discuss the model

What objects or quantities are represented?
Which relationship from today is preserved?
What assumption would you check before trusting it?

Invent one more situation with the same structure.

Exit ticket

Leave with an explanation.

Question 1

What is the Hamming distance between 101101 and 111001?

Question 2

Explain why this claim is true: A code with minimum distance d detects up to d-1 errors and corrects floor((d-1)/2).

Question 3

Create four binary codewords of length 3 with pairwise distance at least 2.

Choose one. Write an answer with a reason, then compare with a partner.

Reflect together

Make your thinking visible.

I used to think…

Name a claim or approach that changed.

Now I can explain…

Give the reason, not only the result.

I still wonder…

Write a question worth bringing to the next circle.

Share one sentence. Ask one follow-up question.

The idea to keep

Redundancy becomes useful when its geometry separates valid messages.

Use the matching practice sets to move from direct examples to proof and transfer.

A good question belongs to everyone in the room.