Skip to content

KN-86 DECKLINE: NeonGrid & Black Ledger Gameplay Specifications

Playtest Blueprints — Launch Title Modules

Version 1.0 | April 2026

Scope: combined design-round artifact. This document contains paired design for the NeonGrid and Black Ledger modules from an earlier design round. It is retained as a design-history reference for the paired-module (NeonGrid ↔ Black Ledger) campaign pattern. Part One (NeonGrid) is superseded by KN-86-NeonGrid-Gameplay-Spec.md v2.0 — cite that file for NeonGrid implementation. Part Two (Black Ledger) is superseded by KN-86-BlackLedger-Gameplay-Spec.md v1.0 (standalone, 2026-04) — cite that file for Black Ledger implementation. For the paired Corporate Espionage campaign archetype, this document remains the authoritative combined reference.

CIPHER-LINE revision note (2026-04-24): Any Cipher voice examples in this combined doc are rendered on the CIPHER-LINE OLED, not the main 80×25 grid. For current vocabulary pools, production fragments, and mode-weight biases, see the CIPHER-LINE Contributions sections in the standalone NeonGrid and Black Ledger specs listed above. Canonical engine spec: docs/software/runtime/cipher-voice.md.


PART ONE: NEONGRID — SPATIAL OPERATIONS MODULE

Section titled “PART ONE: NEONGRID — SPATIAL OPERATIONS MODULE”

NEONGRID is not a maze game. It is a navigation pedagogy—the operator’s first embodied experience with spatial reasoning on the Deckline, evolving from a structured learning tool into a persistent meditation practice and performance utility. The core loop is OBSERVE-LEARN-EXECUTE-VERIFY: observe a procedural grid, learn its topology and constraints, execute a movement plan without error, verify mastery through clean traversal. The operator’s skill grows not from speed (though speedrunning is available) but from the depth of their spatial intuition: can they hold a 10×10 grid topology in working memory? Can they predict sentry patrol patterns from audio alone? Can they move at pianist-tempo, every keystroke intentional, no corrections?

NEONGRID teaches the Lisp-inspired semantics of the KN-86 through play, not instruction. CAR/CDR become muscle memory. The numpad becomes an extension of spatial reasoning. By the end of the first hour, an operator who started with NEONGRID can navigate any Deckline interface because the foundational grammar is lived, not memorized.

But NEONGRID is not finished after onboarding. It persists as an operator’s perpetual gym. High-reputation ICE BREAKER operators return weekly to maintain precision. BLACK LEDGER auditors run NEONGRID FLOW STATE contracts to clear their minds before a 4-hour financial investigation. DEPTHCHARGE submersible pilots use NEONGRID’s sonar-equivalent grid view to mentally simulate underwater routing. NEONGRID is the common language all modules speak.


1. THE NAVIGATION LOOP: ATOMIC UNIT OF PLAY

Section titled “1. THE NAVIGATION LOOP: ATOMIC UNIT OF PLAY”

A single NEONGRID cycle is slower than ICE BREAKER’s OODA (5-15 seconds per decision rather than 0.5-2 seconds), but the loop structure is identical: OBSERVE-LEARN-EXECUTE-VERIFY.

OBSERVE (1-2s): The operator views the grid. The screen shows:

NEONGRID // LEVEL 3 — TRAINING MODE
TIME: 2:15 / 5:00 FLOW: +73% PROFICIENCY: +2
████████████████ ████████████████ ████████████████
█ . . █ █ . █ █ S . █
█ ████████████ █ ███████████ █ ███████████ █
█ . . █ █ . █ █ . █ █
████ ███████████████ █████████████████ ████████
█ . █ . █ . █ █
█ ███████████████████████████████████ █ █████ █
█ @ . . █ █ █
████████████████████████████████████████████████████
KEY: @ = You S = Sentry . = Checkpoint ░ = Wall
Checkpoints: 3 / 3 Next: NORTH Sentry Range: 4 cells Threat: LOW

The operator presses INFO to see raw sentry patrol patterns:

SENTRY PATROL (Info Overlay):
Sentry A: Node (8,5) → (8,12) → (8,5) [5-turn cycle]
Distance to Next Turn: 1 turn (path west)
Predicted position in 2 turns: (8,10)
Collision Risk: NONE (your path north is clear)

The operator has absorbed the spatial situation in 1-2 seconds. The grid is still. No time pressure yet in training mode. But in FLOW STATE contracts, every second of observation costs. Faster observation becomes a learned skill.

LEARN (1-3s): The operator interprets the grid. They now hold a mental model: “Sentry is on an east-west patrol at row 8. I am at (8,2). If I move north to row 7, then east, I will pass above the sentry’s path with 2 cells clearance. I can reach the next checkpoint (row 6, column 9) safely.”

This is the ORIENT phase of ICE BREAKER translated to spatial reasoning. The operator with high NEONGRID proficiency does this in 0.5 seconds (unconscious competence). A trainee takes 3 seconds (deliberate conscious processing).

EXECUTE (1-2s per keystroke): The operator makes a move. They press numpad 8 (NORTH). The screen updates:

█ @ . . █ █ █

becomes:

█ . @ . . █ █ █

One keystroke = one cell movement = one turn of world time. The sentry moves (west, 1 cell). The YM2149 plays a soft tom hit (operator keystroke), then a glissando rising tone (sentry movement acknowledged).

The operator has 0.5 seconds to decide the next move before the world cycles again (in FLOW STATE). In training mode, time is infinite. The operator can pause and think.

VERIFY (0.5s): The operator checks: is the result what they expected? Did the sentry move where predicted? Are they on track to the checkpoint? The YM2149’s Voice 2 pulses (confirmation tone). The operator’s proficiency register increments by 1 (invisible to them, but accumulating).

NEONGRID makes spatial reasoning audible and muscular. An operator cannot read a NEONGRID grid passively. They must move through it, embodying the topology. Over time, the screen becomes unnecessary—the operator navigates by audio alone (Voice 2 sentry glissando tells them sentry distance; Voice 1 hum tells them overall threat; silence tells them exploration is safe).

This is learning at the somatic level. By the time an operator has completed Wave 1 (20-30 hours), their hand knows the numpad like a pianist knows 88 keys. The grid is no longer a visual puzzle. It is a space they inhabit.

Reputation and proficiency diverge in NEONGRID. An operator can have Rep 0 (Apprentice in intrusion) but NEONGRID Proficiency 65 (Expert level navigation). Conversely, an experienced ICE BREAKER operative (Rep 35) might have NEONGRID Proficiency only 20 (they never finished Wave 1 training).


The grid is a procedurally generated maze-like topography. Unlike ICE BREAKER’s network (a directed graph of abstract nodes), the NEONGRID is a literal spatial field with walls, empty space, hazards, and sentry patrol routes.

The grid is seeded by contract parameters:

  • Wave (difficulty tier): 1-4 (defines maze complexity, sentry count, time limit)
  • Level within wave: 1-5 (procedurally varies maze generator parameters)
  • Grid dimensions: 16×10 base (smaller in Wave 1, up to 20×15 in Wave 4)
  • Wall density: 30-50% of cells are walls (maze-like corridors)
  • Checkpoint count: 3-5 goal positions the operator must visit (in sequence or any order, depends on contract type)
  • Sentry count: 1 in Wave 1, 2 in Wave 2, 3-4 in Wave 3, 4+ in Wave 4
  • Hazards: none in Wave 1, SPIKE (1 damage) in Wave 2, PLASMA (instant death) in Wave 3+

Each cell has state:

  • Passability: wall (impassable), empty (passable), hazard (passable but damaging)
  • Sentry occupancy: none, or occupied by sentry A/B/C/D
  • Checkpoint marker: none, or checkpoint number (1-5)
  • Visited flag: whether operator has stepped on this cell (for proficiency tracking)

Sentry Behavior: Predictable Patrol + Reactive Chase

Section titled “Sentry Behavior: Predictable Patrol + Reactive Chase”

Sentries are not random. They follow deterministic patrol routes that repeat every N turns. A sentry’s patrol is chosen at grid generation time and is immutable during the run.

Patrol Patterns (Examples):

  • Linear Patrol: East (5 cells) → West (5 cells) → repeat. 10-turn cycle.
  • Rectangular Patrol: Move around perimeter of a 4×4 area. 8-turn cycle.
  • Lawnmower Patrol: Scan a region row-by-row, then column-by-column. 16-turn cycle.

Sentry movement is tempo-locked to the operator’s movement. Every turn, one of the following happens:

  1. Operator presses a numpad key (move forward 1 cell).
  2. Operator presses ENTER or 5 (wait, skip turn).
  3. Operator presses INFO (observe, no turn consumed in training mode; turn consumed in FLOW STATE).

After the operator’s action, the sentry moves 1 cell along its patrol. If the sentry’s new position overlaps the operator’s position, collision. The operator takes damage (loses 1 HP) or dies (HP=0 → run ends).

Chase Mode (Wave 2+): If the operator comes within 4 cells of a sentry’s patrol route, the sentry enters Chase Mode. Instead of following its patrol, it pursues the operator directly (aiming toward the operator’s cell). Chase mode lasts until the operator moves 6+ cells away (the sentry “forgets” them).

Sentry Communication (Wave 3+): Sentries can detect each other’s alerts. If Sentry A is chasing, Sentry B on the patrol will modify its route to intercept (moving toward Sentry A’s position, creating a “pincer” trap). This creates emergent danger: the operator is not just avoiding individual sentries but encountering coordinated patrol networks.

