BOMBANANA Level 1 configuration: Build the language

BOMBANANA Level 1 sits in the opening training block. It provides 2:30 for Cable, permits 1 mistake, and assigns no Chaos duty. The coaching theme is “Build the language”: Practice positions, colors, and one confirmed answer at a time. These are preparation facts, not a stored solution; live colors, numbers, Braille, symbols, positions, and Random results must be read again on every bomb. Use numbered positions during the first scan, because a later color, symbol, or direction is only useful when the team can attach it to one control.

Only one mistake is allowed, so the group should favor a complete first read over an early speculative input. Every defusal slot is fixed by module family, so the team can rehearse the exact reporting order before loading the mission. There is no Chaos module in this mission, which makes it a useful place to measure the clarity of the core three-role relay. Before starting this BOMBANANA mission, agree on the first module, the fallback queue, and the exact interruption phrase. Start with the clearest shared state, then move toward the most demanding procedure. Early confirmation establishes rhythm without sacrificing a volatile panel. A known plan lets the team spend the countdown solving rather than negotiating vocabulary around active controls.

The BOMBANANA Level 1 defusal line is Cable. Its fixed module is Cable. A fixed family can be studied in advance, but its answer still depends on the new bomb’s colors, positions, Braille, parity, route, notes, or sequence. Read stable values first and changing values last. The order reduces the chance that a live state expires while Mute is still searching a rule branch.

Every defusal slot is fixed by module family, so the team can rehearse the exact reporting order before loading the mission. Number unidentified panels by physical position until their families are known, then replace the temporary labels with module names. Prefer the packet the team can complete cleanly, but never ignore a live interruption to chase an easy clear. Stability comes before cosmetic progress. This BOMBANANA habit prevents values from adjacent Random panels being merged into a convincing but impossible manual packet.

Open BOMBANANA Level 1 with a silent physical scan and one labeled briefing. Deaf maps visible families and positions; Blind checks tactile or Braille information without moving controls; Mute prepares the likely manual branches. With no Chaos assignment, the team can devote all three roles to the first complete packet. Read stable values first and changing values last. The order reduces the chance that a live state expires while Mute is still searching a rule branch.

Let the actual bomb decide the order rather than following the visual layout automatically. Stabilize any panel that changes, heats, or stores a sequence before beginning a slow unrelated lookup. Prefer the packet the team can complete cleanly, but never ignore a live interruption to chase an easy clear. Stability comes before cosmetic progress. In this BOMBANANA run, every new observation should clearly belong either to the active panel or to a named place in the queue.

Blind keeps hands clear until Deaf gives a physical location and the team confirms it. Blind reports tactile fields one at a time; Mute rejects a Level 1 packet missing an LED, stage, count, parity, coordinate, or history value; Deaf preserves the observed order and translates the result into Blind’s viewpoint. Use Blind’s viewpoint for the final instruction even when Deaf sees the panel from another angle. Viewpoint translation belongs before, not during, the movement.

Because there is no ongoing Chaos, use the mission to audit the core relay without a competing watcher task. Close every action with the observed result—cleared, unchanged, or new stage—so nobody silently carries an old answer into the next exchange. One owner at each stage keeps responsibility visible and prevents simultaneous instructions.

Do not divide the 2:30 BOMBANANA countdown evenly across 1 slot. A familiar panel may clear in one exchange, while a route or cumulative sequence needs several observations and confirmations. Reserve an opening scan, a central solving window, and a final reread buffer. Do not let a generous countdown create loose conversation. Consistent packet structure early is what keeps the same group functional when later timers contract.

At the halfway point of Level 1, diagnose any unresolved packet before asking everyone to speak faster. Identify whether the missing piece is observation, manual branch, gesture, physical position, or confirmation. Protect a final reread window. Entering the last seconds with several half-complete packets is riskier than finishing fewer panels with fully confirmed state. A targeted BOMBANANA reset—module, stage, missing field, answer, position—usually costs less than repairing a wrong input.

BOMBANANA Level 1 lists no Chaos module, although ordinary confusion can still break a packet. Use this recovery order: hands off, identify the interruption, resolve or acknowledge it, name the original module, then reread current state. Use “hands off” as a state-control command, not criticism. Neutral language makes it easier to stop a nearly completed action when the evidence changes.

One named watcher can manage the listed Chaos load when its warning threshold and restart phrase are fixed beforehand. After any break, ask whether the panel is unchanged, advanced, or reset. That classification determines whether the old lookup is valid or must be discarded. In BOMBANANA, correct logic applied to expired state still produces a wrong move.

Before attempting BOMBANANA Level 1, rehearse Cable without the timer and let each role state its ownership. Practice the longest packet, interrupt it on purpose, and return to the same module and current stage without reusing stale data. Replay the longest exchange once without a timer and once under pressure. Compare where vocabulary changes, because that is usually where reliability disappears. Repeat the weakest exchange once before loading the mission.

Review the first mistake or longest delay after the attempt. Tighten field order for a fixed module; rehearse the whole difficulty pool after a Random failure; shorten the emergency phrase if an interruption broke the chain. Rotate roles after a clean attempt. Experiencing each information limit helps players request only what the next person can actually observe or communicate. Reliable BOMBANANA progress comes from a reproducible protocol, not one fortunate run.

• State the 2:30 timer and 1-mistake limit before starting.
• Review Cable without memorizing a live answer.
• Prepare the fixed module order as procedures.
• Use the Chaos-free run to measure clean confirmations.
• Finish every packet with a physical position, repeat, and confirmation.