ICE BREAKER — Gameplay Specification

Playtest Blueprint — KN-86 Deckline Pack-In Title

Version 1.0 | April 2026 | Status: Definitive (Supersedes all prior ICE Breaker design in KN-86-Launch-Titles docs)

CIPHER-LINE revision note (2026-04-24): Every reference in this spec to “Cipher voice” narrating, warning, or commentary now describes output that renders on the CIPHER-LINE OLED above the keyboard, not on the main 80×25 grid. Main-grid Cipher dialogue is superseded. Where this spec shows a Cipher line as a full sentence (e.g., “CAPABILITY GAP DETECTED — NETWORK DEPTH EXCEEDS CURRENT MODULE.”), read it as the intent of the beat; the actual rendering on CIPHER-LINE is a clipped fragment pair honoring the voice heuristic (gap. network deeper. / not this one.). See the CIPHER-LINE Contributions section at the end of this spec for the authoritative vocabulary, production fragments, and mode-weight biases ICE Breaker declares. Canonical engine specification: docs/software/runtime/cipher-voice.md.

Mission Contributions

Mission Composition Grammar declaration — verb vocabulary, affinity tag set, and mission-contributions schema are defined in docs/plans/post-v0.1/2026-04-25-mission-composition-grammar.md §1–§3.

(mission-contributions
  :verbs (PENETRATE OBTAIN DESTROY OBSERVE)
  :affinities (DIGITAL NETWORK))

ICE Breaker is the canonical DIGITAL+NETWORK cart and the launch library’s primary anchor for the four offensive verbs. Network intrusion satisfies PENETRATE; data extraction satisfies OBTAIN; sabotage contracts satisfy DESTROY; surveillance implants satisfy OBSERVE. Default :payout-bias (1.0) and :threat-bias (0); ICE Breaker is the calibration baseline.

Capability Registration

ICE Breaker’s (cart-init) issues the following Mission Control capability declaration (canonical authoring contract: ../design-bibles/launch-titles-capability.md §1, ADR-0028 + ADR-0030):