The operator cannot see sentries beyond a 5-cell radius (in GRID VIEW). Sentries are visible only if:

  1. They are on the same row or column as the operator (line of sight).
  2. The operator presses INFO to activate sonar (temporarily reveals all sentries on grid, costs 1 turn in FLOW STATE).
  3. The operator has high NEONGRID proficiency (70+) where sentries are always visible.

The Learning Curve is Built In: Early operators move cautiously (can’t see sentries, so they assume danger everywhere). Expert operators press INFO once, memorize all sentry paths, then navigate perfectly. The proficiency system rewards this compression of observation into prediction.

This is subtle and critical. The grid is not random. It is seeded by the operator’s cartridge history bitfield. If the operator has loaded BLACK LEDGER, the maze includes more “vertical” corridors (like financial account hierarchies). If they’ve loaded DEPTHCHARGE, the maze includes more “branching paths” (like underwater navigation options).

Additionally, if the operator has played a Level N before (same seed), the maze on replay is identical. But the operator’s proficiency with it is higher. A grid that took 5 minutes on first play takes 3 minutes on replay, not because the grid changed, but because the operator learned its topology.

This is not a failure; it’s intentional. NEONGRID is designed for repeated runs of the same levels. Operators memorize layouts. They test their muscle memory against their own prior attempts. Leaderboards rank operators by how fast they can clear Level 3 on their 10th attempt (proving mastery, not luck).


Navigation in NEONGRID uses the numpad as cardinal directions (absolute, not relative):

  • Numpad 8: NORTH (row -1)
  • Numpad 2: SOUTH (row +1)
  • Numpad 4: WEST (col -1)
  • Numpad 6: EAST (col +1)
  • Numpad 5 or ENTER: WAIT (skip turn, world still advances)

This is intentionally NOT relative directional input. The operator cannot “turn” the character. The grid is absolute. This creates a different skill: the operator must mentally rotate the grid in their head, visualizing “NORTH” from any direction. This is harder and deeper than relative input.

Advanced Input (Proficiency 50+): Diagonal movement becomes available (unlocked after mastering cardinal directions). Numpad 7 (NW), 9 (NE), 1 (SW), 3 (SE). Each diagonal costs 1.5 turns (more expensive, but opens new route options).

Macro Recording (LAMBDA key): An operator can press LAMBDA and record a sequence of button presses (up to 20). The sequence is stored. The operator can then press APPLY to replay the sequence automatically, cell-by-cell. This is used for speedrunning (pre-plan the optimal path, record it, replay perfectly on timed runs) and for proving mastery (record a flawless run, submit to leaderboard).

The Deckline has 31 keys. NEONGRID uses only 6 (4 directions + 5/ENTER + shift keys). This is radical minimalism. It teaches the operator: the interface can be sparse and still be complete. The numpad feels like an arcade joystick (analog-style input on a digital grid). The muscle memory is immediate.

Operators who start with NEONGRID and then move to ICE BREAKER are already comfortable with the Deckline’s grammar. CAR/CDR feel natural because the operator has spent 10 hours navigating space with CAR (enter) and CDR (next).


4. SYSTEM THREE: THE CHECKPOINT ARCHITECTURE

Section titled “4. SYSTEM THREE: THE CHECKPOINT ARCHITECTURE”

Checkpoints are the goal positions. A contract may require:

  1. Sequential Traversal: Visit checkpoints in order (1 → 2 → 3) before exiting.
  2. Any Order: Visit all checkpoints in any order before exiting.
  3. Targeted Checkpoint: Reach a specific checkpoint (revealed after reaching intermediate ones).
  4. Flow State: No explicit checkpoints; just survive 5 minutes without touching a sentry.

Each checkpoint is marked on the grid with a * symbol and a number. Walking into a checkpoint cell triggers an audio confirmation (rising major arpeggio, 300ms) and advances the checkpoint counter.

Checkpoint Psychology: The checkpoint exists partly for navigation practice (the operator must plan a safe route to each one) and partly for progression feedback (audible + visual confirmation that they’re succeeding). A run with checkpoints is structured success. A FLOW STATE run with no checkpoints is pure survival. Different psychological tonalities.

Once all checkpoints are visited, an EXIT PORTAL appears at a random location on the grid. The operator must navigate to it and enter (walk into the portal cell). This final traversal is often the hardest because:

  1. The operator must find the portal (fog of war means they can’t see it until nearby).
  2. Sentry patrol routes may have shifted (in Wave 3+ with coordinated AI).
  3. Tension is high (the operator can see the exit is near, but not quite reachable).

Reaching the exit and walking into the portal cell triggers a major-key resolution chord and the level-clear screen.


The YM2149 is the operator’s spatial compass in NEONGRID.

Voice 1 (Ambient Threat Hum): A continuous sine wave tone that encodes overall threat level:

  • Grid quiet, no nearby sentries: C3 (55Hz), barely audible hum
  • One sentry within 6 cells: G3 (98Hz), noticeable hum
  • Two sentries nearby: D4 (147Hz), present but not alarming
  • Sentry in chase mode (within 4 cells): G4 (196Hz), sharp and present
  • Multiple sentries closing in: D5 (294Hz), alarming pitch

The operator learns to navigate by ear. A high-pitch hum means a sentry is near; they should freeze or retreat. Silence means safe exploration.

Voice 2 (Sentry Tracking): A glissando (pitch bend) that plays every time a sentry moves:

  • Sentry moving toward operator: rising glissando (0-500ms, pitch accelerates upward)
  • Sentry moving away: falling glissando (0-500ms, pitch descends)
  • Sentry turning (changing direction): stationary tone (100ms, single note, no bend)

An expert operator can navigate with eyes closed, using only Voice 2 to track sentry movements. The glissando direction tells them if a sentry is approaching or retreating. The tone pitch (high = close, low = far) tells them distance.

Voice 3 (Environmental): Feedback and milestone sounds:

  • Checkpoint reached: Rising major arpeggio (C4-E4-G4, 300ms)
  • Portal spawned: Sharp resonant tone (all three voices spike simultaneously, 200ms)
  • Hazard proximity: Harsh buzz (200Hz + noise, indicating SPIKE or PLASMA nearby)
  • Collision imminent: Discordant cluster (multiple tones 50Hz apart, warning)
  • Collision: Sharp descending glissando + noise burst (failure tone)
  • Clear level: Major key resolution (C major chord progression, 1 second, triumphant)

A NEONGRID operator with Proficiency 75+ can run a Level in audio-only mode (screen turned off, wearing headphones, pure somatic navigation). This is not a gimmick—it’s a legitimate mastery metric. The operator who can navigate a 15×10 maze with 3 sentries using only YM2149 audio cues has achieved true spatial internalization.

This is accessible design accidentally enabling advanced play. Blind operators can fully participate in NEONGRID (audio-only mode is native). Hearing operators can choose to restrict themselves to audio as a skill challenge (like speed-running, but for pattern recognition).


Four systems collide in NEONGRID: the static maze, the sentry patrol network, the operator’s spatial model, and the audio feedback loop. The collisions are designed moments of learning.

An operator thinks they understand a sentry’s patrol cycle. “East 5 cells, then west 5 cells, repeat.” They have a 3-second window to slip past.

But they miscounted. The sentry’s cycle is 9 cells, not 10. The operator moves into the corridor, expecting the sentry to be 2 cells away.

The sentry is 1 cell away. Collision. Operator takes damage (or dies, depending on HP).

This is not a design failure. This is teaching precision. The operator has learned: observation must be meticulous. A miscounting error is a physical consequence (damage). On the next run of the same level, the operator counts more carefully.

The Sentry Communication Surprise (Wave 3+)

Section titled “The Sentry Communication Surprise (Wave 3+)”

An operator successfully evades Sentry A, moving along the western corridor. They are safe. The audio confirms it: Voice 1 hum drops to C3 (threat gone).

But Sentry B, who detected Sentry A’s alert, has moved to intercept. The operator rounds a corner and walks into Sentry B.

This is an emergent collision: two systems (Sentry A’s chase, Sentry B’s communication) interacted in a way the designer scripted, but the operator didn’t predict. The operator has learned: sentries are networked. Evading one doesn’t mean evading all.

On future runs, the operator assumes communication and plans accordingly (move faster, use more distant routes).

An operator at Proficiency 20 tries a Level that requires Proficiency 40. The grid logic is identical, but the difficulty is tuned differently:

  • Wall density is higher (narrow corridors, hard to navigate).
  • Sentry patrol cycles are longer (harder to predict).
  • Checkpoint spacing is greater (longer planning horizon).

The operator fails. They can’t “brute force” their way through like they could in earlier levels. They learn: proficiency is not a decoration—it’s a genuine skill bottleneck.

On later sessions, they train more deliberately (running CALIBRATION contracts to increase proficiency) before attempting harder levels.

An operator has learned that a rising glissando = sentry approaching. But in a specific scenario, they misinterpret:

Sentry A is approaching from the south (rising glissando). Simultaneously, Sentry B is moving away to the north (falling glissando). The two tones overlap. The operator hears “complex pitch motion” and freezes, assuming danger.

In fact, Sentry B’s path diverges and is no threat. Sentry A will pass 2 cells away. The operator was safe, but they over-interpreted the audio.

