This activity is deliberately layered with four distinct insights, not one idea applied to bigger numbers: independent stages (P1), shrinking choices under a no-repeat rule (P2), complementary counting for "at least one" conditions (P3), and combining both P2 and P3 together (P4). Resist confirming complementary counting is the right move in Phase 3 until a group has genuinely tried the messy direct casework first and felt why it's painful โ that discomfort is what makes the shortcut land.
"You've been hired as a security consultant. The vault's owner wants to know exactly how many codes their system allows โ get the count wrong, and you'll either miss a real vulnerability or waste money fixing one that isn't there."
Students work entirely on their whiteboard. Display phase content on student devices only after each gate is unlocked.
The current system
General rule: a code of length \(n\), digits 0โ9, repeats allowed, gives \(10^n\) possible codes.
Require: correct count for 4 and 6 characters, and the general pattern stated as $10^n$ (or described correctly in words) โ this phase should move quickly for a strong group; don't let it drag.
A new security policy
In Phase 1 every position had exactly 10 choices no matter what came before (independent stages). Here, each choice removes an option from the remaining pool, so the number of choices depends on earlier decisions (dependent stages) โ that's a genuinely different structure, not just "a smaller number."
Order of reasoning matters here: count the most restricted position first.
The classic error here is writing $9\times9\times8\times7$ correctly but for the wrong reason, or writing $9\times8\times7\times6$ by incorrectly assuming the second position also loses a "generic" option rather than specifically losing whichever digit was used first. Ask a group to justify each factor individually if the answer is right but the reasoning is shaky.
Require: correct 5,040 answer with reasoning that references shrinking/dependent choices (not just "because there's one less digit"), and correct 4,536 with the most-restricted-position-first logic articulated.
A smarter security upgrade
Direct approach (what most groups try first): count exactly-1-letter, exactly-2, exactly-3, and exactly-4 codes separately, then add. This works but is genuinely tedious:
Complementary approach (the intended discovery): total codes minus all-digit codes.
Let a group finish the direct method if they're determined to โ arriving at the same answer two different ways is genuinely satisfying and reinforces that complementary counting isn't a trick, it's a shortcut to something they could always have done the long way. Don't rush them out of the direct method if they're making real progress; the "why bother with 4 cases when there's 1" realization lands harder after some real effort.
Require: correct final count (1,669,616) by any valid method, and โ this is the key one โ an explicit statement of the complementary idea in their own words, even if they only reach it after finishing the direct method.
Combining every rule at once
Groups should notice โ ideally without being told โ that the "all-digit no-repeat" count is identical to their Phase 2 answer. Pointing this out explicitly if they miss it is worthwhile: it's good evidence they've built a genuinely reusable technique, not just solved four separate puzzles.
Require: correct total no-repeat count (1,413,720), correct all-digit no-repeat count (5,040) explicitly connected back to Phase 2, and the correct final answer with the subtraction reasoning stated clearly.
Once the first character is forced to be a letter, an all-digit code is already impossible โ so the "at least one letter" condition is automatically satisfied and needs no separate handling.
The trap here is a group mechanically reapplying the Phase 4 subtraction method (total minus all-digit) without noticing it's now unnecessary โ that would still arrive at the right structure by coincidence in some setups, but the reasoning would be wrong. Push for the explicit realization that no subtraction is needed at all this time.
1. Have a group present Phase 2c's ordering trap โ why counting the most-restricted position first matters โ since this generalizes far beyond this activity.
2. For Phase 3, ask for a show of hands: who tried the direct 4-case method first? Have one of those groups briefly show how many separate calculations it needed, then have another group show the 2-line complementary version, side by side.
3. Explicitly name the technique: "counting the complement" โ and ask the class where else they might use "total minus the case I don't want" outside of this activity.
4. If time allows, preview that next class extends this same counting logic to circular arrangements โ where the fundamental counting principle alone isn't quite enough.