(register-capabilities
  :module     :ice-breaker
  :bit        0x01
  :provides   '(:network-penetration :network-extraction
                :network-sabotage :network-surveillance)
  :affinities '(:digital :network)
  :seeds      '(network-topology ice-placement encryption-depth)
  :supersedes :terminal                ; per ADR-0030 — supersedes the System-tier baseline
  :threat-cap 6)                       ; cart-tier ceiling (vs TERMINAL's 2)

Relationship to baseline

ICE Breaker supersedes the System-tier :terminal baseline (../../runtime/baselines/terminal.md) per ADR-0030. While inserted, ICE Breaker amplifies the network-intrusion domain — providing the full PENETRATION / EXTRACTION / SABOTAGE / SURVEILLANCE schema set and lifting the threat ceiling from TERMINAL’s training cap of 2 up to the cart’s full operations ceiling of 6. Eject the cart and the deck falls back to TERMINAL’s training-tier penetration verb and capped contract pool. See ../../runtime/mission-control.md §2.3 (the supersedes mechanic) and §3.2.1 (threat-cap inheritance).

Design Philosophy

ICE BREAKER is not a puzzle. It is not a roguelike. It is a tempo sport — a real-time decision engine where the operator’s skill at reading systems (network, threat, toolkit, sound) under time pressure produces stories the designer never scripted. The operator’s learning arc follows John Boyd’s OODA loop: observe the world, orient into a decision frame, decide which action, act (press a key, commit irreversibly). The network, the threat, and the toolkit each run their own OODA loops in parallel. Emergence lives in the collision of these four systems. The core mechanic is Hot Swap — mid-run physical cartridge swaps that expand decision space and force the operator to develop relationships with multiple capability modules. Every session is different because four independent agents are cycling through their OODA faster or slower than the operator. The operator who learns to read tempo wins.

1. THE OODA LOOP: ATOMIC UNIT OF PLAY

The KN-86 Deckline is a tempo instrument. A single OODA cycle takes 2-5 seconds in the early game, 0.5-2 seconds in expert play. The operator who cycles faster than the threat system survives.

The Cycle

OBSERVE (0.5s): The network speaks. The LCD shows: current node’s ICE signature (text), connection status, tool slots, trace level. The YM2149 plays three overlapping voices in real time:

Voice 1: ICE proximity alarm (pitch rises as threat increases)
Voice 2: Data flow (extraction rate, encryption depth)
Voice 3: Pursuit intensity (if a HUNTER is chasing)

The operator presses INFO (left hand, top row). The screen overlays raw telemetry: node ID, ICE type, link quality, trace accumulation rate, estimated traversal time to egress. Sound drops to a soft hum. Listening is information. Silence is golden.

The operator has 0.5 seconds to absorb. The network is still ticking. Threats still advance.

ORIENT (0.5s): The operator has seen the raw data. Now they must interpret it. This is where learning compounds. An operator with Depthcharge history (previous run of the underwater sonar module) recognizes the ICE signature as JUNK-class and fast-paths the decision. An operator without history must synthesize from first principles.

Press INFO again (double-tap) to engage Orient assist: the Cipher voice narrates the situation. At low reputation (Apprentice, Journeyman), Cipher is verbose: “This node’s ICE is JUNK-class, slow. You can brute-force it or traverse.” At high reputation (Master, Legend), Cipher goes silent. You’re on your own.

The operator may also consult the cartridge history bitfield in Universal Deck State — a single-screen view showing which modules have been loaded and their completion status. This is a learned gesture. First-time operators skip it. Veterans check it reflexively.

Orient window: 0.5 seconds. The network is ticking. Threats are closing.

DECIDE (1s): The operator knows the situation. Now they choose: which tool, which key, which path. This is where Hot Swap enters as a decision moment.

Possible decisions:

Use a tool from the current toolkit. Press CONS (left hand, top row) to enter the combination matrix. Select two archetypes from the 6-8 available (each has a physical key or numpad pair). The matrix shows the combined result on the right: intuitive combos are predictable, surprising combos are discoverable via repeated use or Orient hints. Once combined, the tool is consumable and depletes on use.
Traverse the network graph. Press CAR to enter the current node. Press CDR to traverse back to the previous node. Press BACK to return to the network map.
Accept a risk. Press LAMBDA to initiate a speculative action (exploit a vulnerability you haven’t fully mapped, try a tool without full confidence).
Retreat entirely. Press LINK to attempt egress. This is only possible from certain nodes. Successful extraction ends the run with payout.

If the operator realizes mid-decision that they need a capability not loaded, this is the Hot Swap moment. The Cipher voice has been warning for 3-4 turns: “CAPABILITY GAP DETECTED — NETWORK DEPTH EXCEEDS CURRENT MODULE.” The operator can press QUOTE and initiate a physical cartridge swap. The network advances at half-tempo while the swap is in progress (realistic time: ~5 seconds, game time: ~10 seconds of network activity compressed). The swapped-in cartridge enters SCOPED CAPABILITY MODE — it doesn’t load its full experience, just its signature capability applied to the current problem.

Decide window: 1 second. The network is ticking. The threat is adapting.

ACT (immediate): The operator presses a key. This is irreversible. The network responds.

Press EVAL (the 1.75U-wide confirm bar across the bottom) to commit the decision. The cartridge’s nOSh API processes the input:

If a tool was selected, it is consumed and applied. The network changes state. New ICE may spawn.
If traversal was chosen, the operator moves. New node data loads. Threats advance.
If egress was chosen, the game attempts to route back to the entry node. Success = run ends. Failure = remain in network, trace increased.

The YM2149 plays a response tone. Voice 1 pulses (ICE reacting). Voice 3 may spike (threat escalating). The operator immediately sees the new state and the cycle repeats.

Why Tempo is the Core Skill

An OODA cycle has a natural duration. The network advances at a fixed tempo (node traversal time, ICE spawn rate, trace accumulation). The threat (HUNTER, BLACK ICE) cycles at a different tempo — faster or slower than the network. The operator cycles at whatever speed they can process.

An expert operator’s cycle rate: 2 per second (every 0.5s, OODA completes). This is a learned skill. A novice’s cycle rate: 1 per second (OODA takes 1s). The threat advances regardless.

When the operator’s cycle rate exceeds the threat’s cycle rate, the operator gains tempo advantage: they are reading and deciding faster than the threat can react. They slip through a network gap before HUNTER spawns. They extract a tool before trace reaches critical. They retreat before ICE locks the exit node.

Lose tempo and the threat takes the initiative. HUNTER enters your node. ICE cascades. Trace accumulates faster than you can process.

The YM2149 is the tempo instrument. As threat cycles accelerate, Voice 1 rises in pitch. As your cycle rate accelerates, Voice 2 (data flow) becomes more confident, less stuttering. Expert operators play the device like a drummer playing a kit — the audio is as much information as the screen.

2. SYSTEM ONE: THE NETWORK

The network is an organism, not a level. It is a procedurally generated directed graph of 8-16 nodes per contract. Each node is a cell: a corporate system, an encrypted relay, a finance server, a personnel database.

Topology and State

The network is seeded by contract parameters: threat level (1-5), contract type (PENETRATION, EXTRACTION, SABOTAGE, SURVEILLANCE IMPLANT), and cartridge history (which modules you’ve loaded). The seed determines:

Number of nodes
Node distances (traversal time)
ICE populations per node
Encryption depth (which tools are required)
Entry point (usually a public-facing node)
Exit point (usually the same node, 15 nodes deep for Threat 5)

Each node has state:

ICE population: 0-3 instances of JUNK, BLACK, RED, or HUNTER
Intrusion memory: If you triggered ICE here before, they remember. Returning to that node is harder.
Encryption state: Which tools have been applied. Once decrypted, stays decrypted (until network resets after extraction)
Data payload: What you’re extracting (0-100 credits equivalent)

The List Structure: CAR and CDR

The operator navigates the network as a Lisp list: CAR to enter a node (car is “contents of address register” — dig deeper), CDR to traverse backward (cdr is “contents of decrement register” — step back).

Current node is the HEAD of a traversal path. Press CAR to descend deeper, select a child node. The screen shows 3-4 options (adjacent nodes). Press a numpad key to select. The operator enters that node.

Press CDR to ascend, return to the parent node. This is always safe (though ICE may pursue).

The entry node is the root. Egress requires routing back to root and pressing LINK. This is not a trivial task on a Threat 4 or 5 contract. You may take damage (lose credits, increase trace) on the way out.

Fog of War and Observation

The operator cannot see the full network topology. Only the current node and adjacent nodes are visible. The OBSERVE phase (INFO keypress) reveals:

Current node’s ICE class and population
Connections to adjacent nodes (3-4 choices)
Trace level (how much attention you’ve drawn)
Time to next ICE spawn or threat escalation

Double-tap INFO for full sensor data. This is expensive (draws attention, takes time).

The network is a mystery. Learning happens through exploration and repeated runs. An operator who has done three Threat 3 contracts begins to recognize patterns: node types, ICE placements, traversal logic. This is Orient learning.

Network Memory: The Residue of Intrusion

The network remembers. Repeated intrusions change the topology. If you triggered ICE at Node 7 on your first run, Node 7 is now reinforced. The network has learned from the intrusion.

Specifically:

Nodes where you’ve triggered ICE spawn ICE faster
Connections you’ve used repeatedly become slower (network routes traffic away from known intruders)
Encryption depth increases in areas where you’ve used tools before (the sysop patches vulnerabilities)

This is why failed runs are not wasted. A failed run leaves trace data that enriches the next operator’s Observe phase. Trace is not punishment — it is a gift of information. A network you’ve explored before is slightly faster to read because you’ve seen the shapes.

3. SYSTEM TWO: THE TOOLKIT

Tools are consumable verbs. They are generated at cartridge load time and depleted on use. The operator never refills a tool during a run — what you load with is what you have.

The Six Core Archetypes

CRACK — Brute-force encryption. Fast, noisy. High trace cost. Suitable for low-security nodes. One use.
MIRROR — Copy data without removing it. Quiet, slow. Low trace cost. Suitable for data extraction without triggering alarms. One use.
SPIKE — Inject command code. Redirects ICE behavior, spawns false nodes, or clears a path. Variable cost. One use.
CLOAK — Mask operator identity. Reduces trace accumulation. Lasts 3-4 turns. One use.
SIPHON — Extract credits from encrypted finance nodes. High payout, high risk. One use.
GHOST — Erase evidence of intrusion. Retroactively reduces trace. One use.

CONS: The Combination Matrix

The toolkit is built by pressing CONS and selecting two archetypes. The combination generates an emergent tool. The matrix is a 6×6 grid. Most combinations are intuitive:

CRACK + MIRROR = QUICKCOPY (faster copy, moderate risk)
SPIKE + CLOAK = PHANTOM (inject code while masked, stealthy)
SPIKE + SIPHON = GRIND (extract credits faster but noisier)

Three to four combinations are surprising and only discoverable through exploration:

CRACK + GHOST = REWRITE (retroactively change which nodes you visited — ICE forgets you were ever there)
MIRROR + CLOAK = SHADOW (copy data while becoming invisible; trace is not accumulated)
SIPHON + CRACK = LAUNDER (extract credits through encrypted finance channels with no trace)

These surprise combos are hinted at through context. An Orient double-tap in a finance node gives Cipher voice a line: “Encrypted currency flows. A tool that combined extraction and stealth would slip through unnoticed.” This is a breadcrumb. Experienced operators will experiment and find SHADOW.

Using a combo tool consumes both archetypes. This creates tension: use a basic CRACK now, or wait and CONS a REWRITE later?

Degradation and Resource Tension

Each tool has a degradation counter. A CRACK tool starts at 3 uses before full degradation. Each use reduces the counter. At counter=0, the tool is exhausted and vanishes from the toolkit.

No. Wait. That’s wrong. Let me recalibrate.

Each tool is consumed on first use. No degradation counter. One use, then gone. This makes the CONS decision painful: every combination is permanent loss of two archetypes. Resource tension is vertical (do I have the tool I need?) not horizontal (do I have enough durability left?).

This is cleaner. Faster decisions. The tension is real: I see a finance node. I have SIPHON available. Do I use it now (100 credits payout) or CONS it into something else (LAUNDER, no trace)?

If I wait and move to the next node, SIPHON is still available. But if ICE spawns, I may have to burn resources I didn’t plan on. Tempo pressure.

Why Your Toolkit Shapes Orient

The toolkit you load with is your decision frame. An operator loaded with SPIKE, SPIKE, MIRROR, and CLOAK is prepared for a stealthy run: mask, copy, vanish. An operator loaded with CRACK, SIPHON, SIPHON, and GHOST is prepared for a grab-and-run: smash, take credits, erase traces.

The contract may not reward your toolkit. A Threat 4 contract in a heavily encrypted network (requiring multiple CRACK + MIRROR combos) will punish an operator with two SIPHON tools. Mismatch creates tension.

Experienced operators bring a balanced toolkit: 1-2 archetype pairs that generate multiple useful combos. Novices load full CRACK stacks and get locked out of finance nodes.

This is learning at the content level. It is not tutorial — it is felt through play.

4. SYSTEM THREE: THE THREAT

The threat is not a single entity. It is an ecosystem of ICE instances, each running its own OODA loop. Each ICE class cycles at a different tempo. The operator is a fifth agent in this ecosystem, and the operator is always slightly slower.

ICE Classes and Cycle Speeds

JUNK (Cycle: 2s): Slow, simple. Defends a single node. Broken architecture. Easy to brute-force or bypass. Spawns randomly on low-threat nodes. No intelligence. No memory.

BLACK (Cycle: 1s): Medium speed. Defends a region (2-3 linked nodes). Adapts to repeated intrusions. If you brute-force a BLACK once, the next BLACK in the region will be encrypted deeper. ICE learns.

RED (Cycle: 0.5s): Fast. Aggressive. When killed (tool consumed, ICE defeated), spawns a JUNK to its node AND propagates notification to adjacent nodes. RED does not die quietly. Using a tool to kill RED is a local victory with a global cost.

HUNTER (Cycle: 0.5s, then accelerates): The apex threat. Spawned by repeated intrusions (visiting the same node 3+ times) or by network escalation (trace threshold exceeded). HUNTER chases the operator across nodes. Its cycle speed increases each turn (0.5s → 0.4s → 0.3s). HUNTER cannot be killed with current toolkit tools — it can only be slowed (CLOAK) or evaded (by achieving tempo advantage and moving before HUNTER cycles). HUNTER is the run-ender. Most failures happen because HUNTER spawns and tempo inverts.

The Threat OODA: Parallel to the Operator

Each ICE instance runs a tiny OODA against the operator:

OBSERVE: Detect operator presence. ICE senses keypress volume, trace level, tool consumption. Faster keypress tempo = higher threat to the ICE’s assessment.

ORIENT: Classify the intruder. Apprentice (slow decisions, many tool uses = panicked), Journeyman (medium pace), Specialist (fast, measured). Adapt response accordingly.

DECIDE: Spawn additional ICE? Escalate encryption? Summon HUNTER? Wait and watch?

ACT: Execute decision. New ICE spawns. Encryption depth increases.

This is why repeated intrusions change the network. The sysop (embodied as the network’s immune system) learns your patterns. Fast operators are recognized sooner. Novices get second chances.

Trace: The Pressure Mechanic

Trace is accumulated score of operator attention. Every keypress adds trace. Using a tool adds trace. Triggering ICE adds trace. Trace decays slowly over time (you are forgotten if you stop moving).

At trace=30: HUNTER spawn warning (Cipher voice: “PERIMETER ALERT ISSUED”). You have 3-4 turns to egress. At trace=50: HUNTER spawns. The chase begins. At trace=75: Network lockdown. Exit nodes seal. You must fight through ICE to egress (take damage, lose credits, or stay trapped).

Trace is the timer that is not a timer. It is emergent pressure from the system learning you exist.

Detection ≠ Failure

This is critical. The operator does not fail when detected. Detection is a mode change. The tempo shifts. ICE is now hunting. The operator must cycle faster or die.

A Specialist operator at trace=35 with CLOAK available might stay in-network and ride out the search, using CLOAK to drop trace. A Journeyman operator at trace=35 will abort and egress. Both are valid tactics. The Specialist is higher-skill and higher-reward. The Journeyman is safer.

5. SYSTEM FOUR: SOUND

The YM2149 PSG is the fourth agent in the ecosystem. It is not background music. It is a real-time data channel.

Three Voices as Information Channels

Voice 1: ICE Proximity Alarm. Base frequency is set at cartridge load. As threat approaches, pitch rises. Threat=1 at 200Hz (barely audible hum). Threat=5 at 2800Hz (piercing shriek). An experienced operator can hear ICE spawning before it appears on screen.

The rate of pitch change is tempo information. Sharp increases mean HUNTER acceleration. Slow increases mean JUNK-class movement. An operator playing by ear alone (screen off, eyes closed) can estimate threat class and proximity.

This is not flavor. This is a valid play strategy. Speedrunners use sound-only modes. Accessibility feature as advanced technique.

Voice 2: Data Flow. The rate of Voice 2 pulses indicates extraction progress and encryption resistance. A tool is working quickly if Voice 2 accelerates. Encryption is deep if Voice 2 is stuttering. At full extraction, Voice 2 plays a rising arpeggio. At full failure, Voice 2 dies to white noise.

Voice 3: Environmental Chaos. Network instability, escalation status, and global threat level. When Voice 3 is silent, the network is calm and explorable. When Voice 3 is loud, the sysop is active and ICE is coordinating. Silence is exploration time. Noise is pressure.

The Audio Signature of Key Moments

OODA entry: Info keypress triggers a low tom (acknowledgment tone).

Tool selection (CONS): A descending arpeggio plays. The complexity of the arpeggio indicates tool rarity. Basic combos = 4-note arpeggio. Surprise combos = 8-note arpeggio with dissonance.

Successful tool use: Rising tone, high-pitched stab. The tone’s duration is proportional to the tool’s effectiveness.

Tool failure: Tone cut short, replaced by noise.

ICE spawned: Voice 1 jumps, a sudden attack. The attack is different per ICE class. JUNK = slow rise. BLACK = rapid rise. RED = sudden spike with chaotic secondary tones. HUNTER = all three voices spike simultaneously, then Voice 1 locks into a rising pitch.

Trace accumulation: A low, persistent drone that increases in volume as trace approaches critical. At trace=30, the drone becomes a rhythmic pulse (warning). At trace=75, the pulse dominates the mix (system lockdown).

Egress attempt: If successful, a resolving major chord (victory). If blocked by ICE, a discordant crash (failure), replaced by Voice 1 alarm (threat still active).

Cartridge swap (Hot Swap): A distinctive multi-voice stab as the nOSh runtime writes the phase chain to SRAM, then silence during the physical swap, then a reboot tone as the new cartridge initializes.

Playing by Ear as Advanced Technique

A Specialist operator with 20+ runs under their belt can navigate a Threat 3 contract with the screen off, using sound alone. This is not a game feature — it is an emergent skill.

The operator hears Voice 1’s pitch and knows threat approach. Hears Voice 2 accelerate and knows the extraction is working. Hears Voice 3 go quiet and knows the network is calm enough to explore new paths.

This is why sound design is mechanical, not cosmetic. The YM2149 is a sensory extension of the operator.

6. HOT SWAP: THE CAPABILITY MOMENT

Hot Swap is the mechanic that transforms ICE BREAKER from a closed puzzle into an open ecosystem. It is the moment where the operator realizes: “I need a capability I don’t have loaded.”

When and Why

The Cipher voice announces capability gaps in advance. On turn N-3 (3 turns before the gap becomes critical), Cipher intones: “CAPABILITY GAP DETECTED — NETWORK DEPTH EXCEEDS CURRENT MODULE.”

This is not a trap. This is a warning. An operator on a Threat 3 contract might ignore it. An operator on Threat 5 will prepare.

The gap manifests as an inaccessible node. You see a financial network node (SIPHON territory) but your current cartridge is ICE BREAKER (intrusion-focused). You have SIPHON available, but it’s unpowered by the cartridge’s capability model. Or you encounter encrypted underwater relay (Depthcharge sonar territory) and you don’t have the capability to analyze it.

The decision point: Do I try a raw brute-force approach (possible, high risk), or do I Hot Swap?

The Swap Mechanic

Acknowledgment: Press QUOTE on the Deckline. The nOSh runtime announces “INITIATING CAPABILITY SWAP” via Cipher voice. The screen goes black (cartridge is physically pulled).
Physical swap: The operator has 5-10 seconds to pull the current cartridge and insert the target cartridge into the SPI card slot. This is real time. A Sysop (paired operator) may interfere by pressing keys to accelerate threat while you’re swapping. Tension.
Reboot: The cartridge initializes. The nOSh runtime loads the new cartridge’s phase chain state from SRAM (the mission state is preserved). The screen returns to the network view. Cipher voice: “CAPABILITY LOADED — SCOPE MODE ACTIVE.”

Scoped Capability Mode

The swapped-in cartridge does not fully load. It enters scope mode: only its signature capability is available. An operator who swaps to Depthcharge gets sonar analysis tools but not the full Depthcharge experience (which is a deep-sea exploration narrative with its own contract types).

This prevents the operator from becoming lost in a different cartridge’s world. You swap, solve the capability problem, then swap back (or continue forward, deeper into the network, with a new capability available).

Network Advance During Swap

While the operator is holding the Deckline but the screen is black, the network advances at half tempo. ICE does not spawn. Threats do not escalate. Trace accumulation pauses. This gives the operator a small safety window.

The Cipher voice counts down: “SWAP TIME REMAINING: 3… 2… 1… NETWORK RESUMING AT STANDARD TEMPO.” After the countdown, the network resumes at full tempo. If the operator hasn’t finished the swap, the run is at risk.

Why This Is Exciting

Hot Swap is the peak decision moment in a run. It has several properties:

It requires external action. You must physically move. The game becomes embodied. On a real KN-86 (hardware version), you are literally opening the cartridge slot, feeling the card edge, seating the new cartridge. This is not a menu. This is ritual.
It creates multiplayer tension. If you’re playing Sysop Mode (asymmetric two-deck), the sysop can see you swapping and accelerate threat. The human defender is now playing against your physical action, not just your digital decision.
It expands decision space. The operator who owns two or three cartridges has more options. An operator with ICE BREAKER, Depthcharge, and Black Ledger can approach a mixed-threat contract with three different capability sets. An operator with only ICE BREAKER must solve problems within its domain.
It is always a choice, never required. On Threat 1-2 contracts, Hot Swap is never necessary. You can brute-force your way through. The operator who chooses to swap is taking a more elegant path or exploring a deeper level. The operator who doesn’t swap is still valid. But they are aware of what they gave up.

Example Scenarios

Scenario A: Depthcharge Swap

The operator is 6 nodes deep in a Threat 3 Penetration contract. The current node is an encrypted underwater relay (signature ICE: KRAKEN class, only weak to sonar analysis). The operator has CRACK + MIRROR tools, neither of which are effective against KRAKEN.

Cipher warns: “CAPABILITY GAP DETECTED — ENCRYPTION SIGNATURE UNKNOWN.”

The operator decides to swap to Depthcharge. The nOSh runtime preserves the mission state. The operator physically pulls ICE BREAKER, inserts Depthcharge. The cartridge boots. Scope mode active: only sonar analysis is available.

The operator uses sonar (press INFO + EVAL combination) to analyze the KRAKEN. The sonar reveals the ICE’s harmonic frequency. The operator returns to the same node now equipped with this knowledge. The KRAKEN’s effective threat level is reduced (it was always there, but now the operator can read it).

The operator swaps back to ICE BREAKER (or could continue with Depthcharge if they want to explore further). The network advances at half tempo. The mission resumes. The operator is now deeper in the network, with one more capability consumed.

Time cost: ~15 seconds real time, ~30 seconds game time (due to half tempo). Worth it to advance without triggering alarm? Depends on trace level and reputation.

Scenario B: Black Ledger Swap

The operator is on a Threat 4 Sabotage contract. The objective is to infiltrate a finance node and corrupt transaction records. The operator is equipped with SPIKE, CLOAK, and SIPHON.

At the finance node, the operator realizes the records are encrypted with legal tender codes — they require knowledge of real-time currency exchange rates and audit trails. ICE BREAKER doesn’t do that. Black Ledger (an accountant’s cartridge) does.

The operator swaps to Black Ledger scope mode. The cartridge provides a ledger interface showing financial flows. The operator can now see which transactions to corrupt and the optimal sabotage method (which ones will cascade into account freezes, which ones will trigger investigation, etc.).

The operator executes the sabotage with Black Ledger’s insight. Then swaps back to ICE BREAKER to escape the building before the audit system locks down.

The Black Ledger swap gave intel that ICE BREAKER lacked. Without the swap, the sabotage would succeed but leave obvious traces. With the swap, the sabotage is surgical.

Scenario C: Neongrid Swap

The operator is navigating a 9-node Threat 3 contract. The network topology is maze-like (by design, to slow down operators). The operator keeps hitting dead-ends (nodes with only the parent as an exit).

Neongrid (a spatial exploration cartridge) provides a map visualization. The operator swaps, Neongrid scope mode activates, the cartridge renders a bird’s-eye view of the known network topology. The operator sees an optimal path to the objective.

The operator doesn’t need Neongrid’s full experience (which would be a different contract type entirely). Just the map. The operator swaps back to ICE BREAKER and executes the optimized path.

This is Hot Swap as a tool for exploration, not capability gap-filling. It’s valid and rewarded (fewer moves = less trace = safer extraction).

7. EMERGENT COLLISIONS

The four systems — network, toolkit, threat, sound — are designed to collide. The collision produces moments the designer did not script.

The Degrading Toolkit Collision

An operator on turn 6 of a 12-turn contract realizes they’ve used CRACK, CLOAK, and MIRROR. They have SIPHON, SPIKE, and GHOST remaining. The next three nodes require speed (short traversal window before ICE spawns). SPIKE is fast. SIPHON is slow. GHOST is useless (no evidence yet).

The operator must choose: Use SPIKE now (gain tempo) or wait for SIPHON to be useful later (risk encounter with undecrypted nodes).

They use SPIKE. It spawns additional ICE (RED side effect). Now ICE is coordinating across nodes. The operator’s tempo window closed. They must abort and egress.

This is not a failure state designed by the designer. This is an emergence: the toolkit depletion state collided with the network state to create a new strategic problem.

The Network-Memory Collision

An operator completes a Threat 2 contract on their first attempt. The network is now enriched with intrusion memory. Two weeks later, they attempt the same Threat 2 contract again (same seed, because they remember it felt easy).

But the network has learned. ICE is placed more aggressively. Encryption is deeper. The operator is now facing a harder version of the same contract, without realizing why.

They fail. But the failure teaches them: networks have memory. Easier contracts become harder on repeat. The operator stops repeating seeds and seeks new contracts. Cartridge learns player.

The Sound-Tempo Collision

An operator learns to identify HUNTER’s audio signature (all three voices spiking simultaneously). They are on a Threat 3 contract, moving through nodes quickly, playing by ear with the screen off (a learned technique).

They hear Voice 1 accelerate. They hear Voice 3 go chaotic. But they don’t hear the all-three-voice spike. They misjudge: is it a RED spawn, or an approaching HUNTER?

They decide it’s RED. They continue forward.

It was HUNTER. HUNTER cycles faster than the operator’s decision-making. The operator hears the spike too late. HUNTER is already two nodes away.

This is a death moment. It emerges from the operator’s learned techniques colliding with a false-positive in their Orient phase.

The Surprise Combo Collision

An operator has learned through repeated use that CRACK + MIRROR = QUICKCOPY, and SPIKE + CLOAK = PHANTOM. They haven’t discovered SHADOW (MIRROR + CLOAK = become invisible while copying).

They encounter a high-security node with a high-value payload. They want to copy without trace. They have MIRROR and CLOAK available, but they’ve never CONS’d them together.

They decide to try MIRROR + CLOAK on a whim. The arpeggio that plays is unusual — 8 notes with dissonance. Surprise combo. SHADOW emerges. The operator successfully exfiltrates the entire node’s data without a trace spike.

The operator has accidentally discovered a surprising interaction. This discovery is meaningful because it came from their decision-making, not from a hint.

The Linked Play Collision

Sysop Mode: Two operators. One is the intruder (running ICE BREAKER), one is the defender (controlling the threat escalation via the sysop interface on a second KN-86).

The intruder cycles OODA every 1 second. The sysop cycles their control loop (detect threat, decide escalation, spawn ICE, adjust trace) at a variable rate. The sysop is human. Humans are unpredictable.

An expert intruder predicts the sysop’s escalation patterns and exploits them (the sysop always spawns BLACK at node 5, so the intruder doesn’t even go to node 5 on second contracts).

A novice sysop is chaotic. ICE spawns randomly. The intruder can’t predict and must retreat.

A good sysop learns the intruder’s patterns and counters them.

This is high-level emergence: human decision-making (sysop) colliding with AI decision-making (network, ICE) and the human intruder’s learned strategies.

8. SESSION SHAPE: THE EMOTIONAL ARC

Every session has a natural shape. The shape depends on reputation, threat level, toolkit, and the operator’s learned tempo.

The 15-Minute Apprentice Run

An operator with reputation 3 (Apprentice) takes a Threat 1 contract. They have basic tools and no cartridge history.

Minutes 0-2: Curiosity. The operator is exploring the first three nodes, orienting into the contract. Cipher voice is verbose. “You are now at a public-facing financial node. This is a good place to enter the network.” The operator presses INFO and CONS and tries combinations, watching what happens.

Minutes 2-5: Building Confidence. The operator has used three tools and cleared four nodes. No ICE spawned. The tempo is slow. “I can do this,” the operator thinks.

Minutes 5-10: Deepening Puzzle. The operator encounters a more difficult node. ICE population increases. A JUNK-class ICE is in the way. The operator must decide: brute-force with CRACK (high trace), or find a back route (requires deeper exploration).

The operator gets trace=20. Cipher warns: “Perimeter alert issued.” The operator realizes the run has entered a new phase. Not dangerous yet, but they are noticed.

Minutes 10-13: Hurried Escape. The operator drops compass. They’ve explored enough to find the exit. They navigate back toward the root node, moving faster, taking risks. One more CRACK use. Trace=35.

Minute 13-15: Extraction Moment. The operator reaches the exit node. Pressing LINK. A BLACK-class ICE is defending the exit. The operator has no tools left. They LAMBDA a speculative move (press LAMBDA + a numpad key hoping for a system exploit).

It works. The ICE misses. The operator extracts. Payout: 80 credits. Reputation +1. New cartridge history bit set. Session over.

Total time: 15 minutes. The operator is not exhausted. They are beginning to understand the systems.

The 45-Minute Specialist Run

An operator with reputation 18 (Specialist) takes a Threat 3 Extraction contract. They have a balanced toolkit and know Depthcharge and Black Ledger history.

Minutes 0-5: Rapid Assessment. The operator does rapid INFO double-taps and builds a mental map of the first 4-5 nodes. They see a pattern: there’s an encrypted finance node at node 6 (Black Ledger territory) and an encrypted data relay at node 9 (Depthcharge territory).

The operator decides: they will swap to Depthcharge at node 9, extract sonar analysis, then push deeper. They will not swap to Black Ledger (the Specialist is confident enough to solve finance with ICE BREAKER’s tools alone).

Minutes 5-25: Efficient Traversal. The operator cycles OODA at 2 cycles per second. They use tools sparingly. They navigate the first 6 nodes with only one tool consumption (SPIKE to clear a BLACK-class guard).

Trace=15. Low threat.

Minute 25: The Hot Swap Decision. The operator reaches node 9. The encrypted relay is KRAKEN-class ICE. Cipher warns of capability gap. The operator debates: brute-force CRACK (likely to fail) or swap to Depthcharge (time cost, but higher success).

The operator decides to swap. They physically pull ICE BREAKER, insert Depthcharge. The cartridge boots. The operator analyzes the KRAKEN using sonar. The relay’s harmonic signature is revealed: it’s a JUNK variant, not true KRAKEN.

Minutes 26-30: Recovered Tempo. The operator swaps back to ICE BREAKER. Trace=17 (low, due to half-tempo network advance during swap). The operator now continues deeper, knowing they’ve made the right decision. Confidence is confirmed.

Minutes 30-40: Deepening Challenge. Nodes 10-12 are tighter. ICE is coordinating. Trace climbs to 45. A HUNTER spawn warning is issued. The operator accelerates. They use CLOAK to drop trace. Trace=28.

Minutes 40-43: Extraction Approach. The operator is at node 13 (deep network). They have identified the target (high-value data payload). They use MIRROR to exfiltrate without destruction (silent extraction, low trace cost).

Payload secured. Trace=30.

Minutes 43-45: Exit Route. The operator routes back to the root, moving fast. They encounter one more BLACK-class guard at node 4. They have no tools left. They press LAMBDA + a numpad combo, gambling. It fails.

The BLACK ICE escalates threat. Trace jumps to 55. HUNTER enters a nearby node.

The operator is two nodes away from extraction. HUNTER is chasing. Voice 1 is screaming (ICE proximity alarm). The operator cycles OODA at maximum tempo: 3 cycles per second (expert level).

Turn 1: Move to exit node. Turn 2: Press LINK to egress. Turn 3: Network attempts to route operator out.

HUNTER reaches adjacent node. Trace=70. But the operator has completed the egress command. The nOSh runtime is routing them out. The network resists (ICE blocking the exit path), but the operator’s command takes priority.

A discordant crash, replaced by voice 1 alarm (the exit route is under attack). But the operator is through. Extraction successful.

Payout: 340 credits (base 200 + 140 for speed bonus, no failures). Reputation +3. Session over.

Total time: 45 minutes. The operator is satisfied. They solved a Threat 3 with one Hot Swap and no failed exits. They are improving.

Why Failed Sessions Advance Orient

An operator takes a Threat 2 contract and fails at node 8 of 10. HUNTER spawned and they couldn’t escape. Failure.

But the failure is valuable. The operator learned:

This network’s entry point leads to a heavily populated region
JUNK-class ICE at node 5 is deployed to detect fast-moving operators
Trace accumulation is faster in this network than expected
A successful approach would require slower, stealthier traversal

On the next contract, the operator applies these lessons. They move slower. They use CLOAK earlier. They accept a lower pace.

The failed run advanced their Orient phase. They are now better calibrated for this threat level.

9. ONBOARDING: THE FIRST FIVE MINUTES

There is no tutorial screen. The device is turned on. The BOOT sequence runs. The nOSh runtime loads.

Boot Sequence

The Deckline powers on. The screen shows:

[AMBER ON BLACK]
KN-86 DECKLINE CARTRIDGE SYSTEM
NOSH RUNTIME v2.4 — ZAIBATSU DIGITAL

UNIVERSAL DECK STATE LOADED
  OPERATOR HANDLE: [ _________ ]

A cursor blinks. The operator enters their handle. This is their identity across all cartridges. 3-8 characters. The operator types and presses EVAL.

The screen continues:

CARTRIDGE DETECTED: ICE BREAKER v1.0

MODULE CLASS: 0x01 (INTRUSION SUITE)
THREAT RANGE: 1-5
INITIAL REPUTATION: 0 (APPRENTICE)

MISSION BOARD LOADING...

A procedurally generated set of three contracts appears:

CONTRACT 1: SURVEILLANCE IMPLANT
  THREAT LEVEL: 1 | PAYOUT: 40 CREDITS
  OBJECTIVE: Install tracking device in corporate database

CONTRACT 2: PENETRATION (SECURITY TEST)
  THREAT LEVEL: 1 | PAYOUT: 45 CREDITS
  OBJECTIVE: Breach a test network, escape undetected

CONTRACT 3: DATA RECONNAISSANCE
  THREAT LEVEL: 1 | PAYOUT: 35 CREDITS
  OBJECTIVE: Observe and map a network structure

The operator selects CONTRACT 2 (the default is Threat 1). They press a numpad key to select. The nOSh runtime begins the run.

First Run: The OODA Lesson Through Play

The operator boots into the network at the root node. The screen shows:

[NODE 0 — ROOT RELAY]
ICE CLASS: JUNK (SLOW)
CONNECTIONS: 3 NODES AVAILABLE

TOOLKIT:
  A) CRACK (Fast encryption bypass)
  B) MIRROR (Silent data copy)
  C) CLOAK (Identity masking)