This teaches: sound is information, not certainty. The operator must cross-reference audio against visual (if they’re using the screen) or develop more nuanced listening (if audio-only).


Every NEONGRID session has a natural shape. The shape depends on which Wave is being played and the operator’s proficiency.

An operator with Proficiency 0 (Apprentice) takes a Wave 1 Level 1 contract.

Minutes 0-1: Disorientation. The operator views the grid and is confused. The maze is complex, sentries are visible, the checkpoint path is unclear. They press INFO. Cipher voice explains: “The grid shows your position (@), sentry routes (S), and checkpoints (*). Navigate safely to each checkpoint, then reach the exit portal.”

The operator moves slowly, pressing numpad 8 (north). The screen updates. They move again. They check the position of the sentry (still far away). Slow, deliberate movement.

Minutes 1-4: Learning. The operator reaches the first checkpoint. Audio feedback (rising arpeggio) confirms success. They see the pattern: move carefully, watch the sentry, reach checkpoint, repeat.

They navigate to checkpoint 2 and 3, moving faster as confidence builds. The YM2149’s Voice 1 hum becomes familiar. Sentry movements are predictable.

Minutes 4-8: Execution. The operator moves with purpose. They no longer second-guess. The portal spawns. They navigate to it and press ENTER.

Proficiency increments: +8 (for clean completion). Reputation: +1 (training completed).

Minutes 8-10: Reflection. The level-clear screen shows statistics:

LEVEL COMPLETE: Introduction Maze
────────────────────────────────────────
Traversal Efficiency: 73% (some inefficient moves)
Sentry Encounters: 0 (perfect evasion)
Time Taken: 7m 45s
Proficiency Gain: +8
Reputation Gain: +1
────────────────────────────────────────
Next Level: Level 2 (slightly harder maze)

The operator feels competent. They did it. They’re ready for the next level.

Total time: 10 minutes. The operator is not exhausted. They’re energized.

The 20-Minute Specialist Wave 3 Endurance Run

Section titled “The 20-Minute Specialist Wave 3 Endurance Run”

An operator with Proficiency 65 (Expert) takes a Wave 3 Level 4 contract.

Minutes 0-1: Rapid Assessment. The operator views the grid. They don’t see the full maze—only immediate surroundings (fog of war). But they press INFO once to get a full sentry position dump. Sentry A is at (12,5), Sentry B at (8,9), Sentry C at (3,7). They’re coordinating in a pincer formation toward checkpoint 2.

The operator decides: approach checkpoint 1 first (different route), then navigate carefully around the coordinated sentries.

Minutes 1-5: Strategic Execution. The operator moves efficiently. They read the sentry movements (Voice 2 glissandos) and predict accurately. They don’t need to see the grid; they navigate by audio, occasionally glancing at the screen to confirm.

They reach checkpoint 1 in 4 turns (optimal). Audio reward. Checkpoint 2 is risky (sentries coordinating). They take a longer, safer route (7 extra turns, but zero collision risk).

Checkpoint 2 reached. Checkpoint 3 requires cutting through the heart of sentry activity. The operator has 30 seconds of setup time.

Minutes 5-10: Tempo Challenge. Sentries are moving, coordinating. The operator activates FLOW MODE (a mental state, not a cartridge state—they’re cycling OODA at maximum conscious speed). They move with intention. Every keystroke is calculated.

They slip past Sentry C with 1 cell clearance. Voice 1 alarm rises to G4 (danger). They accelerate. Checkpoint 3 is 3 moves away.

They reach it. Audio major arpeggio. Portal spawns across the maze, far away, requiring 12 more moves through dangerous territory.

Minutes 10-15: Final Challenge. The operator pushes toward the portal. Sentry A and B are repositioning. The audio hums with threat. The operator navigates fast but safely (high proficiency = can move fast without errors).

They reach the portal. Walk in. Clear!

Proficiency: +15 (wave 3 bonus for expert). Reputation: +2 (multi-sentry evasion).

Minutes 15-20: Reflection and Choice. The operator could continue to Level 5 (final Level of Wave 3). They’re energized. They take it.

Total time: 20 minutes (two levels, increasing difficulty). The operator is satisfied. They advanced two levels in one session. Their expertise is validated.

An operator attempts a Wave 3 Level 3 and dies at the final checkpoint (miscalculates a sentry patrol, takes damage, HP=0).

Failed run. No proficiency gain from completion. But there’s a hidden proficiency +2 for reaching the 60% waypoint (a partial-progress bonus). The operator didn’t waste the attempt—they learned something (the sentry patrol mechanics, the specific maze layout).

On the next run, they pass the 60% waypoint at 45% of the clock (faster learning). On the third run, they complete it.

Each failure is a session that invested in mastery, even though it didn’t yield completion rewards.


There is no tutorial. NEONGRID is the tutorial.

The operator powers on. The nOSh runtime loads. The mission board appears:

MISSION BOARD — Available Contracts
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
CONTRACT 1: CALIBRATION [NEW]
Duration: 2 minutes Rep Gain: +0.5 Description: Test NORTH movement
CONTRACT 2: INTRODUCTION MAZE [NEW]
Duration: 10 minutes Rep Gain: +1 Description: Navigate to 3 checkpoints
CONTRACT 3: ARCADE SPEEDRUN [LOCKED]
(Unlock after Intro Maze)

The operator selects CONTRACT 1 (by curiosity or default).

The screen shows:

NEONGRID // CALIBRATION — NORTH MOVEMENT
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
You are positioned in a small grid. Press NUMPAD 8 to move NORTH.
█████
█ . █
█ @ █
█████
Cipher Voice: "The grid shows walls (█) and empty space.
You (@) must reach the checkpoint (.).
Press 8 on the numpad to move NORTH."
Waiting for input...

The operator presses 8. The grid updates:

█████
█ @ █
█ . █
█████

Wait, that’s wrong. The operator moved south, not north. But the contract says “move north.”

Hmm. Actually, the contract is testing whether the operator understands: in NEONGRID, the grid is absolute. NORTH is up on the screen (visually). The operator moved up. The checkpoint moved down (or the operator moved away from it).

Cipher voice: “You moved NORTH (up the screen). The checkpoint is SOUTH. Move NORTH again and leave the grid area.”

The operator presses 8 again. They exit the grid area (move past the top boundary).

█████
█ █ <- operator has exited
█ . █
█████
Cipher Voice: "Clear. You have learned NORTH."
Proficiency: +1

The operator is now ready for CONTRACT 2. They have embodied the numpad without instruction. The learning happened through interaction.

The operator sees a small maze (6×6):

NEONGRID // INTRODUCTION MAZE
━━━━━━━━━━━━━━━━━━━━━━━━━━━
████████████
█ * █ █ @ █
█ ███████ █
█ . █ █
███████ ██ ██
█ . █ █
█ ██████ ██ █
└──────────┘
Checkpoints: 1/3 found
Time: 1:00 / 5:00
Threat: NONE (no sentries in intro)
Cipher Voice: "Navigate to all checkpoints (*), then escape.
No threats yet. Take your time."

The operator has no time pressure. They navigate by trial and error, learning the maze. They reach the first checkpoint (audio reward). The second checkpoint is behind a complex path—they have to explore.

No sentry yet. No collision risk. Pure navigation practice. After 5 minutes, they clear the maze.

Proficiency: +3 (basic maze navigation). Reputation: +1 (training completed).

The operator has now completed the core NEONGRID onboarding. They understand:

  1. Numpad controls direction absolutely (NORTH is always up).
  2. INFO gives tactical information.
  3. Checkpoints are goals.
  4. Audio confirms progress.
  5. Grids can be complex but navigable with planning.

9. PROFICIENCY SYSTEM: THE HIDDEN DEPTH METRIC

Section titled “9. PROFICIENCY SYSTEM: THE HIDDEN DEPTH METRIC”

NEONGRID introduces a Proficiency Stat that is invisible to the operator but affects all Deckline modules.

Proficiency is the operator’s hand-eye-ear coordination, spatial reasoning depth, pattern recognition speed, and decision-making confidence under time pressure.

It is measured in 0-100. It starts at 0 and increases through play:

ActionProficiency Gain
Complete CALIBRATION+1
Complete TRAINING contract+2-3
Complete FLOW STATE (5 min error-free)+5
Speedrun a level (finish in <50% time)+3
Reach level without sentry encounters+1
Complete wave 2+ level without damage+2
Navigate audio-only mode (screen off)+3

Proficiency does not increase during failures, but partial progress gives +1 (mercy bonus for effort).

In ICE BREAKER:

  • Proficiency 0-20: All network ciphers are +1 grade harder. Threat levels feel artificially high.
  • Proficiency 21-40: Baseline. No modifier.
  • Proficiency 41-60: All ciphers -1 grade. Network navigation feels smoother.
  • Proficiency 61-80: Ciphers -1 grade, exclusive high-rep contracts unlock.
  • Proficiency 81-100: Ciphers -2 grades, threat levels feel -1, “Master Operator” contracts unlock.

In BLACK LEDGER:

  • Proficiency 0-20: Account tree navigation is slower. Delays on CDR inputs.
  • Proficiency 21-40: Baseline.
  • Proficiency 41-60: Account tree navigation 20% faster.
  • Proficiency 61-80: Pattern recognition in anomaly detection is enhanced (Cipher voice hints improve).
  • Proficiency 81-100: “Forensic Master” contracts unlock (billion-dollar conspiracies).

