What information matters?
🧮 Practice lab
Calculator check
Compute the expression here, then carry the result and LED state into the game callout.
Read back: expression → result → LED state.
➗ Two-stage cue: 🔢 enter the raw result → 💡 read the new LED → odd/even → ✅ press the returned digit.
Capture the expression, operator order, LED color or status, and the confirmation control. Read the expression left to right and repeat it before calculating.
How should the input be checked?
The interpreter says the expected value and the condition that makes it valid. The input player enters it once, confirms, and reports whether the display advances or shows an error.
How should a calculator solve be checked?
For example, 57 - 17 = 40 and 60 + 17 = 77 still follow the same workflow: read the expression, say the raw result aloud, wait for the indicator-light state, and only then confirm the entry. Two independently documented runs give useful checks: 60 + 22 = 82 with a blue LED and an even result leads to 1, while 37 with a blue LED and an odd result leads to 0. Both outcomes match the corresponding cells in the reference table. These are worked examples, not a substitute for recording the full live state when the game presents a different expression.
When recording a calculator solve, preserve the complete expression, the displayed result, the light color, and the confirmation timing. A result without its indicator state is incomplete because the light is part of the decision.
Final-key lookup
After the raw result is accepted, classify it as odd or even and use the new LED state. The current reference table is:
| Active LED | Odd raw result | Even raw result |
|---|---|---|
| Red | 3 | 5 |
| Green | 2 | 9 |
| Blue | 0 | 1 |
| Yellow | 7 | 0 |
The table agrees with the worked examples: 60 + 22 = 82 with a blue LED and an even result leads to 1, while 37 with a blue LED and an odd result leads to 0. The practice panel performs both stages: it calculates the raw result, then reports the final key from the LED and parity. If the game has not accepted the raw result yet, do not use the second-stage key.
What should be checked before calculating?
Use this four-field checklist: first number, operator, second number, and LED state. Read the expression twice if a digit is partially hidden or the panel is moving. The operator should confirm whether the panel expects the equation first and the LED-related value second before entering anything.
| Check | Example | Why it matters |
|---|---|---|
| Expression | 57 - 17 | A single digit changes the result |
| Result | 40 | The raw result is the first value to confirm |
| LED | Color and current state | It changes the follow-up mapping |
| Confirmation | Accepted / reset / error | Determines whether to continue or reread |
How should a failed calculator input be recovered?
Stop pressing, record the exact expression and LED state, and check whether the panel reset. Do not reuse the previous result after the indicator changes. Reopen the Module Solver for arithmetic, use Level Lookup to plan calculator practice, and open the puzzle index if the panel is not the calculator module.