TRACE LEVEL: 0
CIPHER VOICE: "Welcome to the network. You are at the root relay."
             "Your objective is to reach objective node and return."
             "OBSERVE the network. DECIDE your path."

The operator presses INFO (OBSERVE key). The screen updates with detailed telemetry. The YM2149 plays a simple tom hit. The operator is learning: INFO reveals information. Listening reveals more.

The operator presses INFO again (ORIENT key). Cipher voice narrates: “The root relay has three connections. Node A leads to financial systems. Node B leads to security archives. Node C is unknown.”

This is the ORIENT assist. The Cipher voice has interpreted the data.

The operator now DECIDES. They press CAR to enter a node. They select Node C (the unknown one, because it is interesting). The nOSh runtime moves them there.

[NODE C — UNKNOWN RELAY]
ICE CLASS: BLACK (MEDIUM)
CONNECTIONS: 2 NODES AVAILABLE
  * Return to root
  * Deeper node (NODE D)

TOOLKIT:
  A) CRACK (available)
  B) MIRROR (available)
  C) CLOAK (available)

Immediately, something is different. The YM2149 Voice 1 rises in pitch (ICE proximity alarm). The operator hears it. They are learning: pitch = threat.

The operator presses INFO. Raw data. They press INFO again. Cipher interprets: “This node has BLACK-class defensive ICE. You have not encountered this class before. It is faster than JUNK. It remembers your intrusions.”