In DEPTHCHARGE:

  • Proficiency affects drone positioning speed and sonar signal interpretation.
  • Proficiency 60+ unlocks “Ghost Mode” (submersible can navigate while hidden).

In NEONGRID itself:

  • Proficiency affects difficulty scaling (higher proficiency = harder challenges unlock).
  • Proficiency affects reward multipliers (higher proficiency earns more credits per contract).

Proficiency is a metagame metric. It rewards players who commit to learning the Deckline’s spatial-motor grammar, not just winning individual contracts. An operator who spends 30 hours in NEONGRID becomes a better operator everywhere.

This is intentional design: invest in fundamentals, reap cross-module benefits.

An operator who skips NEONGRID and goes straight to ICE BREAKER will struggle (all ciphers are harder). They’ll eventually develop proficiency through ICE BREAKER play, but slowly. An operator who disciplines themselves to complete Wave 1 in NEONGRID first develops proficiency faster and plays all modules more skillfully.


10. LINKED PLAY: SPECTATOR AND VERSUS MODES

Section titled “10. LINKED PLAY: SPECTATOR AND VERSUS MODES”

NEONGRID supports asymmetric multi-player.

Two operators connect via TRRS cable. Operator A plays a NEONGRID level. Operator B watches on a secondary Deckline (read-only, no input).

Operator B can see Operator A’s grid in real-time. They see the same threats, same sentry positions. They cannot intervene, but they can coach verbally (real-world communication).

This is useful for:

  • Teaching (veteran showing novice how to navigate a specific level).
  • Training (two operators competing mentally—who can predict the optimal path?).
  • Accessibility (operator with visual impairment can still play if a sighted partner relays grid state verbally).

Two operators play identical maze layouts simultaneously, on separate Decklines. Timer runs. Final score: who reached the portal faster?

The mazes are synchronized (same topology, same sentry patrol patterns). The only variable is operator skill and decision-making.

High-score leaderboard: fastest clear times on each level, attributed to named operators. Bragging rights.


╔════════════════════════════════════════════════════════════════════════════════╗
║ NEONGRID // WAVE SELECTION PROFICIENCY: 42 REPUTATION: 5 ║
╠════════════════════════════════════════════════════════════════════════════════╣
║ ║
║ TRAINING WAVES: ║
║ ║
║ WAVE 1: INTRODUCTION [ACTIVE] ║
║ Level 1 ✓ (11pts) Level 2 ✓ (14pts) Level 3 ✓ (16pts) ║
║ Level 4 ✓ (18pts) Level 5 ✓ (20pts) WAVE BONUS: 20pts ║
║ Your Best: 20:34 (Level 5) | Campaign Score: 99 points ║
║ ║
║ WAVE 2: COORDINATION [AVAILABLE] ║
║ Level 1 ○ (15pts) Level 2 ○ (18pts) Level 3 ? (20pts) ║
║ Level 4 ? (22pts) Level 5 ? (24pts) WAVE BONUS: 30pts ║
║ Unlock: Complete all Wave 1 levels [UNLOCKED!] ║
║ ║
║ WAVE 3: CHAOS [LOCKED] ║
║ Unlock: Reach Proficiency 60 [28/60 progress] ║
║ ║
║ WAVE 4: ENDLESS [LOCKED] ║
║ Unlock: Complete Wave 3 ║
║ ║
║ CAR to select wave │ CDR to browse │ SYS-hold to main menu ║
╚════════════════════════════════════════════════════════════════════════════════╝
╔════════════════════════════════════════════════════════════════════════════════╗
║ NEONGRID // WAVE 2 LEVEL 2 TIME: 1:24 / 3:00 SCORE: 52 pts ║
╠════════════════════════════════════════════════════════════════════════════════╣
║ ║
║ ████████████████ ████████████████ ████████████████ ████████████████ ║
║ █ 1 . █ █ 2 █ █ █ █ . █ ║
║ █ ███████████████████████████ █ █ █████████████████████████ █ ║
║ █ █ . █ █ █ . █ █ █ ║
║ █ █ ███████████████████████████ █████ █████████ ████████ █ █ ║
║ █ █ █ @ █ █ █ █ █ █ ║
║ █ █ █ ██████████ █████████████ █ ██████████████ ███████████ █ ║
║ █ █ █ █ █ █ 3 █ █ █ ║
║ █ █ █ ███████████████████████████████████████ █ █████████████████ ║
║ █ █ S1 S2 █ █ █ ║
║ ████████████ ████████████████████████████████████████████████████████ ║
║ ║
║ KEY: @ = You . = Checkpoint S = Sentry █ = Wall ░ = Hazard ║
║ Checkpoints: 1/3 found Threat Level: MEDIUM Sentry Status: 2 Active ║
║ Sentry 1: Patrol [patrol] Sentry 2: Chase Mode (3 cells away) ║
║ ║
║ Numpad (8/2/4/6) to move │ 5 to wait │ INFO for sentry details │ ENTER ║
╚════════════════════════════════════════════════════════════════════════════════╝
╔════════════════════════════════════════════════════════════════════════════════╗
║ NEONGRID // SENTRY TRACKING OVERLAY ║
╠════════════════════════════════════════════════════════════════════════════════╣
║ ║
║ SENTRY ANALYSIS: ║
║ ║
║ Sentry 1 (position 9,8): ║
║ Current Patrol: LAWNMOWER (scanning rows) ║
║ Pattern Cycle: 12 turns (8 turns remaining) ║
║ Predicted Position in 2 turns: (9,6) [moving north] ║
║ Distance from You: 5 cells ║
║ Collision Risk in 3 turns: SAFE (patrol moves away) ║
║ ║
║ Sentry 2 (position 4,3): ║
║ Current Mode: CHASE (pursuing detected threat) ║
║ Direction: SOUTHEAST (toward last observed position) ║
║ Distance from You: 4 cells ║
║ Collision Risk in 2 turns: MODERATE (may change trajectory) ║
║ Chase Termination: 4 more turns if you evade ║
║ ║
║ RECOMMENDATION: Move NORTH now (2 turns), then EAST. Sentry 1 clears path. ║
║ Sentry 2 will overshoot. Safe corridor opens in 3 turns. ║
║ ║
║ BACK to hide overlay │ CAR to highlight recommendation │ SYS for menu ║
╚════════════════════════════════════════════════════════════════════════════════╝
╔════════════════════════════════════════════════════════════════════════════════╗
║ NEONGRID // SETTINGS & PROFICIENCY ║
╠════════════════════════════════════════════════════════════════════════════════╣
║ ║
║ Your Proficiency: 42 / 100 [████████░░░░░░░░░░░░░░░░░░░░░░░░░] ║
║ ║
║ EFFECT ON OTHER MODULES: ║
║ ✓ ICE Breaker: All ciphers -0 grades (you are at baseline proficiency) ║
║ ✓ Black Ledger: Account navigation +0% (at baseline) ║
║ • Depthcharge: Not yet loaded ║
║ ║
║ AUDIO FEEDBACK: ║
║ [ ] Mute Voice 1 (Threat Hum) ║
║ [ ] Mute Voice 2 (Sentry Tracking) ║
║ [ ] Mute Voice 3 (Feedback Tones) ║
║ [✓] Audio-Only Mode (hide grid, navigate by ear alone) ║
║ ║
║ Next Proficiency Milestone: 60 (unlocks Wave 3 Chaos) ║
║ Estimated completion: 8-10 more hours of play ║
║ ║
║ CAR to toggle settings │ BACK to close │ SYS for menu ║
╚════════════════════════════════════════════════════════════════════════════════╝


PART TWO: BLACK LEDGER — FORENSIC AUDIT MODULE

Section titled “PART TWO: BLACK LEDGER — FORENSIC AUDIT MODULE”

BLACK LEDGER is not an accounting simulation. It is an investigative deduction engine—the operator’s first experience with lateral thinking on the Deckline, evolving from structured pattern-recognition contracts into full forensic conspiracy-solving. The core loop is SCAN-ASSESS-TRACE-EXPOSE: scan a financial ledger, assess which transactions are suspicious, trace money through shell accounts, expose the conspiracy by linking evidence.

Unlike NEONGRID’s embodied, somatic learning, BLACK LEDGER demands abstract cognitive reasoning. The operator must hold a complex financial hierarchy in working memory, cross-reference amounts and dates, infer deleted transactions from contextual clues, and build theories that connect disparate facts.

BLACK LEDGER teaches the operator to see patterns in numbers. It respects the operator’s intelligence—there are no hints, no hand-holding. Contracts are presented as raw data. The operator must extract meaning.

But BLACK LEDGER is not purely analytical. It has a story layer. Each contract represents a real corporate conspiracy (fictional, but grounded in real money-laundering tactics). The operator is a detective solving a mystery. The satisfaction is not “I found the right answer” but “I uncovered a $2.3M fraud scheme that no one else noticed.”


1. THE INVESTIGATION LOOP: ATOMIC UNIT OF PLAY

Section titled “1. THE INVESTIGATION LOOP: ATOMIC UNIT OF PLAY”

A single BLACK LEDGER cycle is slow—measured in minutes, not seconds. But the loop structure parallels ICE BREAKER’s OODA:

SCAN → ASSESS → TRACE → EXPOSE (and repeat, deepening each cycle).

SCAN (2-5 minutes): The operator views the ledger. The screen shows:

BLACK LEDGER // AUDIT: ZENITH INDUSTRIES
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
Time Remaining: 34:15 / 45:00
ACCOUNT HIERARCHY:
Zenith Industries (Holding Company)
├─ Zenith Pacific Division
│ └─ Q1 Revenue: $8.2M
│ └─ Q2 Revenue: $7.9M
│ └─ Quarterly Outflows: $1.2M (standard operating expenses)
├─ Nexus Holdings (Shell Company)
│ └─ Q1 Balance: $2.1M
│ └─ Q2 Balance: $1.8M
│ └─ Unusual Transfer: $2.0M to Caribbean Trust [FLAGGED?]
└─ Venerus Consulting (Front Company)
└─ Q1 Revenue: $0.3M
└─ Invoice Pattern: High variance (some invoices $50K, others $5K)
CIPHER VOICE: "You are auditing Zenith Industries.
Your task: identify transactions that deviate from legitimate business operations.
Use CDR to scroll through accounts. CAR to drill into details.
QUOTE to flag suspicious items. Submit when complete."
[More details visible via CAR / CDR navigation]

The operator is surveying the landscape. They are not yet committing to investigation paths. They’re getting a feel for the corporate structure and spotting obvious anomalies (e.g., $2.0M to Caribbean Trust stands out as unusual).

ASSESS (3-8 minutes): The operator begins drilling into specific accounts. They press CAR to enter an account:

NEXUS HOLDINGS — ACCOUNT DETAIL
═════════════════════════════════════════════════════════════
Account Type: Shell Company (registered in Delaware, beneficial owner unknown)
Account Status: Active
Q1 Balance: $2.1M
Q2 Balance: $1.8M
Quarterly Change: -$300K (withdrawn to Caribbean Trust)
TRANSACTION HISTORY:
Date: 2088-01-15 From: Zenith Industries Amount: $500K [LEGITIMATE?]
Date: 2088-02-03 From: Zenith Industries Amount: $1.5M [LARGE_TRANSFER]
Date: 2088-03-10 To: Caribbean Trust Amount: $2.0M [SUSPECT!]
Date: 2088-03-12 From: Zenith Industries Amount: $300K [normal]
[Use CDR to scroll. Use QUOTE to flag.]

Now the operator is assessing. They see a pattern:

  1. Zenith Industries is pumping large sums into Nexus Holdings.
  2. Nexus is immediately shunting the money to Caribbean Trust (a jurisdiction famous for money laundering).
  3. The timing is suspicious (the $2.0M transfer happens right after a large inflow).

The operator presses QUOTE (the bookmark key) to flag the $2.0M transfer as suspicious. The transaction is marked.

TRACE (5-15 minutes): The operator has identified a suspicious money flow. Now they must follow it. They press CAR to follow the $2.0M transfer into Caribbean Trust:

CARIBBEAN TRUST ACCOUNT — MONEY TRAIL
═════════════════════════════════════════════════════════════
Received from: Nexus Holdings
Amount: $2.0M (incoming on 2088-03-10)
Balance after: $2.0M
Outflow Sequence:
Date: 2088-03-15 To: Cayman Finance Corp Amount: $1.95M [5% fee charged]
Date: 2088-03-20 Received: Inter-Trust Exchange Fee Amount: $50K [reverse flow!]
[Continue tracing via CAR to Cayman Finance Corp...]

The operator is now following money through the shell network. Each account reveals the next leg of the money trail. The operator is building a mental map of the transaction sequence.

They press CAR to drill into Cayman Finance Corp and find that the $1.95M is transferred again to “Handler LLC” (the final destination). The money has been laundered through three shells.

EXPOSE (2-5 minutes): The operator has traced the full money trail. They now understand: $2.0M from Zenith Industries → Nexus Holdings → Caribbean Trust → Cayman Finance Corp → Handler LLC. Along the way, 5% fees were “shaved” (actually kept by the intermediaries as payment for laundering services).

The operator uses CONS (the combination key) to link all the flagged transactions into a “theory” or “evidence chain.” The chain represents the complete money laundering operation.

When ready, the operator presses EVAL to submit their findings. The judge (a persona in the nOSh runtime) evaluates the operator’s flagged transactions:

AUDIT VERDICT
═════════════════════════════════════════════════════════════
CASE: Zenith Industries Audit
YOUR FINDINGS: 4 suspicious transactions flagged
Judge Evaluation:
✓ $2.0M Nexus → Caribbean Transfer [CORRECT - money laundering]
✓ $1.95M Caribbean → Cayman Transfer [CORRECT - continuation]
✓ Caribbean Fee Income [CORRECT - kickback]
○ $300K Zenith → Nexus [INCORRECT - this was standard quarterly top-up]
[You incorrectly flagged a legitimate transaction]
VERDICT: PARTIAL SUCCESS
Guilty Transactions Found: 3 / 4
False Flags: 1 (cost: -50 points)
Time Bonus: (12:43 remaining / 45:00) = +28%
FINAL SCORE: (500 base + 300 for 3 correct) × (1.0 - 1/9) × 1.28 = 893 points
REPUTATION GAIN: +2
CREDITS GAINED: 893 ¤

The operator has solved the case. They identified the money laundering scheme (success), but made one false accusation (a learning moment). The reward is substantial, but not perfect.


The ledger is a tree structure of financial accounts. Unlike ICE BREAKER’s network graph, it is strictly hierarchical: parent accounts contain child accounts. Money flows downward (or sometimes sideways, through transfers between accounts).

Each ledger is generated at contract creation time:

  • Contract type: AUDIT, RECONSTRUCTION, FORENSIC TRACE, SHELL MAPPING
  • Corporate structure: 5-15 accounts arranged hierarchically
  • Money sources: Where the dirty money enters (usually a legitimate-looking parent company)
  • Money destinations: Where the money exits (offshore accounts, handler accounts)
  • Transaction count: 20-80 transactions total
  • Red herring rate: 40-80% of transactions are legitimate, mixed with suspicious ones

Each account has state:

  • Account name: e.g., “Zenith Industries,” “Nexus Holdings,” “Caribbean Trust”
  • Account type: Holding Company, Subsidiary, Shell, Offshore, Front Company
  • Balance: Current account balance
  • Transaction history: List of transfers in/out
  • Parent account: The account this one reports to (if any)
  • Child accounts: Sub-accounts (if any)

Each transaction has state:

  • Date: When the transfer occurred
  • Amount: How much money moved
  • Source account: Where the money came from
  • Destination account: Where the money went
  • Description: A brief label (invoice, “quarterly top-up,” “service fee,” etc.)
  • Suspicious flag: Hidden to the operator, but the “judge” knows the ground truth

A critical design choice: the operator does not see the full ledger at once. They must navigate accounts one at a time, building a mental map of the structure.

Additionally, some transactions are deleted from the visible log (simulating account cleanup by someone trying to hide). The operator must reconstruct these deleted transactions from contextual clues:

  • Account balance deltas (if an account had $1M on Day 1 and $800K on Day 5, and only one visible transaction is $150K out, then $50K is unaccounted for—deleted transaction).
  • Counterparty records (if a subsidiary received a $500K invoice from an external vendor, but the invoice log shows no such payment, it was deleted).
  • Date gaps (if transactions jump from Day 1 to Day 5 with no Day 2-4 entries, something was deleted).

This is by design. The RECONSTRUCTION contract type explicitly requires inferring deleted transactions. But even AUDIT contracts include occasional deletions to keep the operator sharp.


Money in BLACK LEDGER flows through a directed acyclic graph. Unlike ICE BREAKER’s network (where the operator can loop back), money flows downward through shells and can occasionally loop sideways (transfer between accounts at the same level).

When the operator views a transaction, they see:

TRANSACTION DETAIL
═════════════════════════════════════════════════════════════
Date: 2088-03-10
From Account: Nexus Holdings (balance pre-transfer: $2.1M)
To Account: Caribbean Trust (balance post-transfer: $2.0M)
Amount: $2.0M
Description: Quarterly Transfer
Counterparty: Caribbean Trust (beneficial owner: unknown)
Routing: Direct (no intermediaries)
[Suspicious Indicators:
• Large amount ($2.0M) unusual for this account
• Caribbean destination (tax haven jurisdiction)
• No documented business purpose for transfer]
[Use QUOTE to flag. Use CAR to follow to destination. Use CDR to scroll to next transaction.]

The transaction is a cell with multiple entry points:

  1. CAR on the transaction → Follow money to destination account
  2. QUOTE on the transaction → Mark as suspicious (or clear flag)
  3. EQ on two transactions → Compare amounts, dates, counterparties (are they part of the same scheme?)
  4. CDR in transaction list → Scroll through transaction history

Deleted Transactions: Reconstruction Puzzle

Section titled “Deleted Transactions: Reconstruction Puzzle”

A RECONSTRUCTION contract shows account balance changes but hides some transactions:

ACCOUNT BALANCE HISTORY
═════════════════════════════════════════════════════════════
Shell Company Z - Q1 2088
Date: 2088-01-01 Opening Balance: $0
Date: 2088-01-15 Receipt: $1.0M From: Parent Company (VISIBLE)
Date: 2088-01-20 [REDACTED - TRANSACTION DELETED]
Date: 2088-02-10 Outflow: $200K To: Unknown Account (VISIBLE)
Date: 2088-02-15 [REDACTED - TRANSACTION DELETED]
Date: 2088-03-01 Balance Check: $700K
RECONSTRUCTION PUZZLE:
The account went from $1.0M (after receipt on 01-15) to $700K (on 03-01).
Visible outflow: $200K on 02-10.
Missing: $100K (1M - 200K visible - 700K final = $100K unaccounted for).
You must infer: there was a $100K transfer on one of the redacted dates.
Who did it go to? When? Why?
[Use CONS to construct a transaction theory. Provide amount and likely destination.]