The operator ACTs. They press CONS (combination) and selects CRACK + CLOAK. The combo merges into PHANTOM (mask while breaking encryption). One tool slot consumed.

The screen shows: “APPLYING PHANTOM TOOL…” The YM2149 plays an arpeggio. The tool activates. The ICE is masked and the encryption is cracked. Trace increases slightly (the tool had some noise, but less than raw CRACK alone).

The operator is now at NODE D. New situation. Same cycle repeats.

Over the next 3-4 cycles, the operator navigates to a deeper node and finds the “objective.” They press EVAL to confirm. The nOSh runtime awards 5 credits for successful interaction.

Now the operator must return. They navigate back through the nodes they’ve explored. TRACE is climbing (trace accumulates for each turn spent in the network). At TRACE=25, Cipher voice intones: “Perimeter alert issued.”

The operator recognizes this from the mission briefing: trace at 25 means they are noticed. They accelerate. They press CDR to go back to the root node. They press LINK to attempt egress.

The exit is clear (no ICE is guarding on Threat 1). The nOSh runtime announces: “EXTRACTION SUCCESSFUL.”

The mission ends. The operator returns to the mission board.

What the Operator Learned (Without Explicit Teaching)

INFO reveals data. INFO double-tap provides interpretation. This is OBSERVE and ORIENT.
The Cipher voice is a guide who gets progressively quieter as your reputation increases.
CONS combines tools into new effects. Combinations can be surprising or intuitive.
The YM2149 is a real-time information channel. Pitch = threat. Arpeggio = tool effect. Silence = exploration time.
Pressing EVAL commits an action irreversibly. Sound confirms or denies success.
TRACE accumulates. At certain thresholds, the network escalates.
The goal is simple: reach a node, extract, return.