The operator must use contextual clues to infer the deleted transaction. This exercises lateral thinking and financial intuition.


4. SYSTEM THREE: THE SHELL COMPANY DETECTOR

Section titled “4. SYSTEM THREE: THE SHELL COMPANY DETECTOR”

A key skill in BLACK LEDGER is identifying shell companies. Shell companies exist to obscure money flows. They have characteristics:

  • Minimal business activity: Few transactions, low variance
  • Odd account names: Generic corporate names (Nexus Holdings, Caribbean Trust) vs. operational companies (Zenith Pacific Division)
  • Offshore jurisdiction: Delaware, Cayman Islands, BVI
  • No employees: (Not visible to operator, but Cipher voice hints at this)
  • High transfer-through rate: Money enters, is immediately routed out

The operator learns to recognize these patterns through play. On contract 1, a shell company is obvious (huge red flag). On contract 5, shells are disguised (mixed in with legitimate subsidiaries, requiring careful analysis).

The final goal of a SHELL MAPPING contract is to discover the beneficial owner—the human behind all the shells. Typically, the money eventually routes to a personal account (e.g., “J. Handler Personal Account” or “Cayman Private Trust - Handler beneficiary”).

Once the operator has mapped the entire shell network and traced money to a personal account, they can infer the beneficial owner. This is presented as a deduction:

BENEFICIAL OWNER INFERENCE
═════════════════════════════════════════════════════════════
You have traced $5.2M through the following shell network:
Zenith Industries → Nexus Holdings → Caribbean Trust →
Cayman Finance Corp → Handler LLC → Handler Private Account
The final account (Handler Private Account) is documented as belonging to:
Account Holder: J. Handler (identity on file)
Account Location: Cayman Islands
Account Status: Personal Trust
CONCLUSION: J. Handler is the beneficial owner of the shell network.
[Press EVAL to submit this finding. If correct: +50 reputation bonus.]

The YM2149 provides investigation atmosphere and financial tension.

Voice 1 (Investigation Theme): A slow, minor-key progression (C minor → G minor → F minor) that repeats every 8 beats. Base tempo: 60 BPM (slow, deliberate).

As time pressure increases (fewer than 10 minutes remaining), the tempo accelerates (120 BPM by the final minutes). The chord progression becomes more discordant (adding diminished chords, creating unresolved tension).

The operator learns: audio tempo = time pressure.

Voice 2 (Transaction Tone): Each transaction type has a distinct “personality” tone:

  • Legitimate operational transfer (salary, quarterly dividend): C4 (calm, normal)
  • Unusual but possibly legitimate (foreign vendor invoice, tax payment): D4 (questioning)
  • Suspicious (round-number transfer, tax-haven destination): E4 (alert)
  • Highly suspicious (deleted transaction, counterparty unknown): F#4 (alarm)

As the operator scrolls through a transaction list (CDR), the tone plays softly, telegraphing the transaction type. An experienced operator learns to auditorily scan a list: C, C, C, D, E, E, F#, C… They immediately know where the suspicious transactions are without reading.

Voice 3 (Feedback and Verdict):

  • QUOTE (flag transaction): Bright bell tone (G5, 100ms) + confirmation beep
  • CONS (link evidence): Ascending harmonic sequence (C4-E4-G4, stacked, 300ms)
  • Correct finding (judge confirmation): Major key resolution (C major, 1 second, satisfying)
  • False accusation (judge rejection): Unresolved minor (C minor with suspended tone, 300ms, unsatisfying)
  • Case submission (EVAL): Dramatic verdict swell (chord progression: Cm → Gm → Cm, 1 second)

An expert BLACK LEDGER operator can scan a transaction list by listening alone:

  • Hear C, C, C tones → all legitimate, skip ahead
  • Hear E, F#, E → suspicious cluster, investigate
  • Hear discordant cluster → hidden fraud, plan deep trace

This is not a gimmick. It accelerates case work. A Specialist operator can scan a 50-transaction list in 2 minutes by ear, identifying the top 5 suspicious items without reading.


The four systems collide in BLACK LEDGER: the corporate hierarchy, the money flows, the operator’s deductive reasoning, and the financial mystery itself.

An operator spots a large transfer from a subsidiary ($5M to a shell company). It looks suspicious. They flag it.

When they trace the money further, it turns out the shell company is a legitimate subsidiary restructuring. The money was moved to the shell to isolate tax liability for a bad investment (legal, if ethically questionable). It’s not money laundering.

The operator has incorrectly flagged a legitimate transaction. The judge penalizes them. They learn: appearance of suspicion ≠ actual wrongdoing. Good financial analysis requires hypothesis testing, not assumption.

On future contracts, the operator is more careful. They trace money to its final destination before flagging. They cross-reference transaction purposes. They think more deeply.

An operator is reconstructing deleted transactions. They infer: there was a $50K transfer on 02-15. They guess it went to “External Vendor Account.”

But when they trace the ledger history, they discover: External Vendor Account received $50K on 02-16 (not 02-15). So the $50K transfer couldn’t have been on 02-15.

The operator’s reconstruction is wrong. They must re-examine the balance deltas and come up with a different theory.

This teaches precision. Deleted transactions are puzzles. One misplaced piece breaks the whole solution.

An operator has mapped 8 shell companies. They’ve traced money from company A → B → C → D → E → F → G → H → Final Account. They believe they understand the conspiracy.

But then they notice: Company D has two parent accounts (both B and C send money to it). The graph is not linear; it’s branching. The operator has been thinking one-dimensionally (a straight line of transfers) when the actual structure is a network.

This emergent complexity forces the operator to revise their understanding. They must re-examine all the connections, seeing the full network topology.

This teaches systems thinking: money laundering is not a simple pipeline. It’s a complex, interconnected system designed to obscure the source.

An operator is working on a case with 15 minutes remaining. They’ve identified 6 of 8 guilty transactions. They know roughly where the final 2 are (in a deep subsidiary account), but they need to navigate there.

They can either:

  1. Spend 10 minutes carefully tracing the account hierarchy to find the final transactions (high certainty, low time buffer).
  2. Spend 3 minutes guessing based on pattern recognition (fast, but risky—might flag false positives).

They choose option 2 (fast). They submit with 2 minutes remaining. They correctly identify 1 of the final 2 transactions, but incorrectly flag 1 false positive.

Final score is lower than if they’d taken more time. They learn: speed is a risk factor. Expertise is knowing when to be fast (obvious red herring) and when to be slow (complex shell network).


BLACK LEDGER sessions are long and episodic. Each case is typically 30-60 minutes.

The 45-Minute Specialist FORENSIC TRACE Case

Section titled “The 45-Minute Specialist FORENSIC TRACE Case”

An operator with Reputation 20 (Investigator) takes a Threat 3 FORENSIC TRACE case.

Minutes 0-5: Briefing and Scanning. The operator sees the case brief:

CASE BRIEFING: "SHADOW HOLDINGS"
Duration: 45 minutes
Threat: 3 / 5 (corporate sensitivity)
Objective: Trace $2.3M in suspected bribes through shell network.
Identify the final beneficiary.
CORPORATE STRUCTURE:
Acme Corp (legit company) - parent
├─ Zenith Pacific (subsidiary) - legitimate operations
├─ Nexus Holdings (shell) - opacity
└─ Caribbean Trust (offshore) - high-risk jurisdiction
Your task: link the money flows and expose the conspiracy.

The operator presses CAR to enter the investigation. They are now in SCAN mode, surveying the hierarchy and spotting obvious entry points (Nexus Holdings looks suspicious immediately).

Minutes 5-15: Initial Assessment. The operator drills into Nexus Holdings and sees a $2.3M inflow from Acme Corp, followed by an immediate $2.0M outflow to Caribbean Trust. Red flags everywhere.

They flag these transactions and begin tracing. CAR into Caribbean Trust. More suspicious activity.

They are now in ASSESS mode, building a mental map of the money flows.

Minutes 15-30: Deep Trace. The operator follows the money trail:

  • $2.0M from Nexus → Caribbean Trust
  • $1.95M from Caribbean Trust → Cayman Finance Corp (5% fee shaved)
  • $1.85M from Cayman Finance Corp → Handler LLC (another 5% fee)

They manually trace the money, account by account. This is the TRACE phase. They are building evidence.

At minute 25, they discover: Handler LLC has a wire transfer to “Handler Private Account” (personal trust). The money has reached its final destination.

Minutes 30-40: Theory Building. The operator uses CONS to link all the flagged transactions into a coherent story:

  1. Bribe money ($2.3M) enters Acme Corp
  2. Immediately routed to Nexus Holdings (shell, hides origin)
  3. Then to Caribbean Trust (tax haven)
  4. Then to Cayman Finance Corp (further obscure)
  5. Finally to Handler LLC (front company for individual)
  6. Ultimately to Handler Personal Account (the recipient)

The operator has now entered the EXPOSE phase. They understand the whole conspiracy.