All of this was learned by playing, not reading. The first run is a safe failure zone (Threat 1 has no HUNTER spawn, low ICE populations, generous trace thresholds). The operator is encouraged to experiment.

10. LINKED PLAY: SYSOP MODE

The KN-86 Deckline is designed for solo play. Linked play is an optional asymmetric mode.

Two KN-86 units connect via a 3.5mm TRRS cable (audio + control lines). One unit runs ICE BREAKER as the intruder. The other unit runs a sysop interface (nOSh runtime mode 0x10: Sysop Control).

The Sysop Role

The sysop sees a different screen:

[SYSOP INTERFACE]
NETWORK STATUS: NORMAL
INTRUDER DETECTION: NODE 5 (TRACE=18)

THREAT CONTROLS:
  [SYS] → Initiate network-wide alert
  [BACK] → Spawn ICE at specified node
  [LINK] → Accelerate trace accumulation
  [CAR] → Route ICE to intercept intruder
  [CDR] → Lower ICE alert status

VOICE CHANNELS:
  Voice 1 (ICE alarm) — Sysop control
  Voice 2 (Data flow) — Intruder control
  Voice 3 (Chaos) — Shared (escalates with threat)

The sysop is a human defender. They can:

Manually spawn ICE at specific nodes
Accelerate threat escalation (pressing LINK to increase trace + spawn HUNTER)
Route ICE to intercept the intruder’s likely escape path
Adjust the YM2149 Voice 1 (making ICE alarms louder or quieter, signaling threat level)

The intruder (ICE BREAKER operator) does not know which choices the sysop will make. The sysop’s decisions are unpredictable (because sysop is human). This asymmetry creates high-tension play.

Linked Play Dynamics

An expert intruder vs. a novice sysop: The intruder predicts the sysop’s spawning patterns and exploits them. They move through gaps in the sysop’s ICE placement. The intruder’s experience advantage dominates.

A novice intruder vs. an expert sysop: The sysop predicts the intruder’s likely routes and pre-positions ICE. The sysop’s experience advantage dominates.

A matched pair: The game is back-and-forth. The intruder cycles OODA at 2Hz. The sysop cycles their defensive loop at 0.5Hz (human reaction time). The intruder has tempo advantage, but the sysop can make strategic decisions the intruder can’t react to in time.

Economics

Both operators benefit from successful extraction:

Intruder: Payout from contract completion + bonus for speed.
Sysop: Security fee (percentage of contract payout) + bonus for successful defense (if extraction is blocked, sysop gets a defense payout).

If the intruder succeeds, both operators profit (intruder gets the larger cut). If the intruder fails, the sysop gets a smaller but guaranteed fee.

This creates a negotiation dynamic. A novice intruder might say, “I’ll take easy contracts so you get your security fee without stress.” An expert intruder might say, “I’m taking Threat 4. You get half of my payout if I escape.” The partnership adjusts difficulty to find a sustainable dynamic.

Setup Requirements

Two KN-86 units (hardware version) or two emulator windows (emulator version with network bridging)
One 3.5mm TRRS audio cable (carries both audio mix and control signals via multiplexing)
Phase chain synchronization (the nOSh runtime must sync mission state between devices every 2 seconds)

The emulator version supports linked play via OSC (Open Sound Control) networking over localhost. Two emulator instances can connect and run linked play across the same machine.

11. CROSS-MODULE INTEGRATION: THE FOUR-CARTRIDGE ECOSYSTEM

ICE BREAKER is designed to work alone and in concert. The other three launch titles (Depthcharge, Black Ledger, Neongrid) each add a capability layer that ICE BREAKER can access via Hot Swap.

Cartridge History and Reputation

Universal Deck State contains a cartridge history bitfield (16 bits, 4 cartridges × 4 bits per cartridge for completion status: 0=never loaded, 1=loaded once, 2=completed easy contract, 4=completed hard contract).

Reputation is global across all cartridges. Loading a cartridge for the first time is a skill-agnostic action. Completing a contract with a cartridge adds to reputation at a fixed rate (5 rep per easy contract, 15 rep per hard contract, regardless of which cartridge).

The operator’s reputation is their credential: “I am rep 25 (Master)” across the entire system, not “I am rep 25 in ICE BREAKER, rep 10 in Depthcharge.”

How Each Cartridge Improves OODA

Depthcharge (Sonar Analysis Capability):

Improves OBSERVE phase
Operator can use sonar to analyze encrypted relays, underwater networks, and encrypted node types
Sonar reveals: ICE class, node population, encryption depth, node age (how many intrusions it’s seen)
Hot Swap to Depthcharge when encountering deep encryption on ICE BREAKER contracts
Long-term benefit: Operators who regularly load Depthcharge develop faster OBSERVE reading of similar node types on ICE BREAKER solo runs

Black Ledger (Financial Audit Capability):

Improves DECIDE phase
Operator can use ledger interface to plan tool consumption optimally
Ledger shows: which nodes contain highest-value payloads, which ones are guarded, optimal extraction order
Hot Swap to Black Ledger when planning complex EXTRACTION contracts
Long-term benefit: Operators who regularly load Black Ledger develop intuition for financial node patterns; they make better DECIDE calls on ICE BREAKER

Neongrid (Spatial Navigation Capability):

Improves ORIENT phase
Operator can use map visualization to understand network topology
Map shows: all explored nodes, their connections, traversal times, node types
Hot Swap to Neongrid when lost or planning a new route
Long-term benefit: Operators who regularly load Neongrid develop spatial intuition; they navigate larger networks faster on ICE BREAKER solo

ICE BREAKER (Core Intrusion Suite):

Improves ACT phase
Base capability: all other cartridges depend on ICE BREAKER as foundation
Intrusion tools (CRACK, MIRROR, SPIKE, CLOAK, SIPHON, GHOST) are only accessible with ICE BREAKER loaded
No long-term bonus (ICE BREAKER is always available)

Hot Swap Scenarios Across Cartridges

An operator developing all four cartridges can Hot Swap strategically:

Full Sonar Run: Load Depthcharge for the entire contract. Focus on encrypted relay analysis. All OBSERVE phases use sonar. Suitable for educational play or high-difficulty contracts where encryption depth is the limiting factor.
Audit + Swap: Load Black Ledger for initial contract planning, then swap to ICE BREAKER for execution. Spend the first 5 minutes with Black Ledger (DECIDE phase) planning the optimal extraction route, then swap and execute with ICE BREAKER’s tools.
Escape Swap: Load ICE BREAKER for the intrusion and execution. At extraction, swap to Neongrid to visualize the optimal escape route back to root, then swap back to ICE BREAKER and execute the egress.
Chain Swap: On a long Threat 4-5 contract, perform multiple Hot Swaps. Depthcharge for deep encrypted nodes, Black Ledger for financial decision-making, back to ICE BREAKER for execution. Each swap costs time but expands decision quality.

The Capability Curve

Session 1 (ICE BREAKER alone): The operator is learning OODA with limited tools. Threat 1-2 contracts only.

Sessions 2-5 (ICE BREAKER + 1 alt cartridge): The operator loads a second cartridge and learns Hot Swap. They can now attempt Threat 2-3. They experience the value of a second capability.

Sessions 6-15 (ICE BREAKER + 2-3 alt cartridges): The operator owns multiple cartridges and can Hot Swap fluidly. They attempt Threat 3-4. They are developing reputation.

Sessions 16+ (Full four-cartridge library): The operator owns all four and can Hot Swap freely. They attempt Threat 5 contracts. The system is fully open. Emergence is maximal.

12. APPENDIX A: “THE RUN”

Session Log: Operator CIPHER, Reputation 18 (Specialist)

Contract: EXTRACTION, Threat 3, Corporate R&D Facility Network Payout: 250 credits base (240-340 with bonuses) Cartridges available: ICE BREAKER, Depthcharge (loaded), Black Ledger

MINUTE 0:00 — BOOT AND SELECTION

The Deckline powers on. CIPHER enters their handle. The mission board loads. Three Threat 3 contracts are available. CIPHER selects EXTRACTION (they want data, not destruction).

CONTRACT BRIEFING:
  Objective: Extract prototype designs from Research Node 9
  Entry point: Node 0 (Root Relay)
  Threat: Research facility ICE (Medium speed, adaptive)
  Payout: 250 base + speed bonus
  Recommended: 12-15 node traversal
  Estimated risk: MODERATE (trace 50 acceptable, 75+ dangerous)

[OBSERVE] CIPHER presses INFO. The briefing display shows detailed telemetry: entry coordinates, recommended toolkit balance, estimated ICE distribution. Voice 1 plays a soft drone (threat is present but not acute). Voice 2 is absent (no extraction in progress).

[ORIENT] CIPHER thinks: “Threat 3, moderate speed. I have Depthcharge loaded, but I’m not sure I’ll need it. I can start with ICE BREAKER solo and swap if the encryption gets deep. Prototype designs are likely at a secured research node, probably node 8-10.”

[DECIDE] CIPHER decides to load ICE BREAKER as the primary cartridge. The nOSh runtime loads the capability module. The phase chain is initialized (empty, new run).

[ACT] CIPHER presses EVAL to begin.

MINUTE 0:30 — NETWORK ENTRY

[NODE 0 — ROOT RELAY]
ICE CLASS: JUNK
POPULATION: 1 JUNK instance
CONNECTIONS: 3 nodes (A, B, C)

TOOLKIT LOADED:
  Slot 1) CRACK
  Slot 2) MIRROR
  Slot 3) SIPHON
  Slot 4) (empty)

TRACE: 0
CIPHER VOICE: "Entry confirmed. Root relay is lightly defended.
               The network is waiting. What is your first move?"

[OBSERVE] CIPHER presses INFO. The screen updates:

  • Node A: FINANCE (encrypted, likely BLACK-class)
  • Node B: SECURITY (standard encryption, likely JUNK or BLACK)
  • Node C: RESEARCH ARCHIVE (unknown, likely contains research data)

Hmm. Node C is directly toward the objective. That’s unusual. ICE BREAKER contracts often hide the objective nodes deeper.

[ORIENT] CIPHER double-taps INFO. Cipher voice: “Node C is a research archive. Direct path, but likely defended. Node A is financial and encrypted — slow to traverse but valuable if you need credits. Node B is security — a checkpoint. Recommend cautious approach.”

CIPHER interprets: Node C is bait. The direct path to research is too easy. The real research node (Node 9) is probably deeper. Nodes A and B are distractions or secondary objectives.

[DECIDE] CIPHER decides: Move to Node B (security checkpoint). A Specialist learns to move through checkpoints carefully. It builds map knowledge.

[ACT] CIPHER presses CAR to enter a node, selects Node B via numpad.

MINUTE 1:00 — NODE 1 (SECURITY CHECKPOINT)

[NODE B — SECURITY CHECKPOINT]
ICE CLASS: BLACK
POPULATION: 1 BLACK instance
CONNECTIONS: 2 nodes (Root, Node D)

TRACE: 5 (slight bump for entering BLACK-class node)
CIPHER VOICE: "Security checkpoint. BLACK-class ICE guards access.
               Adaptive. It will remember your intrusions."

[OBSERVE] CIPHER presses INFO. Raw data: Black ICE’s encryption depth is 2 (moderate). Trace accumulation at this node is 2 per turn (fast, because ICE is active). The connection to Node D is “active” (recently trafficked, ICE is alert).

[ORIENT] CIPHER double-taps INFO. Cipher voice: “This BLACK-class instance is fresh. It has not been defeated before. Using a brute-force tool (CRACK) will be loud and costly. Using a silent tool (MIRROR) will be slow but stealthy.”

CIPHER thinks: I have MIRROR available. I could use MIRROR to silently pass this node. But MIRROR is my silent extraction tool. I might need it at Node 9 (the objective). Alternatively, I could use CRACK + MIRROR to create QUICKCOPY, a balance of speed and stealth.

[DECIDE] CIPHER decides: Use CRACK + MIRROR (CONS combination). Creates QUICKCOPY. Cost: 2 toolkit slots, 1 tool combo.

[ACT] CIPHER presses CONS, selects CRACK and MIRROR. The arpeggio plays (8 notes, medium complexity). The QUICKCOPY tool manifests in the toolkit. CIPHER presses EVAL to apply QUICKCOPY.

Voice 2 accelerates (tool in use, data flow increasing). The BLACK ICE is bypassed. Trace increases to 12 (moderate cost for a moderately stealthy tool).

MINUTE 1:30 — NODE 2 (RESEARCH DISTRIBUTION)

[NODE D — RESEARCH DISTRIBUTION HUB]
ICE CLASS: JUNK
POPULATION: 2 JUNK instances (not actively hostile, inventory systems)
CONNECTIONS: 3 nodes (Return to B, Node E, Node F)

TRACE: 12

[OBSERVE] CIPHER presses INFO. Two JUNK instances are here, but they’re not guarding. They’re inventory systems. The connections show Node E and Node F are both connected to this hub. Node E is marked as “ARCHIVE,” Node F is marked as “DEVELOPMENT.”

[ORIENT] CIPHER double-taps. Cipher voice: “This is a distribution hub. Archive node (E) likely contains old research. Development node (F) is active. The objective (recent prototype designs) is probably at F.”

CIPHER learns the network structure: The operator is building a map. The objective is likely at Node F (deeper, more active). But going to F requires moving through more nodes. Time cost vs. success rate.

[DECIDE] CIPHER decides: Move to Node F (Development). Direct approach to the objective location.

[ACT] CIPHER presses CAR, selects Node F.

MINUTE 2:00 — NODE 3 (DEVELOPMENT LAB)

[NODE F — DEVELOPMENT LAB]
ICE CLASS: RED
POPULATION: 1 RED instance (active, hostile)
CONNECTIONS: 2 nodes (Return, Node G — Deeper)

TRACE: 15 (moderate, yellow warning)
CIPHER VOICE: "Development lab. RED-class ICE detected.
               Aggressive. Will spawn additional ICE on defeat."

[OBSERVE] CIPHER presses INFO. RED-class means: if defeated with a tool, it spawns a JUNK instance elsewhere in the network. This is escalation. The trace accumulation at this node is 3 per turn (fast).

But more importantly: Node F only leads to Node G. There’s no escape from Node G except back to F. This is a deeper gamble.

[ORIENT] CIPHER double-taps. Cipher voice: “RED-class instances are aggressive. Defeating it will draw attention elsewhere. The deeper node (G) may contain the objective, or it may be a dead-end trap.”

CIPHER thinks hard. They have one tool remaining (SIPHON). If they use SIPHON here, they lose their last tool slot. They can’t CONS again. But SIPHON won’t help against RED-class ICE — SIPHON extracts credits, not clears encryption.

CIPHER realizes: They need to either find another tool slot or abandon the deep path and return to Node E (Archive), which might have research data at lower risk.

[DECIDE] CIPHER decides: Retreat to Node E (Archive), not Node G. A Specialist knows when deeper is not better.

[ACT] CIPHER presses CDR (go back), then presses CAR to enter Node E from the hub.

MINUTE 2:30 — NODE 4 (RESEARCH ARCHIVE)

[NODE E — RESEARCH ARCHIVE]
ICE CLASS: BLACK
POPULATION: 1 BLACK instance
CONNECTIONS: 2 nodes (Return, Node H — Deeper)

TRACE: 18
CIPHER VOICE: "Research archive. Contains older prototype designs.
               BLACK-class ICE guards access. Moderate risk."

[OBSERVE] CIPHER presses INFO. BLACK-class here is different from the earlier BLACK — this one is focused on data protection, not access denial. Encryption depth is 1 (light). Trace accumulation is 1 per turn (slow, because this ICE is not aggressive, just protective).

The tool bar shows: 1 SIPHON remaining. No CONS options (you need 2 tools to CONS, and CIPHER has 1).

[ORIENT] CIPHER double-taps. Cipher voice: “Archive stores old designs. Lower risk, lower value. Recent designs are likely deeper. Node H may contain more current research.”

But CIPHER is only at Trace=18. They have room to escalate (trace 50 is the “elevated threat” threshold on this contract). They can afford to attempt Node H.

But they don’t have tools. SIPHON alone won’t help with encryption.

CIPHER realizes: They need a second capability. Black Ledger (financial analysis) won’t help here. Depthcharge (sonar analysis) might help with deeply encrypted nodes.

Actually, wait. CIPHER brought Depthcharge loaded. CIPHER can Hot Swap.

[DECIDE] CIPHER thinks: “I’m at Trace=18. I have about 30 turns before trace becomes dangerous (50). If I Hot Swap now, I can:

Use Depthcharge to analyze the deeper encryption (Node H and beyond)
Get sonar signatures for encrypted nodes
Swap back to ICE BREAKER and execute extraction with better knowledge”

CIPHER decides to Hot Swap.

[ACT] CIPHER presses QUOTE (Hot Swap initiation).

MINUTE 3:00 — HOT SWAP MOMENT

Cipher voice: “INITIATING CAPABILITY SWAP. Physical cartridge replacement required.”

The screen goes black. The YM2149 stops playing. CIPHER is holding the Deckline, but the device is inactive. In a real hardware scenario, CIPHER would now physically open the cartridge slot, pull ICE BREAKER, and insert Depthcharge.

In the emulator, we’re simulating the 5-second physical swap.

The network is advancing at half-tempo during the swap. Threats are not escalating. Trace is not accumulating. This is the grace period.

After 5 seconds (simulated), the new cartridge is seated. The Deckline boots. Voice 1 plays a reboot tone. The screen returns to the network view.

[NODE E — RESEARCH ARCHIVE] [SCOPED CAPABILITY MODE]
ICE CLASS: BLACK
DEPTHCHARGE SONAR ACTIVE

Sonar can analyze:
  • ICE class and subtype
  • Node encryption depth
  • Node age (intrusion history)
  • Signal propagation (distance to adjacent nodes)

Current scan: Node H (adjacent)
  Encryption depth: 3 (DEEP)
  Ice class: BLACK variant (Pattern-adaptive)
  Node age: 0 intrusions (Fresh ICE)
  Propagation: Medium (normal traversal time)

[OBSERVE + ORIENT combined] CIPHER is now using Depthcharge sonar. The OBSERVE phase shows raw node data (encryption depth 3). The ORIENT phase is enhanced: Cipher voice explains: “Node H is heavily encrypted. Pattern-adaptive ICE means it learns from repeated intrusions. This is where the recent prototype designs likely are. Risk is moderate-to-high.”

CIPHER is now a Specialist with sonar intel. They can make an informed decision.