Minutes 40-45: Submission and Verdict. The operator presses EVAL to submit their findings. The judge evaluates:

VERDICT: Success (All Guilty Transactions Found)
═════════════════════════════════════════════════════════════
Flagged: 5 guilty transactions
Judge Evaluation:
✓ Nexus Inflow
✓ Nexus → Caribbean Transfer
✓ Caribbean → Cayman Transfer
✓ Cayman → Handler Transfer
✓ Handler Private Transfer
Accuracy: 100% (5/5 correct, 0 false flags)
Time Bonus: (5 min remaining / 45 min) = +11%
Beneficial Owner: Handler (correctly identified)
FINAL SCORE: (1500 base + 5×200) × 1.0 × 1.11 = 2665 points
REPUTATION GAIN: +5 (major investigation success)
CREDITS GAINED: 2665 ¤

The operator solved the case perfectly. Reputation increased by 5 (significant bump). They feel accomplished.

Total time: 45 minutes. A full investigative session. The operator is satisfied.

An operator spends 30 minutes on a case and realizes with 5 minutes remaining that they’ve misunderstood the shell network. They have flagged 4 transactions, but 2 are false positives (legitimate transfers they misflagged).

They submit. Verdict: Partial Success. Score is low (due to false flags). Reputation gains only +1.

But the case is not wasted. The operator learned:

  • How complex shell networks can be disguised among legitimate operations
  • The importance of cross-referencing dates and amounts before flagging
  • How their intuition about “suspicious” can be wrong

On the next case, they apply these lessons. They are more careful, more methodical. Their solve rate improves.


There is no tutorial. BLACK LEDGER teaches through play.

The operator powers on. The mission board appears:

MISSION BOARD — Available Cases
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
CASE 1: BASIC AUDIT [NEW]
Duration: 15 minutes Rep Gain: +1
Objective: Identify 2-3 suspicious transactions in a simple corporate structure
CASE 2: SIMPLE RECONSTRUCTION [LOCKED]
Unlock after completing Case 1
CASE 3: FORENSIC TRACE [LOCKED]
Unlock after Reputation 5

The operator selects CASE 1.

BLACK LEDGER // BASIC AUDIT
━━━━━━━━━━━━━━━━━━━━━━━━━━
Time Remaining: 15:00
OBJECTIVE: Audit a small company. Identify suspicious transactions.
CORPORATE STRUCTURE:
Main Corp (Parent)
├─ Operations Division (legitimate)
└─ Nexus Shell (suspicious-looking)
Cipher Voice: "You are an auditor. Your job: find the money flows
that don't make sense. Use CAR to drill into accounts.
CDR to scroll through transactions. QUOTE to flag suspicious ones.
EVAL to submit your findings."
[Press CAR to begin investigation]

The operator presses CAR to enter the first account. They see:

MAIN CORP — ACCOUNT OVERVIEW
═════════════════════════════════════════════════════════════
Balance: $50M
Last 5 Transactions:
01-15: Receive $10M (salary payments received from operations) [normal]
02-01: Transfer $5M to Operations Division [normal]
02-10: Transfer $2M to Nexus Shell [suspicious?]
03-01: Receive $1M (dividend from operations) [normal]
03-15: Transfer $3M to Nexus Shell [very suspicious!]
Cipher: "Look at the last two transfers to Nexus Shell.
That company doesn't do operations. Why is money being sent there?"
[CAR to drill into Nexus Shell. QUOTE to flag the transfers.]

The operator presses CAR to enter Nexus Shell:

NEXUS SHELL — ACCOUNT OVERVIEW
═════════════════════════════════════════════════════════════
Balance: $5M
Incoming: $5M (from Main Corp, two transfers: $2M and $3M)
Outgoing: $5M (routed to Caribbean Trust)
Cipher: "This company received money and immediately sent it out.
That's the signature of a shell company hiding money flow.
Flag the transfer to Caribbean Trust. Follow the money with CAR."

The operator presses QUOTE to flag the Caribbean transfer. Audio feedback (bright bell tone).

They press CAR to follow the money to Caribbean Trust. They see:

CARIBBEAN TRUST — ACCOUNT OVERVIEW
═════════════════════════════════════════════════════════════
Balance: $5M
Incoming: $5M (from Nexus Shell)
Outgoing: $4.75M (to Final Handler Account) [5% fee]
Cipher: "You've traced the money. It entered legitimately (Main Corp),
was hidden in a shell, then moved to a final account.
This is money laundering. Flag this transfer too."

The operator flags this transfer. They now understand the pattern.

Cipher: “You’ve found the money trail. Press EVAL to submit your case.”

The operator presses EVAL. Verdict:

AUDIT VERDICT
═════════════════════════════════════════════════════════════
You flagged 2 guilty transactions (correct).
You found 0 false positives (perfect accuracy).
Time remaining: 10:45
CASE SCORE: 500 (base) + 200 (correct flags) + 250 (time bonus) = 950 pts
REPUTATION GAIN: +2
CREDITS: 950 ¤

The operator has completed the intro case. They now understand:

  1. CAR drills into accounts
  2. CDR scrolls transactions
  3. QUOTE flags suspicious items
  4. Money flows through hierarchies
  5. Shell companies are obvious (yet insidious)

They are ready for CASE 2 (RECONSTRUCTION, which is harder).


BLACK LEDGER introduces a Logic Index stat (parallel to NEONGRID’s Proficiency).

Logic Index represents: analytical reasoning, pattern recognition in financial data, ability to infer missing information from context, and comfort with ambiguity.

It is measured 0-100 and increases through play:

ActionLogic Gain
Complete AUDIT case (0 false flags)+2
Complete RECONSTRUCTION (all deleted transactions inferred)+5
Complete FORENSIC TRACE (find beneficial owner)+3
Solve SHELL MAPPING (identify all shells in network)+4
Succeed with <25% time remaining+2 (speed bonus)

Like Proficiency, Logic Index affects cross-module gameplay:

  • In ICE BREAKER: High Logic (70+) gives +10% payout bonuses for SABOTAGE contracts (the operator can infer optimal destruction targets).
  • In NEONGRID: High Logic (70+) allows advanced pattern recognition in FLOW STATE (can predict sentry movements multiple turns ahead).
  • In DEPTHCHARGE: High Logic (70+) unlocks “strategic submersible” contracts (plan multi-phase underwater operations).

BLACK LEDGER supports asymmetric two-player mode:

Auditor (P1): Navigates the ledger, flags transactions. Makes decisions.

Analyst (P2): Watches the ledger, sees the full corporate structure (P1 can only see parts). Cannot directly control P1 but can suggest investigations via a LINK communication channel.

Example Scenario:

  • Auditor has traced money through 3 shells so far.
  • Analyst (watching the full structure) can see there are 2 more shells the Auditor hasn’t explored yet.
  • Analyst presses LINK and sends a message: “Check Caribbean Trust’s sub-accounts. Money might loop there before final exit.”
  • Auditor receives the hint and investigates, discovering the additional shells.

This creates asymmetric knowledge. The Analyst has more information but less agency. The Auditor has agency but incomplete information. Cooperation is essential.

Scoring: Both players share the final verdict. If the case succeeds, both get reputation and credits. If the case fails, both share the penalty. This creates accountability and collaboration.