[DECIDE] CIPHER thinks: “Node H is deep encryption (depth 3). I don’t have the tools to crack depth 3 with ICE BREAKER alone. But I can:

Continue deeper with Depthcharge sonar, mapping more nodes
Swap back to ICE BREAKER and attempt a different route
Use SIPHON + ICE BREAKER combination to extract financial data instead of research data”

CIPHER decides: Continue deeper with Depthcharge sonar. Map the network. Find the real objective.

[ACT] CIPHER presses CAR, selects Node H.

MINUTE 3:45 — NODE 5 (ADVANCED RESEARCH VAULT)

[NODE H — ADVANCED RESEARCH VAULT] [SCOPED CAPABILITY MODE]
ICE CLASS: RED (Pattern-adaptive variant)
POPULATION: 1 RED instance (dangerous)

DEPTHCHARGE SONAR SCAN:
  Encryption depth: 4 (CRITICAL)
  ICE class: RED-adaptive
  Node age: 0 intrusions (Fresh, highly alert)
  Signal propagation: High (slow traversal)
  Data payload signature: PROTOTYPE DESIGNS (match objectives)

CIPHER found it. The objective is here. But it’s defended by RED-adaptive ICE at encryption depth 4.

Cipher voice: “OBJECTIVE LOCATED. Node H contains the prototype designs. Encryption depth 4 exceeds current capability. Recommended: retreat, resupply with capability modules, or attempt high-risk extraction.”

[OBSERVE] CIPHER sees the objective is behind RED-adaptive ICE, which will spawn additional ICE if defeated. The encryption depth is 4, which ICE BREAKER alone cannot handle.

[ORIENT] CIPHER thinks: “I need a combination of capabilities. Depthcharge has mapped the node. ICE BREAKER has tools. But I don’t have a tool that can handle encryption depth 4.”

Cipher voice continues: “CAPABILITY GAP DETECTED. Encryption depth 4 requires advanced decryption or redirect. Recommend Hot Swap to Black Ledger for financial redirect protocol, or ABORT and plan differently.”

[DECIDE] CIPHER realizes: Black Ledger can help. Black Ledger’s financial audit capability can redirect payment flows, potentially bypassing the ICE entirely. CIPHER will Hot Swap to Black Ledger, use its redirect protocol, then swap back to ICE BREAKER to extract.

[ACT] CIPHER presses QUOTE (second Hot Swap).

MINUTE 4:15 — SECOND HOT SWAP

The screen goes black. The YM2149 stops. Network advances at half-tempo.

CIPHER physically swaps Depthcharge (out) for Black Ledger (in). The reboot tone plays. The screen returns.

[NODE H — ADVANCED RESEARCH VAULT] [SCOPED CAPABILITY MODE]
ICE CLASS: RED (Pattern-adaptive variant)

BLACK LEDGER FINANCIAL AUDIT ACTIVE:
  Encryption depth: 4 (analyzable)
  Payment routing: SIPHON protocol available
  Redirect vector: Financial authorization channel (bypass ICE, use sysop-level credentials)
  Risk: MEDIUM (draws financial audit attention, but bypasses RED ICE)

[OBSERVE + ORIENT] Black Ledger has mapped the financial flows. The research vault has a procurement system that authorizes research transfers. By accessing the financial authorization channel, CIPHER can bypass the RED ICE guard (the ICE doesn’t monitor financial transactions, only network intrusions).

[DECIDE] CIPHER will use Black Ledger’s financial siphon protocol. This is a risky play: it draws financial audit attention, but it completely bypasses the RED ICE.

[ACT] CIPHER uses Black Ledger’s REDIRECT SIPHON protocol. The YM2149 plays a complex arpeggio (Black Ledger signature). Trace increases to 28, but the objective is being extracted.

The data payload (prototype designs) is being copied to a financial ledger (disguised as a purchase order). Black Ledger’s scoped capability handles the transfer.

MINUTE 4:40 — EGRESS DECISION

CIPHER has the objective. Now they need to escape. They are at:

Node H (deep in the network)
Trace=28 (yellow warning, approaching escalation)
No tools remaining (SIPHON was used)
Black Ledger loaded (but not as useful for escape)

Cipher voice: “Objective extracted. Financial routing successful. Recommended: exit the network immediately. Trace is approaching escalation threshold.”

[OBSERVE] CIPHER presses INFO. Adjacent nodes: return to Node E (Archive). From there, back to the security checkpoint (Node B), then back to root (Node 0). Traversal will take 3-4 turns. Trace will accumulate.

[ORIENT] CIPHER double-taps. Cipher voice: “Extraction complete. Return path is clear. Trace accumulation during escape will be ~2-3 per turn. You will reach trace ~35-38 at root. Acceptable risk.”

[DECIDE] CIPHER decides: Escape now. Don’t explore further. Get out.

[ACT] CIPHER swaps back to ICE BREAKER (third Hot Swap for the purpose of having intrusion tools available during escape, though none will be used).

The screen goes black. Reboot tone. CIPHER is back to ICE BREAKER scope mode.

MINUTE 5:15 — ESCAPE ROUTE

CIPHER navigates back: Node H → Node E → Node B (Security Checkpoint) → Node 0 (Root).

Each transition costs 1-2 trace accumulation. Trace climbs: 28 → 31 → 33 → 35 → 38.

At Node 0 (Root), CIPHER presses LINK (escape attempt).

The network attempts to route CIPHER out. The nOSh runtime checks: is there a clear exit route? Yes. The root relay has no ICE guarding (JUNK-class only, and it’s busy with other traffic).

Extraction begins. Voice 1 plays a rising tone. Voice 2 plays a resolving chord (success). Trace drops to 0 (operator is no longer in the network).

MINUTE 5:45 — SESSION END

EXTRACTION SUCCESSFUL

PAYOUT CALCULATION:
  Base payout: 250 credits
  Speed bonus: +40 credits (completed in 5:45, under target 12-15 min)
  Stealth bonus: +30 credits (trace never exceeded 50)
  Objective bonus: +40 credits (prototype designs extracted)

  TOTAL PAYOUT: 360 credits

REPUTATION GAIN: +8 (Threat 3 contract, clean extraction)

NEW TOTAL: Reputation 26 (MASTER tier)

CARTRIDGE HISTORY UPDATE:
  ICE BREAKER: Completed Threat 3
  Depthcharge: Used for analysis (history updated)
  Black Ledger: Used for extraction (history updated)

DECK STATE SAVED TO SRAM

MISSION COMPLETE.

CIPHER is now Master tier (reputation 26). They successfully extracted the objective using two Hot Swap moments and a combination of three capabilities. The session took 5:45, well under the estimated 12-15 minutes (speed bonus). Trace never exceeded the escalation threshold (stealth bonus). Total payout: 360 credits.

SUMMARY

ICE BREAKER is a tempo sport where the operator’s OODA loop cycles against three adversarial systems: the network (procedurally generated, adaptive), the threat (ICE with independent cycles), and the toolkit (consumable, combinatorial). Emergence lives in the collisions of these systems. The Hot Swap mechanic (mid-run cartridge swaps) expands decision space and creates physical ritual moments that are both tactile and strategic.

A session arc follows the operator’s emotional journey: curiosity → confidence → pressure → improvisation → escape. No two runs are identical because the network remembers intrusions, the threat adapts to player tempo, and the toolkit’s combination matrix produces surprising interactions.

The device teaches itself through play. Sound is a first-class information channel. Failure advances learning (failed runs leave trace data). Reputation is persistent across all cartridges, encouraging players to develop relationships with multiple capability modules.

The four-cartridge ecosystem (ICE BREAKER + Depthcharge + Black Ledger + Neongrid) creates a capability curve: one cartridge → full library. Each additional cartridge improves a specific OODA phase (Depthcharge = Observe, Black Ledger = Decide, Neongrid = Orient).

Linked play (Sysop Mode) adds an asymmetric multiplayer layer where human unpredictability becomes a core mechanic.

This is not a roguelike. This is not a puzzle. This is a real-time tempo instrument for reading and deciding under pressure. The operator who learns to cycle faster than the threat will survive.

DESIGN NOTE: THE PERFECT GAME AND THE 8 FALLACIES

The ICE Breaker perfect game — a clean extraction at maximum threat with zero trace and no failed tool applications — is structured around the operator internalizing and exploiting the 8 Fallacies of Distributed Computing (Deutsch/Gosling, 1994). Each fallacy maps to an assumption the network’s defensive systems make, and the perfect operator is the one who never makes these assumptions themselves:

The network is reliable. It isn’t. Nodes drop. Connections degrade on repeated intrusion. The perfect operator plans alternate routes before they’re needed.
Latency is zero. Every traversal costs time and trace. The perfect operator accounts for traversal cost in every decision — never assuming instant movement.
Bandwidth is infinite. Tool slots are finite. Data extraction is rate-limited. The perfect operator never over-commits tools to a single node.
The network is secure. The entire game exists because it isn’t. But this cuts both ways — the operator’s own position is never secure either. The perfect operator never assumes a cleared node stays cleared.
Topology doesn’t change. Networks remember intrusions and reshape. The perfect operator treats the map as a living document, not a solved puzzle.
There is one administrator. ICE operates independently. HUNTER has its own cycle. The sysop (in linked play) adds a third adversarial intelligence. The perfect operator reads each system as a separate actor with separate tempo.
Transport cost is zero. Every action accumulates trace. Every swap costs network-advance time. The perfect operator accounts for the true cost of every move — not just the immediate effect.
The network is homogeneous. Nodes vary wildly: encryption depth, ICE class, data type, tool compatibility. The perfect operator never applies a one-size-fits-all strategy.

The perfect game is not about memorizing patterns. It is about developing an intuition that never falls for any of the 8 fallacies — cycling OODA faster than the threat while respecting every hidden cost the network imposes. Operators who internalize these principles stop thinking about individual tool combinations and start thinking about the network as a system with friction, memory, and cost at every layer.

CIPHER-LINE Contributions

Per the CIPHER-LINE Grammar Framework, ICE Breaker declares the following cipher-grammar block in its .kn86 container. The nOSh runtime merges these contributions into the active grammar tables at cart-load and removes them at pull. The coherence stack persists across pulls.