╔════════════════════════════════════════════════════════════════════════════════╗
║ BLACK LEDGER // CASE SELECTION REPUTATION: 15 LOGIC_INDEX: 52 ║
╠════════════════════════════════════════════════════════════════════════════════╣
║ ║
║ AVAILABLE CASES: ║
║ ║
║ CASE 1: Basic Audit [COMPLETED ✓] Completion: 100% ║
║ Best Score: 950 pts | Best Time: 12:34 ║
║ ║
║ CASE 2: Simple Reconstruction [COMPLETED ✓] Completion: 85% ║
║ Best Score: 1420 pts | Accuracy: 95% ║
║ ║
║ CASE 3: Shell Network [AVAILABLE] Threat Level: 2/5 ║
║ Estimated Duration: 25 minutes ║
║ Unlock: Reputation 10 ✓ (You are eligible) ║
║ Your Record: Not yet attempted ║
║ ║
║ CASE 4: Money Laundering [AVAILABLE] Threat Level: 3/5 ║
║ Estimated Duration: 40 minutes ║
║ Unlock: Reputation 15 ✓ (You are eligible) ║
║ Your Record: 1st attempt - Lost due to time (Reviewed feedback) ║
║ ║
║ CASE 5: Caribbean Conspiracy [LOCKED] ║
║ Unlock: Reputation 20 (You have 15/20 - 5 pts to go) ║
║ ║
║ TRAINING CASES (Repeatable, no rep gain): ║
║ • Shell Detection 101 ║
║ • Forensic Trace Basics ║
║ • Deleted Transaction Inference ║
║ ║
║ CAR to select case │ CDR to browse │ INFO for case details │ SYS for menu ║
╚════════════════════════════════════════════════════════════════════════════════╝
╔════════════════════════════════════════════════════════════════════════════════╗
║ BLACK LEDGER // ACCOUNT TREE TIME: 28:15 / 45:00 ║
╠════════════════════════════════════════════════════════════════════════════════╣
║ ║
║ CORPORATE STRUCTURE (Hierarchy View) ║
║ ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ ║
║ ║
║ ├─ ZENITH INDUSTRIES (Parent Holding Company) [Balance: $8.5M] ║
║ │ │ ║
║ │ ├─ [+] Pacific Division (Subsidiary) [Balance: $120K] [LEGIT] ║
║ │ │ Last Transfer: $50K out (payroll) - 03-10 ║
║ │ │ ║
║ │ ├─ [+] Nexus Holdings (Shell Company) ⚠️ [Balance: $2.1M] [SHELL] ║
║ │ │ Last Transfer: $2.0M out (Caribbean) - 03-10 [SUSPICIOUS] ║
║ │ │ ║
║ │ └─ [+] Venerus Consulting (Front) [Balance: $50K] [SHELL] ║
║ │ Last Transfer: $10K invoice (unknown) - 02-15 ║
║ │ ║
║ └─ OFFSHORE TIER (Addresses Unknown - Hidden Structure) ║
║ ├─ Caribbean Trust [Balance: $1.8M] ║
║ ├─ Cayman Finance Corp [Balance: $1.6M] ║
║ └─ Handler LLC [Balance: $1.5M] ║
║ ║
║ SELECTED: Nexus Holdings ║
║ ─────────────────────────────────────────────────────────────────────────── ║
║ Account Type: Shell Company (Delaware incorporation) ║
║ Beneficial Owner: [UNKNOWN] ║
║ Status: Active ║
║ Last Activity: 03-10 (5 days ago) ║
║ ║
║ Recent Transactions: ║
║ 01-20: IN +$500K from Zenith Industries ║
║ 02-05: IN +$1.5M from Zenith Industries ║
║ 03-10: OUT -$2.0M to Caribbean Trust [FLAGGED ⚠️] ║
║ 03-12: IN +$300K from Zenith Industries ║
║ ║
║ [Press CAR to drill into Nexus details] ║
║ [Press CDR to browse other accounts] ║
║ [Press QUOTE to flag suspicious activity] ║
║ [Press EQ to compare transactions] ║
║ ║
╚════════════════════════════════════════════════════════════════════════════════╝
╔════════════════════════════════════════════════════════════════════════════════╗
║ BLACK LEDGER // MONEY FLOW DIAGRAM ║
╠════════════════════════════════════════════════════════════════════════════════╣
║ ║
║ TRACED MONEY PATH (Sankey Diagram) ║
║ ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ ║
║ ║
║ Zenith Industries ║
║ [Bribery Payment: $2.3M] ║
║ │ ║
║ ├─ $500K (01-20) ──→ Nexus Holdings ║
║ │ │ ║
║ ├─ $1.5M (02-05) ──→ (Shell - Hides Origin) ║
║ │ │ ║
║ └─ $300K (03-12) ──→ (Continued funding) ║
║ │ ║
║ $2.0M total (03-10) ║
║ │ ║
║ ↓ [5% fee shaved] ║
║ │ ║
║ Caribbean Trust ║
║ [Tax Haven Routing] ║
║ │ ║
║ $1.95M (post-fee) ║
║ │ ║
║ ↓ [5% fee shaved] ║
║ │ ║
║ Cayman Finance Corp ║
║ [Further Obscure] ║
║ │ ║
║ $1.85M (post-fee) ║
║ │ ║
║ ↓ ║
║ │ ║
║ Handler LLC ║
║ [Final Destination] ║
║ │ ║
║ ↓ ║
║ Handler Personal Account ║
║ [BENEFICIAL OWNER: Unknown] ║
║ ║
║ Total Original: $2.3M ║
║ Final Amount: $1.85M (19.8% lost to fees) ║
║ ║
║ [Press BACK to hide diagram] [Press CAR to drill into each account] ║
╚════════════════════════════════════════════════════════════════════════════════╝
╔════════════════════════════════════════════════════════════════════════════════╗
║ BLACK LEDGER // TRANSACTION DETAIL TIME: 28:15 / 45:00 ║
╠════════════════════════════════════════════════════════════════════════════════╣
║ ║
║ TRANSACTION ID: TXN-2088-03-10-001 ║
║ ═════════════════════════════════════════════════════════════════════════════ ║
║ ║
║ Date: 2088-03-10 Time: 14:32:17 GMT ║
║ From Account: Nexus Holdings (Shell Company, Delaware) ║
║ To Account: Caribbean Trust (Offshore, Cayman Islands) ║
║ Amount: $2,000,000.00 USD ║
║ Currency: USD ║
║ Routing: Direct Wire (no intermediaries) ║
║ Description: "Quarterly Transfer" ║
║ ║
║ ROUTING DETAILS: ║
║ └─ SWIFT Code: XXXXXX (routed through London banking center) ║
║ └─ Intermediary Bank: [Standard international routing] ║
║ ║
║ FUND SOURCE: Previous incoming transfer from Zenith Industries (02-05) ║
║ └─ Amount: $1.5M | Plus Jan-20 transfer: $500K | = $2.0M available ║
║ ║
║ SUSPICIOUS INDICATORS: ║
║ ⚠️ Large transfer amount ($2M unusual for this account's historical average) ║
║ ⚠️ Destination jurisdiction (Cayman Islands - known tax haven) ║
║ ⚠️ Lack of documented business purpose ║
║ ⚠️ Timing: Immediate transfer out (no working capital held in shell) ║
║ ⚠️ Counterparty: Caribbean Trust is privately registered (beneficial owner ║
║ unknown to public records) ║
║ ║
║ LIKELIHOOD OF MONEY LAUNDERING: 95% ║
║ ║
║ ─────────────────────────────────────────────────────────────────────────── ║
║ [Press QUOTE to FLAG this transaction] ║
║ [Press CAR to follow money to destination (Caribbean Trust)] ║
║ [Press EQ to compare with other suspicious transactions] ║
║ [Press CDR to scroll to next transaction] ║
║ [Press BACK to return to account overview] ║
╚════════════════════════════════════════════════════════════════════════════════╝
╔════════════════════════════════════════════════════════════════════════════════╗
║ BLACK LEDGER // CASE VERDICT ║
╠════════════════════════════════════════════════════════════════════════════════╣
║ ║
║ CASE: "SHADOW HOLDINGS" — Money Laundering Investigation ║
║ Status: SUBMITTED ║
║ ║
║ ═════════════════════════════════════════════════════════════════════════════ ║
║ YOUR FINDINGS: ║
║ ═════════════════════════════════════════════════════════════════════════════ ║
║ ║
║ Flagged Transactions: 5 total ║
║ 1. Zenith → Nexus ($1.5M) ............................ [GUILTY ✓] ║
║ 2. Zenith → Nexus ($500K) ........................... [GUILTY ✓] ║
║ 3. Nexus → Caribbean ($2.0M) ........................ [GUILTY ✓] ║
║ 4. Caribbean → Cayman ($1.95M) ...................... [GUILTY ✓] ║
║ 5. Cayman → Handler ($1.85M) ........................ [GUILTY ✓] ║
║ ║
║ ═════════════════════════════════════════════════════════════════════════════ ║
║ JUDGE EVALUATION: ║
║ ═════════════════════════════════════════════════════════════════════════════ ║
║ ║
║ Accuracy: 5/5 correct flags (100%) ║
║ False Positives: 0 (no legitimate transactions incorrectly flagged) ║
║ Beneficial Owner Identified: Handler, J. ✓ ║
║ Time Remaining: 5m 23s / 45m 00s ║
║ ║
║ VERDICT: COMPLETE SUCCESS ║
║ ║
║ ═════════════════════════════════════════════════════════════════════════════ ║
║ SCORING: ║
║ ═════════════════════════════════════════════════════════════════════════════ ║
║ ║
║ Base Payout (Threat 3): ¤900 ║
║ Guilty Transaction Bonus (5 × 200): ¤1000 ║
║ Accuracy Multiplier (100%): ×1.00 ║
║ Time Bonus (23% remaining): ×1.23 ║
║ ───────────────────────────── ║
║ FINAL CASE REWARD: ¤2573 ║
║ ║
║ Reputation Gain: +4 ║
║ Logic Index Gain: +5 (complex conspiracy solved) ║
║ Beneficial Owner Discovery Bonus: +50 reputation ║
║ ║
║ CUMULATIVE REPUTATION: 15 → 19 (1 below next unlock threshold) ║
║ ║
║ ═════════════════════════════════════════════════════════════════════════════ ║
║ ║
║ [Press EVAL to return to case selection] ║
║ [Press QUOTE to review flagged transactions] ║
║ ║
╚════════════════════════════════════════════════════════════════════════════════╝


NEONGRID and BLACK LEDGER are not games in the traditional sense. They are capability pedagogy—systems designed to teach the operator to think spatially (NEONGRID) and analytically (BLACK LEDGER).

Both modules are structured around emergent learning: the operator develops expertise not from tutorials but from repeated, gradually-increasing challenges that reward deeper understanding of the underlying systems.

Both modules integrate seamlessly into the broader KN-86 ecosystem via cross-module proficiency metrics (Proficiency for NEONGRID, Logic Index for BLACK LEDGER), creating incentives for operators to invest in foundational skills that pay off across all cartridges.

The hidden depth—audio-only navigation in NEONGRID, complex multi-shell conspiracies in BLACK LEDGER—creates a mastery curve that extends for hundreds of hours. An operator who invests the time becomes not just good at NEONGRID, but a fundamentally better Deckline operator.

This is the quality bar ICE BREAKER set. NEONGRID and BLACK LEDGER meet it.