Vocabulary Pools

(:subject              "ice" "trace" "node" "packet" "relay" "shell"
                       "handshake" "core" "perimeter" "sentry")
(:object               "firewall" "core" "shell" "perimeter" "handshake"
                       "pipe" "edge" "gate")
(:location             "sector" "node" "subnet" "backbone" "edge"
                       "deep-node" "shallow-node")
(:verb-present         "pings" "hums" "watches" "routes" "slips"
                       "locks" "mirrors" "siphons")
(:verb-past-participle "compromised" "extracted" "burned" "mirrored"
                       "cracked" "slipped" "pinned")
(:memory-keyword       "ice" "trace" "handshake" "shadow" "relay"
                       "hunter" "black ice" "junk" "kraken")
(:affect-word          "loud" "clean" "watched" "silent" "noisy"
                       "cold" "wrong")

Production Fragments (merged into nOSh baseline)

(:mode-observe
  (3 (:subject) ". " (:heading?))
  (2 (:location) " " (:verb-present) ".")
  (2 (:object) ". " (:affect-word) ".")
  (1 "trace up."))

(:mode-annotate
  (3 "that one. " (:affect-word) ".")
  (2 (:ice-breaker/ice-class) " " (:affect-word) ".")
  (1 "too clean.")
  (1 "watched."))

(:mode-reflect
  (3 "same " (:memory-keyword) ". " (:memory-fragment))
  (2 "this node. " (:memory-fragment))
  (1 (:memory-fragment) ". then the trace."))

(:mode-drift
  (2 "the one that pinged back.")
  (2 "last relay. three decks ago.")
  (1 "handshake at dawn.")
  (1 "kraken. sector nine."))

; Cart-scoped non-terminal — only callable by ICE Breaker productions
(:ice-breaker/ice-class
  (3 "black.") (3 "red.") (2 "junk.") (1 "kraken.") (1 "shadow."))

; Event-types registered globally; any cart may emit these once registered
:event-types
  ((:type :ice-crack        :affect (:tense))
   (:type :trace-spike      :affect (:tense :significant))
   (:type :hunter-spawn     :affect (:tense :anomalous))
   (:type :hot-swap-prompt  :affect (:anomalous))
   (:type :egress           :affect (:significant)))

Mode-Weight Biases

Per-beat additive deltas (clamped ±0.20 by the framework):

Beat	`observe`	`annotate`	`reflect`	`drift`	`silent`
`:active-hack`	+0.05	—	—	—	+0.05
`:high-tense`	—	−0.05	—	—	+0.10
`:phase-transition`	—	—	+0.05	—	—
`:cart-swap-lull`	—	—	+0.05	+0.10	—
`:debrief`	—	+0.05	+0.05	—	—

Rationale. ICE Breaker’s tempo is fast in :active-hack — the voice should observe and shut up, not editorialize. :high-tense tightens silence further so the trace rising without a voice line hits harder. :phase-transition and :cart-swap-lull push reflect/drift to make cross-cartridge memory stick around. :debrief leans into annotate+reflect — the Cipher earns its editorial after the run ends.

Style Deltas

((:active-hack    (:terseness +32 :certainty -16))
 (:high-tense     (:terseness +48 :certainty -32))
 (:cart-swap-lull (:temporal-blur +24))
 (:debrief        (:terseness -16 :certainty +24)))

Fast phases → clipped and uncertain. Debrief → slightly looser, more sure.

Structurally Important Moments Preserved on CIPHER-LINE

These are beats the main-grid spec currently narrates via Cipher lines. On CIPHER-LINE they become fragment pairs rendered across Rows 2–3:

Beat	Intent	CIPHER-LINE fragment(s)
Orient assist, low rep	”This node’s ICE is JUNK-class, slow. You can brute-force it or traverse.”	`junk. slow.` then `brute. or slip.` (two ticks, mode `observe` then `annotate`)
Orient assist, high rep	(silent — operator on their own)	`(silent tick)` for 3–5 ticks; operator sees Rows 2–3 freeze
Capability gap warning	”CAPABILITY GAP DETECTED — NETWORK DEPTH EXCEEDS CURRENT MODULE.”	`gap.` then `not this one.` (annotate, anomalous-tagged)
HUNTER spawn at trace=30	”PERIMETER ALERT ISSUED”	`perimeter. awake.` (annotate, tense)
Hot Swap initiation	”INITIATING CAPABILITY SWAP”	`swap.` then `hold.` (the nOSh runtime emits; cart-swap-lull)
Successful egress	”NETWORK COMPROMISED. DATA EXTRACTED. NO TRACE.”	`clean.` then `no trace.` (annotate + observe; significant)
Compromised egress	”EXTRACTED. BURNED.”	`got it. burned.` (annotate; tense + significant)

The intent is preserved; the surface and length change. No structurally important beat is dropped — every one still lands, it just lands on the OLED in fragments the operator catches in peripheral vision while they work the main grid.

nEmacs Contributions

Per ADR-0016 (nEmacs + REPL + Input Model), each cart declares what its scripted-mission surface looks like — grammar fragments contributed to the predictive palette, domain vocabulary that earns the +5 ranking boost (ADR-0016 §7), whether it uses prompt-text for raw text entry (§8), and whether any of its keys bind :double-tap or :long-press events (§9). The context-polymorphic dispatch model (§3) means ICE Breaker’s verbs on Row 24 are rendered by firmware from the cart’s own keymap — when the player is in an ICE Breaker run (not inside nEmacs/REPL), the keys mean exactly what ICE Breaker says they mean.

Scripted Missions?

Yes — scan-orchestration and loadout scripting. ICE Breaker is a tempo-driven cart but operators at Journeyman+ reputation may author pre-run scripts at the deck (Lisp snippets in nEmacs) that automate repetitive CONS combinations, pre-stage observational sweeps, or codify a hot-swap handoff routine. These are loadout-style scripts per the pre-run framing of ADR-0016’s narrative — the operator writes logic at the deck, deploys, watches it execute. Scripted missions remain fully optional on the critical path (ADR-0002); a low-rep operator can clear every contract without touching nEmacs. High-rep operators use scripts to raise their personal ceiling.

Typical scripted-mission shapes:

(orient-sweep) — chains observe, scan-class, trace-check primitives on node entry.
(cons-loadout :mirror :cloak) — pre-stages a capability combination so the operator only needs to hit EVAL at the right moment.
(on-hunter-spawn (egress-if-clean)) — reactive handler bound to the :hunter-spawn event.

Cart Grammar Fragments

Contributed via (emacs-extend-grammar ...) at cart-load. These forms become legal in :nemacs-nav scope when ICE Breaker is loaded, filtered into the palette by the ADR-0009 legal-form filter:

(emacs-extend-grammar
  (scan            (node))                      ; returns (:subject ... :class ...)
  (scan-class      (node))                      ; shorthand for (scan) | :class
  (trace-level)                                 ; returns current 0..100
  (cons-pair       (tool-a tool-b))             ; the CONS combination matrix
  (break-ice       (node tool))                 ; commits a crack; fires :ice-crack event
  (egress          (&optional :clean :burned))  ; terminates run
  (hunter-nearby?)                              ; boolean predicate
  (on-hunter-spawn (&body handler))             ; event binder
  (when-trace-above (level &body body))         ; conditional on trace
  (slip-to         (node)))                     ; graph traversal primitive

Vocabulary Contribution

Via (emacs-extend-vocabulary ...). Overlaps the CIPHER-LINE Contributions :memory-keyword pool but serves a different purpose: the CIPHER-LINE version seeds the voice; this one biases T9 prediction so when an operator types ic on the 2-key, ice ranks higher than icy:

(emacs-extend-vocabulary
  "ice" "trace" "handshake" "node" "relay" "sentry"
  "hunter" "perimeter" "junk" "black" "red" "kraken"
  "shadow" "mirror" "cloak" "crack" "slip" "cons"
  "compromise" "egress" "burned" "clean")

`prompt-text` FFI Usage

No. ICE Breaker has no raw text entry. All interaction is primitive-key orchestration — no handle-entry prompts mid-run, no typed commands. The cart declares nothing via prompt-text and ships without the Nokia multi-tap path.

Double-Tap and Long-Press Bindings

ICE Breaker opts into the ADR-0016 §9 event model on two keys:

Key	`:tap`	`:double-tap`	`:long-press`
`INFO`	`observe` — basic telemetry	`orient-assist` — Cipher narrates (low-rep) / silent (high-rep)	—
`CONS`	`open-combo-matrix`	—	`show-recent-combos` — surface last 3 successful pairings as a quick-pick
`CAR`	`descend` — enter node	`scan-deep` — scan then descend	—

All other ICE Breaker keys bind :tap only — tempo is fast and the operator benefits from deterministic single-press verbs; multi-level bindings are reserved for drill-down affordances where the second press is genuinely different work.

Row 24 action bar renders these per ADR-0016 §9: INFO:OBS INFO²:ORIENT CAR:ENTER CAR²:SCAN+ENTER CONS:COMBO CONS…:RECENT EVAL:COMMIT QUOTE:SWAP.

Context-Polymorphic Key Semantics (Cart Gameplay)

During an active ICE Breaker run (not nEmacs/REPL), keys resolve via the cart’s keymap as declared in its Lisp handlers. Row 24 reflects the current context; Row 0 remains firmware-owned status. Summary of verbs:

Key	Verb in ICE Breaker
`INFO`	OBSERVE (tap) / ORIENT (double-tap)
`CAR`	Enter/descend node (tap) / Scan+descend (double-tap)
`CDR`	Traverse back up
`CONS`	Open combination matrix (tap) / Recent combos (long-press)
`EVAL`	Commit action
`QUOTE`	Initiate Hot Swap
`BACK`	Return to network map
Numpad 1–6	Select listed option / node / tool

When the player exits the ICE Breaker run to nEmacs (via SYS → Edit), these semantics hand off to :nemacs-nav scope and cursor-polymorphic dispatch resumes — this is the ADR-0016 §3 boundary, and Row 24 flips to the editor’s action verbs automatically.