KN-86 Deckline Launch Titles — Capability Model

System Design Document Kinoshita Consumer Electronics Hardware Reference: KN-86 Deckline (1988 Personal Cyberspace Terminal)

INTRODUCTION: PHILOSOPHY OF CAPABILITY

The KN-86 Deckline does not sell games. It sells capability. Each launch title is a capability module—operational software that expands what the deck can do, how the operator can work, and what the mission board can generate.

The device’s Universal Deck State (persisted on the Pi’s microSD per ADR-0011; ADR-0015 added CIPHER coherence-stack and event-ring fields) is the connective tissue. Every module reads from it, writes to it, unlocks new contract templates based on what cartridges have been loaded. Reputation accrues across all modules. Credits pool in one economy. The phase chain preserves mission state across physical cartridge swaps.

The Capability Curve:

1 cartridge: complete single-domain career
4 cartridges: multi-phase contracts, cross-domain threats, highest-paying operations
Full library: the most complex, highest-leverage work

This document defines the complete architectural foundation for the four launch modules: ICE BREAKER, NEONGRID, BLACK LEDGER, and DEPTHCHARGE.

MODULE 1: ICE BREAKER — NETWORK INTRUSION CAPABILITY

Gameplay Reference: ICE Breaker’s detailed gameplay specification, including OODA loop mechanics, Hot Swap mid-run cartridge swaps, and tempo-driven combat, is documented in KN-86-ICE-Breaker-Gameplay-Spec.md. This section describes the module’s integration into the capability model and cross-module contracts. For playtest blueprint and core mechanical design, refer to that dedicated spec.

1.1 Module Identity

Designation: NETWORK INTRUSION (MODULE CLASS: 0x01) Publisher: Zaibatsu Digital (Osaka) Profile: Flagship capability module; pack-in with hardware Operator Role: Network penetration specialist, security tester, data extraction specialist Deck State Signature: Sets bit 0 in cartridge history bitfield on first load Loading Screen: Rapid hex dump fills screen with harsh white noise, freezes, center dissolves into the angular Zaibatsu mark. Silence. 3.0 seconds.

ICE BREAKER transforms the Deckline into a network intrusion workstation. The operator specializes in reconnaissance, node mapping, cipher breaking, system compromise, and defensive countermeasures (Sysop Mode). It is not a game about hacking—it is the operational framework for modeling network incursion workflows.

On First Load: The Mission Board immediately gains access to PENETRATION, EXTRACTION, SABOTAGE, and SURVEILLANCE templates. The operator’s deck is now marked as having intrusion capability. All future module interactions check this bit: Sysop Mode in ICE BREAKER is unavailable until another module is loaded (creating asymmetry in linked play). Depthcharge waterfront sequences become available if ICE BREAKER is loaded.

1.2 Mission Template Architecture

Contract Classes

Contract Type	Description	Threat Range	Base Payout	Phases
PENETRATION	Gain access to a network node; plant marker or disable defense	1–4	400–1600 ¤	1–2
EXTRACTION	Recover specific data from a defended node; data weight varies	2–5	800–3200 ¤	2–3
SABOTAGE	Corrupt or disable a system asset; secondary effect on adjacent nodes	2–4	1200–2400 ¤	1–2
SURVEILLANCE IMPLANT	Deploy persistent monitoring beacon; requires periodic maintenance	1–3	600–2000 ¤	3–4 (episodic)

Template Structure (Procedural Generation)

PENETRATION Contract:

threat_level: 1–4 (ICE density, node depth)
network_topology: 3–7 nodes, randomly connected
primary_defense: cipher_grade (A–D), firewall_type (STATIC/REACTIVE)
secondary_defenses: 0–2 (trap trigger, lockdown cascade)
reward: threat_level × 100 ¤
bonus_condition: complete in single cartridge load (no phase swap)

EXTRACTION Contract:

threat_level: 2–5 (ICE intelligence, data guard proximity)
target_data: size_bytes (256–4096), classification (FINANCIAL/PERSONNEL/DESIGNS)
network_depth: 2–5 hops from entry node
data_guards: 1–3 active ICE routines (pursuing operator)
exfil_window: turn limit (varies by threat_level; higher threat = tighter window)
reward: 200 ¤ per 512 bytes + threat_bonus
abort_penalty: data corruption; partial recovery possible if escape successful

SABOTAGE Contract:

threat_level: 2–4 (target criticality, secondary cascade risk)
target_system: type (COMMS/POWER/SECURITY/FINANCIAL)
collateral_sensitivity: how many adjacent nodes are affected on destruction
disarm_option: bypass ICE without triggering cascade (harder, higher reward)
reward: 300 ¤ base + 200 ¤ per avoided cascade
complication: other deck loaded? If BLACK LEDGER in history, financial cascades have audit trail (mission becomes phase 2)

SURVEILLANCE IMPLANT Contract:

threat_level: 1–3 (initial plant difficulty)
target_frequency: weekly/biweekly/monthly check-in requirement (3–12 phases total)
persistence_duration: real-time calendar (if skipped, contract fails; operator loses reputation)
information_yield: data trickles in; smaller than EXTRACTION but passive income (100–200 ¤ per phase)
maintenance_risk: each check-in has small re-detection chance (cumulative; higher rep = lower risk)
reward: 50–150 ¤ per phase + completion bonus of 500 ¤
complication: if NEONGRID loaded, training interference (surveillance becomes noisy; harder success threshold)

Threat Range Mechanics

Network density scales with threat level. A threat 1 node is 3–5 ICE routines; threat 4 is 12–20. ICE intelligence (how well it predicts operator moves) scales nonlinearly—threat 3 ICE is 4× smarter than threat 1, not 3×.

1.3 Deck State Integration

SRAM Writes:

knowledge_index increments by 1 after completing a PENETRATION contract (max 255; gates advanced node types at knowledge ≥ 50)
logic_index increments by 1 after a successful EXTRACTION or sabotage of a REACTIVE defense (max 255; gates cipher grade C and above at logic ≥ 30)
credit_balance increases/decreases per contract outcome
reputation_score increases by 1 per threat point overcome; decreases by 2 on mission failure
cartridge_history bit 0 set permanently; bits 1–3 checked on load to generate cross-module complications

Reputation Thresholds (ICE BREAKER Context):

Rep 0–4: Entry-level node access. Contracts max threat 2. No Sysop Mode. Data extraction limits 512 bytes max.
Rep 5–14: Intermediate operations. Threat max 3. Sysop Mode available (requires second module in history). Extraction limit 2048 bytes.
Rep 15–24: Advanced specialist. Threat max 4. REACTIVE ICE becomes standard. Multi-phase extractions common. Surveillance implants unlock.
Rep 25–49: Master operator. Threat max 5. Access to highest-intelligence ICE. Phase chains can span 4+ cartridges. Sysop Mode grants additional probe tools.
Rep 50+: Elite tier. Exclusive contracts: ZERO-DAY HUNT (find undocumented ICE), NETWORK ARCHAEOLOGY (recover data from dead systems), RIVAL OPERATOR CLASH (PvP via link cable).

1.4 Cross-Module Interactions

With NEONGRID (Training Module):

If NEONGRID is in cartridge history: ICE BREAKER contracts include CALIBRATION NODES—test data that looks like real threats but grants bonus rep on completion.
Navigation becomes slightly easier in NEONGRID context (lower cipher grades on first encounter).

With BLACK LEDGER (Forensic Audit):

SABOTAGE contracts targeting FINANCIAL systems generate an automatic BLACK LEDGER phase: operator must audit the damage trail, trace fund flows, cover tracks.
2-phase mission: ICE BREAKER phase 1 (plant sabotage), BLACK LEDGER phase 2 (audit cover-up).
Reward increases 40% if both phases complete cleanly.

With DEPTHCHARGE (Sonar/Submersible):

SURVEILLANCE IMPLANT contracts on underwater relay stations become possible if DEPTHCHARGE is in history.
Asymmetric linked operation: one operator runs ICE BREAKER surveillance network, other runs DEPTHCHARGE evasion. Operator A’s sonar pings trigger Operator B’s ICE alerts.
“Dead drop” contract type unlocks: plant encrypted data package in a node; retrieve via submersible drone at different time.

Self-Reference:

Sysop Mode (defensive network monitoring) requires a second module in history. Solo ICE BREAKER has limited tools. Loaded with any other module: Sysop Mode activates, doubles ICE deployment options, enables active defense against incoming intrusions (linked play only).

1.5 Multi-Phase Mission Design

Phase Architecture

Each phase is atomic: cartridge swap point. The phase chain (8 bytes in SRAM) stores:

current_phase_id (1 byte): which phase we’re on
mission_type (1 byte): PENETRATION/EXTRACTION/etc.
context_data (6 bytes): threat level, node depth, data handle, ICE state

Example 2-Phase: EXTRACTION + SABOTAGE (Directed Chaos)

Phase 1 (ICE BREAKER):

Penetrate a node to depth 3, extract 1024 bytes of personnel data.
Threat 3, time limit 8 turns.
Success criteria: exfiltrate data to deck local storage.
Reward: 1200 ¤.
Phase chain write: phase=1, mission=DIRECTED_CHAOS, threat=3, data_handle=0x42.

Phase 2 (ICE BREAKER, same cartridge or after reload):

Sabotage the backup system that would detect the data theft.
Secondary complication: ICE in this node has memory of phase 1 attack. It’s more aggressive.
Threat 4 (elevated from 3 due to phase 1 activity).
Success criteria: disable backup without triggering lockdown (harder than normal sabotage).
Reward: 2000 ¤ + 500 ¤ phase-chain completion bonus.

Total: 3700 ¤. Rep gain: +3 (threat points) +1 (phase completion) = +4. But if phase 1 fails, phase 2 is inaccessible; mission aborted, rep hit -2.

Example 3-Phase: SURVEILLANCE IMPLANT (Full Cycle)

Phase 1 (ICE BREAKER, Week 1 real-time):

Plant implant in a communications hub. Threat 1.
Reward: 150 ¤. Phase chain marks: phase=1, mission=SURVEILLANCE, maintenance_window=weekly.

Phase 2 (ICE BREAKER, Week 2):

Check-in on implant. ICE may have detected it (25% chance + rep modifier). If detected: re-plant or abort.
Reward: 100 ¤ (data trickle) + 100 ¤ maintenance bonus.
Phase chain updates: phase=2, detection_risk=+0.05.

Phase 3 (ICE BREAKER, Week 4):

Final check-in. If detection_risk ≥ 0.5: ICE is hunting. Operator must either extract implant (lose data source) or re-obfuscate (hard cipher puzzle).
If clean extraction: 200 ¤ + 500 ¤ completion bonus.
Reputation: +2 for each successful check-in, -3 if caught.

Total payout: 950–1050 ¤ across 4 weeks. Reputation range: +4 to -3. Engagement is about persistence, not a single session.

1.6 Capability Progression

Not difficulty levels, but operational mastery and deck evolution.

Rep 0–4 (Apprentice):

Access: single-node targets, static ICE only.
Deck capability: 6 active operations max per session.
Mastery: learning node traversal, basic cipher, escape mechanics.
Audio feedback: Cipher voice is present, helpful. Warnings on approaching ICE.

Rep 5–14 (Journeyman):

Access: multi-node networks (3–4 depth), reactive ICE.
Sysop Mode unlocked (requires paired module).
Deck capability: 12 active operations per session; 2 concurrent extraction windows.
Mastery: predicting ICE behavior, route planning, active defense.
Audio feedback: Cipher voice becomes terse. Operator must listen for subtle pitch shifts (sonar-like ICE proximity cues).

Rep 15–24 (Specialist):

Access: advanced networks (5+ depth), threat 4 ICE.
Surveillance implants available.
Deck capability: 20 active operations; 3 concurrent extraction windows; long-range node probes.
Mastery: multi-phase planning, trade-off analysis (speed vs. stealth).
Audio feedback: Cipher voice is minimal; the deck’s ambient sound design becomes the primary operational cue.

Rep 25–49 (Master):

Access: highest-threat networks, threat 5 ICE.
Sysop Mode is fully featured; passive network monitoring becomes available.
Deck capability: unlimited active operations; ZERO-DAY hunts unlock.
Mastery: designing own implant configurations, predicting ICE evolution.
Audio feedback: Pure silence; Cipher voice only on critical alerts.

Rep 50+ (Legend):

Access: EXCLUSIVE contracts—RIVAL OPERATOR CLASH (link cable), NETWORK ARCHAEOLOGY.
Deck capability: multi-cartridge simultaneous operations (requires phase chain orchestration).
Mastery: teaching other operators, writing custom ICE.
Audio feedback: Cipher voice returns, now speaking cryptic prophecy / lore tidbits.

1.7 Contract Economics

Base Payout Formula:

base_reward = threat_level × 200 ¤
time_bonus = (turns_remaining / turns_limit) × 0.2 × base_reward
rep_multiplier = 1 + (reputation_score / 100)
final_payout = (base_reward + time_bonus) × rep_multiplier

Examples:

Threat 2 PENETRATION, rep 5, completed in 4/8 turns: (400 + 100) × 1.05 = 525 ¤
Threat 4 EXTRACTION, rep 25, completed in 6/10 turns: (800 + 160) × 1.25 = 1200 ¤
Threat 5 SABOTAGE, rep 50, completed in 3/6 turns: (1000 + 500) × 1.5 = 2250 ¤

Risk/Reward Curve:

Threat	Base Reward	Failure Rep Hit	Rep Gain (Success)	Operator Profitability
1	200 ¤	-1	+1	Break-even to +200 ¤
2	400 ¤	-1	+2	Safe +300–500 ¤
3	600 ¤	-2	+3	Risky +400–800 ¤
4	800 ¤	-2	+4	High variance, 1200+ ¤
5	1000+ ¤	-3	+5	Extreme variance; 2000+ ¤ or rep collapse

Universal Credit System:

All modules trade in ¤ (kinoshita credits). Unused credits carry across cartridge swaps. A wealthy operator (5000+ ¤) can bribe ICE to reduce threat by 1 level (one-time, per contract, costs 500 ¤). Credits fund deck upgrades, reputation recovery, and cross-module gear (explained later).

Expensive Operations (Rep 25+):

ZERO-DAY HUNT: costs 2000 ¤ upfront; reward is 5000–8000 ¤ if successful, custom cipher unlock.
NETWORK ARCHAEOLOGY: costs 1500 ¤ to initiate (environmental scan equipment); reward 3000–5000 ¤ depending on data antiquity.
RIVAL OPERATOR CLASH: costs 500 ¤ (link cable setup); reward is 2000–4000 ¤ + reputation trophy (bragging rights across all modules).

1.8 Operator Workflow

A Typical “Shift” (Single Cartridge Load, ~30 minutes):

Boot & Status Check (2 min): Cipher voice plays system startup prompt. Operator reviews available contracts on Mission Board, checks rep/credit balance, notes any ongoing surveillance implants requiring maintenance.
Contract Selection (1 min): Operator selects a PENETRATION or EXTRACTION contract (threat 2–3, typical choice). ICE BREAKER loads the contract, generates network topology, displays it as an ASCII graph.
Reconnaissance Phase (5 min): Operator uses CDR (list traversal) to scroll through network nodes, probes entry point defenses using CAR. Audio cues (pitch of YM2149) indicate ICE proximity. Operator maps safe routes.
Active Phase (15 min): Operator executes: APPLY deploys tools (probes, cipher-breakers, data extractor). CAR/CDR navigate deeper. Real-time ICE pursuit if detected; operator must balance speed vs. stealth. Tension via audio + text updates.
Exfil/Completion (5 min): Operator escapes network or triggers sabotage. Data secured (or lost). Cipher voice delivers debrief. Mission complete or failed. Reputation and credits awarded. Contract archived.
Next Operation or Shutdown (2 min): Operator queues next contract or powers down (credits/rep saved to SRAM).

Multi-Shift Campaign (Multi-Module Operator):

An operator with ICE BREAKER + BLACK LEDGER might pursue a 2-phase EXTRACTION + SABOTAGE operation spanning 60 minutes across two cartridge swaps:

Phase 1 (ICE BREAKER, 25 min): Extract financial records from a node.
Swap cartridge.
Phase 2 (BLACK LEDGER, 25 min): Audit the transaction trails, cover the theft.
Swap back to ICE BREAKER for final sabotage (10 min).
Total payout: 3700–4500 ¤ if all phases succeed. Reputation: +6.

1.9 Cipher Voice Integration

The Cipher (YM2149-controlled speech synthesis, minimal CPU cost) narrates ICE BREAKER operations. Its tone: precise, militaristic, cryptic.

On Load:

“Kinoshita Intrusion Suite armed. Deck status: ready. Running threat assessment… Loading your cartridge history. [pause] Found DEPTHCHARGE in your profile. Underwater relay nodes available. Interesting choices, operator.”

During Penetration:

“You’re in. Network topology rendering. Three entry vectors available. ICE density rising in eastern node.”

During ICE Pursuit:

“ICE acquiring lock. Evasion window: 3 turns. Your choice: stand and fight, or flee. Both have costs.”

On Mission Success:

“Contract complete. Data secured. Reputation increased. You now have access to… [check reputation threshold] …advanced cipher grades. Congratulations.”

On Mission Failure:

“ICE locked you down. Contract terminated. Reputation decreased. Your next operations will be watched more closely. Proceed carefully.”

Debrief (Rep 25+):

“Your technique is improving. That node was running a variant ICE I’ve never seen before. You just taught me something. I appreciate that. Credits transferred.”

Sysop Mode Active (Linked):

“Sysop Mode enabled. You are now a network defender. Incoming intrusion detected. Operator [linked deck handle] is moving through node 4. Deploy countermeasures?”

The Cipher’s voice evolves: at low rep, it’s instructive. At high rep, it becomes almost conversational, dropping hints about deeper mysteries, offering respect. By rep 50+, it speaks in riddles and philosophy, hinting at a larger world beyond the cartridge.

1.10 Cell Architecture

ICE BREAKER defines the core navigable structures:

CELL_TYPE NODE {
  ON_CAR: probe_node(depth, threat_level, ice_type)
           -> returns ICE_INTELLIGENCE (hostile/neutral/compromised)
  ON_CDR: move_adjacent_node()
           -> returns NODE (neighboring in network graph)
  ON_EVAL: execute_tool(tool_type)
            -> CRYPTO_BREAKER | DATA_EXTRACTOR | TRAP_DEFUSER
};

CELL_TYPE ICE {
  ON_CAR: query_strength() -> returns threat_level (1–5)
  ON_CDR: move_toward_operator() -> returns new proximity_score
  ON_EVAL: engage_operator() -> triggers combat/evasion sequence
};

CELL_TYPE NETWORK {
  ON_CAR: get_node_at(index) -> returns NODE
  ON_CDR: get_adjacent_networks() -> returns NETWORK list
  ON_EVAL: initiate_extraction() -> locks data, starts exfil sequence
};

CELL_TYPE DATA {
  ON_CAR: get_size() -> returns bytes (256–4096)
  ON_CDR: get_classification() -> FINANCIAL | PERSONNEL | DESIGNS
  ON_EVAL: lock_data() -> begins countdown to permanent delete if not exfil'd
};

Composition Example:

Operator navigates: NETWORK → NODE → ICE → (if defeated) → DATA.

(NETWORK
  (NODE 1 (ICE threat=3 intelligence=adaptive)
         (DATA size=2048 class=FINANCIAL))
  (NODE 2 ...)
  (NODE 3 ...))

Operator uses CDR to scroll through nodes, CAR to probe ICE, APPLY to deploy tools. EVAL triggers tool execution. Lists compose into a fully navigable, interactive network model.

1.11 Sound Design as Interface

The YM2149’s three voices:

Voice 1 (Square Wave, ~3kHz): ICE proximity. Pitch increases as operator approaches ICE. Frequency = threat_level × base_pitch. Operator learns to “listen” for danger; experienced operators can predict ICE behavior by pitch modulation.

Voice 2 (Sawtooth, ~1kHz): Data flow. Pulses when operator is extracting data. Frequency modulation represents data throughput. Faster pulse = larger data chunks. Sudden silence = data loss / interruption.

Voice 3 (Noise, variable): Environmental chaos. Random bursts when ICE is actively hunting. Volume and density correlate with pursuit intensity. Complete silence = stealth successful.

Operational Feedback:

Entering a network: all three voices initialize, establishing ambient baseline.
Safe zone: minimal tone; mostly silence.
Detection imminent: Voice 1 (ICE) rises sharply; Voice 3 (chaos) begins sporadic bursts.
Active pursuit: all three voices in counterpoint—a musical representation of simultaneous threats.
Extraction success: Voice 2 reaches peak frequency, then resolves downward in a resolved cadence.
Lockdown/failure: all voices harmonize in a discordant minor chord, then cut.

Not entertainment. Pure operational semiotics.

1.12 Link Protocol

Two KN-86 decks running ICE BREAKER can link via cable. Asymmetric roles:

ATTACKER Role:

One operator launches intrusion contracts.
Their network topology is shared (read-only) to the DEFENDER.
Real-time position updates sent every turn.

DEFENDER Role:

One operator monitors the ATTACKER’s position passively (Sysop Mode).
Can deploy ICE countermeasures, move ICE to intercept.
Cannot launch offensive contracts; only defensive redirection.

Data Flow:

Attacker Deck:
  -> operator_position (node_id, depth)
  -> extracted_data_handle (size, classification)
  -> evasion_route (next nodes planned)

Defender Deck:
  <- threat_assessment (adjusted ICE intensity)
  <- countermeasure_status (deployed, active, neutralized)
  -> lockdown_trigger (if ICE catches attacker)

Linked Example: Asymmetric Operation

Scenario: Attacker tries EXTRACTION at threat 3. Defender is Sysop.

Turn 1: Attacker enters network. Defender sees entry node. Defender moves ICE to intercept.
Turn 2: Attacker probes Node 2. ICE arrives at Node 1 (Defender chose that position). Attacker safe.
Turn 3: Attacker reaches data. Defender deploys advanced ICE at Node 2 (Attacker’s next exit route). Attacker sees ICE bar ahead; must choose new route or engage.
Turn 4: Attacker backtracks to Node 3, avoided Node 2. Defender counterdeployed ICE there too. Attacker cornered.
Turn 5: Attacker engages ICE in combat (cipher puzzle, real-time). Defender simultaneously hacks that ICE to reduce its intelligence by 2 (costs Defender 3 turns of Sysop actions). Attacker wins combat, escapes.
Extraction success. Reward split: Attacker gets 1200 ¤, Defender gets 400 ¤ (for effective Sysop play). Reputation: Attacker +3, Defender +2.

Economics: Both decks benefit, but risk is asymmetric. Attacker can fail (reputation hit). Defender cannot fail (passive role), but earns less. This creates dynamic partnerships.

MODULE 2: NEONGRID — GRID TRAVERSAL / TRAINING CAPABILITY

2.1 Module Identity

Designation: NAVIGATION (TRAINING) (MODULE CLASS: 0x02) Publisher: Edgeware Systems Co., Ltd. (Tokyo) — KEC first-party Profile: Introductory module; teaches KN-86 interaction grammar; persistent utility tool Operator Role: Trainee operator, deck calibrator, navigation architect Deck State Signature: Sets bit 1 in cartridge history bitfield on first load Loading Screen: Edgeware wordmark assembles character by character with soft keyclick per letter, single clean 440Hz tone on completion. Corporate. Restrained. 2.0 seconds.

NEONGRID is the onboarding framework and persistent operational utility of the Deckline. It teaches function key semantics, numpad navigation, list operations, and the fundamental philosophy of Lisp-inspired cellular navigation. Unlike most training software, NEONGRID is not a disposable tutorial—it becomes a core deck utility throughout the operator’s career.

On First Load: The Mission Board generates CALIBRATION and NAVIGATION TRAINING contracts. The operator learns: CDR (list descent), CAR (structure inspection), EVAL (action execution), QUOTE (marking positions). NEONGRID has no real monetary reward—it pays in reputation and deck proficiency. Completing NEONGRID training unlocks faster contract generation across ALL modules and reduces ICE Breaker cipher difficulty by 1 grade.

Persistent Utility: NEONGRID remains accessible after initial training. Operators use it as:

Route planner (for ICE BREAKER network escapes)
Cipher pattern visualizer (for BLACK LEDGER financial tracing)
Sonar calibration tool (for DEPTHCHARGE depth mapping)
A meditative navigation exercise for high-stress operators

2.2 Mission Template Architecture

Contract Classes

Contract Type	Description	Duration	Rep Gain	Deck Proficiency Gain
CALIBRATION	Test specific function key; verify input/output	1–2 min	+0.5	+1 per key tested
NAVIGATION TRAINING	Navigate a procedural grid, reach checkpoint	5–10 min	+1	+2 per zone
PATTERN RECOGNITION	Identify cipher patterns in scrolling grid	5 min	+0.5	+1
FLOW STATE	Endless grid movement; survive 5 min without error	5 min	+1	+3 (sharp rep spike)

Template Structure (Procedural Generation)

CALIBRATION Contract:

target_key: one of 30 KN-86 keys (CAR/CDR/CONS/NIL, EVAL/QUOTE/LAMBDA/APPLY, ATOM, EQ, navigation, system)
test_sequence: 3–5 inputs that test that key's function
expected_output: text or position change
operator_mastery: speed × accuracy score
reward: minimal credits (50–100 ¤), significant rep (+0.5 per correct input)

Example: CAR calibration.

Input 1: CAR on a list (return head element). Operator presses CAR, gets returned element. PASS.
Input 2: CAR on an atomic value. Operator should get error/NULL. Operator presses CAR, gets error. PASS.
Input 3: CAR on a nested list. Return head of head. Operator presses CAR twice correctly. PASS.
Reward: 0 ¤, rep +1.5, proficiency +3.

NAVIGATION TRAINING Contract:

grid_size: 5×5 to 10×10 ASCII grid
checkpoints: 2–5 locations operator must visit in sequence
navigation_method: numpad ONLY (forces muscle memory)
time_limit: 1 turn per step (no time bonus; focus on learning)
hazards: none (non-threatening; pure navigation)
reward: 100–200 ¤, rep +1–2 per checkpoint, proficiency +2 per zone

Example: Training Grid 2.

[START]
....E
.W...
P....
.....
S....

Operator must navigate: START → P (Press CAR at start, traverse down) → E (CDR across) → S (CAR down) → W (CDR right).

PATTERN RECOGNITION Contract:

grid_type: scrolling cipher patterns (hamming codes, repeat sequences, prime number spacing)
operator_task: identify pattern, input it via numpad
time_pressure: medium (30–60 seconds)
difficulty: 3 patterns (easy), 5 patterns (intermediate), 7+ patterns (advanced)
reward: 150–300 ¤, rep +1–3, cipher proficiency +2–5

FLOW STATE Contract:

grid: procedurally generated, infinite (or until error)
operator_task: navigate continuously, no errors, 5 minutes
hazards: none; purely mechanical flow
success_condition: 5 minutes without input mistake
reward: 500 ¤, rep +2 (SHARP SPIKE; represents operator focus), proficiency +3
failure_condition: one wrong input = mission restart

The FLOW STATE is a meditation exercise. Operators run it to center themselves before high-stakes ICE BREAKER raids or to recover reputation after failures. It’s paid relaxation.

2.3 Deck State Integration

SRAM Writes:

knowledge_index not affected (NEONGRID is metacognitive, not epistemic)
logic_index not affected
credit_balance increases slowly (NEONGRID is cheap; 50–500 ¤ per contract)
reputation_score increases moderately; fractional rep gains (+0.5, +1, +2) accumulate
cartridge_history bit 1 set permanently; all other modules check this bit to reduce cipher difficulty
NEW: proficiency_vector (4 bytes) — a hidden deck stat encoding operator hand-eye coordination, decision speed, pattern recognition aptitude. Affects all future operations.

Proficiency Mechanics:

Proficiency is invisible to the operator but affects all modules:

Proficiency Level	Effect
0–20	All cipher difficulties +1 grade. ICE BREAKER threat levels effectively +1.
21–40	Neutral. Baseline module behavior.
41–60	All cipher difficulties -1 grade. Slightly faster contract generation.
61–80	Cipher difficulties -1 grade. Mission board generates bonus high-rep contracts.
81–100	Cipher difficulties -2 grades. ICE threat levels effectively -1. Exclusive “expert” contracts unlock.

Reputation Thresholds (NEONGRID Context):

Rep 0–2: CALIBRATION contracts only. 16 keys to master (4 reps per key mastery = 8 hours of training).
Rep 2–5: NAVIGATION TRAINING added. Basic grids (5×5).
Rep 5–10: PATTERN RECOGNITION added. Cipher training begins.
Rep 10–20: FLOW STATE added. Operator is “trained.” NEONGRID becomes optional utility.
Rep 20+: NEONGRID is meditation/proficiency maintenance only. No new contracts. But operators return monthly (real-time calendar) to stay sharp.

2.4 Cross-Module Interactions

With ICE BREAKER (Network Intrusion):

Having NEONGRID in cartridge history: ICE BREAKER node routing becomes easier (cipher grades -1).
CALIBRATION keys practiced in NEONGRID apply directly to ICE BREAKER: operator’s CAR/CDR navigation is smoother, faster.
Proficiency 50+: operator can preview network topology in NEONGRID-style grid before loading ICE BREAKER (strategic advantage).

With BLACK LEDGER (Forensic Audit):

PATTERN RECOGNITION contracts in NEONGRID teach the same cipher patterns used in BLACK LEDGER financial reconstruction.
Operator with high NEONGRID proficiency (70+) can “see” money-flow patterns at a glance in BLACK LEDGER.
Navigation speed in BLACK LEDGER increased 25% if NEONGRID is in history.

With DEPTHCHARGE (Sonar/Submersible):

NAVIGATION TRAINING grids procedurally match DEPTHCHARGE depth topology (sonar return patterns visualized as grids).
Operator trained in NEONGRID can “read” DEPTHCHARGE sonar returns more intuitively.
Proficiency translates to faster drone positioning in combat scenarios.

Self-Reference:

Solo NEONGRID: pure training, no operational constraints.
Paired with another module: NEONGRID becomes a utility, selectively loaded for prep or maintenance.

2.5 Multi-Phase Mission Design

NEONGRID does not have traditional multi-phase operations. Instead, it has proficiency chains: repeated missions over real-time calendar that maintain and increase operator skill.

Proficiency Chain Example: “The 10-Week Mastery Program”

Week 1–2: CALIBRATION of all 16 keys. Rep +8 total. Proficiency +16.

Week 3–5: NAVIGATION TRAINING grids, increasing difficulty. Rep +6 total. Proficiency +20.

Week 6–8: PATTERN RECOGNITION, cipher variants. Rep +5 total. Proficiency +15.

Week 9–10: FLOW STATE, twice per week, maintain muscle memory. Rep +4 total. Proficiency +10.

Total: Rep +23, Proficiency +61 (moves operator from baseline to “expert” tier).

Impact: After 10 weeks, this operator’s ICE BREAKER operations are 2 grades easier, threat levels feel -1, and exclusive contracts unlock.

2.6 Capability Progression

Proficiency Tiers, Not Rep Tiers:

Tier 1: Apprentice (Proficiency 0–20)

Clumsy navigation. Keys are deliberately poorly labeled in ASCII art (operator must learn by trial).
Grid size: 5×5 max.
Numpad response time: visible (200ms lag on screen to simulate operator error).
Audio: frequent error beeps; Cipher voice is encouraging but admits the operator is struggling.

Tier 2: Novice (Proficiency 21–40)

Navigation is smooth. Keys are now properly labeled.
Grid size: up to 10×10.
Numpad response: immediate (no lag).
Audio: error beeps are less frequent; Cipher voice is neutral, professional.

Tier 3: Competent (Proficiency 41–60)

Navigation is fast. Grids become visually complex (ASCII art is denser).
Grid size: 15×15 possible; infinite (FLOW STATE).
Numpad response: prediction (operator anticipates Cipher’s next prompt).
Audio: error beeps are rare; Cipher voice hints at deeper patterns.

Tier 4: Expert (Proficiency 61–80)

Navigation is intuitive. Grids are abstract (operator reads them as data, not visual puzzles).
Operator can visualize grid state mentally; less reliance on screen display.
Numpad response: operator is leading, not following.
Audio: Cipher voice is sparse; mostly silence, broken by operator’s own typing rhythm.

Tier 5: Master (Proficiency 81–100)

Navigation is unconscious. The grid is a metaphor.
Operator runs FLOW STATE in the dark, headphones on, pure somatic navigation.
Numpad response: musician-like flow; no conscious decision-making.
Audio: Cipher voice speaks only in riddles. “You no longer read the grid, you are the grid.”

2.7 Contract Economics

Payout Formula:

base_reward = 100 ¤ (CALIBRATION) | 200 ¤ (TRAINING) | 300 ¤ (PATTERN) | 500 ¤ (FLOW)
speed_bonus = (completion_time / expected_time) × 0.1 × base_reward
accuracy_multiplier = (correct_inputs / total_inputs)
final_payout = base_reward × accuracy_multiplier + speed_bonus

Examples:

CALIBRATION (CAR key): 100 ¤ base, 100% accuracy, completed in 30 seconds (expected 60s): 100 × 1.0 + 50 = 150 ¤.
NAVIGATION TRAINING: 200 ¤ base, 95% accuracy (1 wrong turn), completed in 3 minutes (expected 5): 200 × 0.95 + 40 = 230 ¤.
PATTERN RECOGNITION: 300 ¤ base, 100% accuracy, completed in 3 minutes (expected 5): 300 × 1.0 + 120 = 420 ¤.
FLOW STATE: 500 ¤ base, 100% accuracy (5 min no errors): 500 × 1.0 = 500 ¤ (no speed bonus; task is time-limited, not speedrun).

Universal Credit System Integration:

NEONGRID is cheap. An operator can run CALIBRATION + TRAINING contracts for ~400–500 ¤ per session, no risk. It’s a “safe” money source for operators between risky ICE BREAKER raids. Experienced operators use NEONGRID as a cooldown activity, trading minimal time for modest credits and significant proficiency gains.

Expensive “Expertise” Operations:

MASTERY CHALLENGE: operator pays 500 ¤ to unlock a randomized “perfect run” contract (highest difficulty grid, FLOW STATE rules, but with real-time calendar pressure and cross-module integration). Reward: 2000 ¤ + exclusive decal for deck + reputation +3 if successful.

2.8 Operator Workflow

A Typical NEONGRID Session:

Pre-Mission Check (1 min): Operator loads NEONGRID, checks proficiency score, reads Cipher’s greeting.
Contract Selection (30 sec): Operator picks CALIBRATION (warm-up), TRAINING (main practice), or FLOW STATE (cooldown).
Execution (2–10 min depending on contract): Operator runs the contract. Pure focus. No narrative, no stakes, no failure penalty—only progression.
Debrief (1 min): Cipher voice analyzes performance. Proficiency increases logged. Credits awarded. Operator sees progress bar fill.
Transition (30 sec): Operator either queues another NEONGRID contract or loads a different cartridge to apply their training.

Multi-Session Campaign:

A new operator spends their first 2–3 deck loads entirely in NEONGRID (6–8 hours cumulative across a few days). By load 4, they’re confident enough to attempt ICE BREAKER introductory contracts. By load 10, NEONGRID is optional; the operator uses it maybe once a week for maintenance.

An expert operator (rep 50+, proficiency 90+) still loads NEONGRID monthly:

15-minute FLOW STATE session (5 min × 3 runs)
Proficiency maintenance, meditation, grip-testing
Credits: 1500 ¤ for minimal time investment

2.9 Cipher Voice Integration

Cipher’s tone in NEONGRID: patient mentor, increasingly impressed as operator improves.

On Load (Apprentice):

“NEONGRID initialized. This module teaches you how to talk to the deck. How to think in lists. How to navigate. I know it’s strange. I’ll guide you. Take your time.”

During CALIBRATION (Apprentice):

“Press CAR. This key asks: ‘What is the first element?’ Let’s try it.”

Operator makes error:

“Close. You pressed CDR instead. CDR asks for the rest of the list, not the first. Try again.”

During NAVIGATION TRAINING (Novice):

“You’re moving smoothly now. I see the pattern—you’re thinking ahead two moves. That’s good.”

During PATTERN RECOGNITION (Competent):

“Fascinating. You recognized the Hamming code buried in the noise before I even highlighted it. Your pattern recognition is exceptional.”

During FLOW STATE (Expert):

“You haven’t made an error in two minutes. The grid is an extension of you now. Keep going.”

Operator reaches Proficiency 100:

“[silence for 10 seconds] … I have nothing left to teach you. You have become the grid. Now go teach others. Or better yet: go break something. You have the skill. And I have a feeling—you have the will too.”

2.10 Cell Architecture

NEONGRID defines the navigable grid primitive:

CELL_TYPE GRID {
  ON_CAR: get_cell_at(current_position) -> returns CELL
  ON_CDR: move_forward() -> updates current_position, returns GRID
  ON_EVAL: navigate_to(target) -> calculates path, executes sequence
};

CELL_TYPE CELL {
  ON_CAR: get_content() -> returns SYMBOL (landmark, hazard, checkpoint)
  ON_CDR: get_adjacent_cells() -> returns list of CELL
  ON_EVAL: interact() -> if checkpoint, mark complete; if landmark, describe it
};

CELL_TYPE LANDMARK {
  ON_CAR: get_name() -> returns string (name of location)
  ON_CDR: get_adjacent_landmarks() -> returns nearby landmarks
  ON_EVAL: meditate() -> operator dwells here; proficiency +0.5, sound feedback
};

CELL_TYPE CHECKPOINT {
  ON_CAR: get_id() -> returns checkpoint number
  ON_CDR: get_next_checkpoint() -> returns next CHECKPOINT in sequence
  ON_EVAL: mark_complete() -> flags as visited; triggers audio reward
};

Composition Example:

(GRID 5x5
  (CELL 0,0 LANDMARK "entrance")
  (CELL 0,1 LANDMARK "corridor")
  (CELL 1,1 CHECKPOINT 1)
  (CELL 2,0 LANDMARK "chamber")
  (CELL 2,2 CHECKPOINT 2)
  ...)

Operator navigates by CDR-ing through the grid, CAR-ing individual cells, and EVAL-ing checkpoints. Fully navigable, intuitive Lisp metaphor.

2.11 Sound Design as Interface

The YM2149 in NEONGRID serves positive reinforcement and operator state feedback.

Voice 1 (Square Wave, ~2kHz): Operator action echo. Every keypress produces a tone. Pitch is based on which key was pressed:

CAR: high pitch (C4, 262 Hz)
CDR: mid pitch (G3, 196 Hz)
CONS: low pitch (C3, 131 Hz)
Navigation keys: brief chirps (ascending/descending based on direction)

Operator learns to “hear” their own commands, building somatic feedback loop.

Voice 2 (Sawtooth, ~1kHz): Position feedback. A continuous tone represents operator’s location in the grid:

Tone frequency = position_y / grid_height × 1000 Hz (vertical axis mapped to pitch)
Operator can close eyes and “navigate by ear”

Voice 3 (Noise, variable): Achievement tone. Checkpoints reached, patterns recognized:

Checkpoint: ascending arpeggio (3 notes, 200ms each)
Pattern identified: rising swell (1 second crescendo)
Error: descending buzz (100ms)
FLOW STATE success: full resolve (major chord, 2 second duration)

Operational Feedback:

Warm-up: all three voices initialize in harmony (welcoming)
Active navigation: Voice 1 (action) + Voice 2 (position) form harmonic movement
Checkpoint reached: Voice 3 (achievement) swells over Voices 1+2 (creates moment of triumph)
Error: Voice 1 drops out; Voice 3 (error buzz) dominates
Cool-down: all voices fade to silence (meditative)

2.12 Link Protocol

NEONGRID has optional asymmetric linked play for teaching:

INSTRUCTOR Role (Master Operator):

Designs a custom NAVIGATION TRAINING grid
Sends grid to STUDENT deck via cable
Can hint/guide in real-time (Cipher voice relays hints)
Sees STUDENT’s position and mistakes in real-time

STUDENT Role (Learning Operator):

Receives custom grid
Navigates independently
Receives hints from Instructor (filtered through Cipher)
Cannot see Instructor’s view

Data Flow:

Instructor Deck:
  -> grid_definition (ASCII art + checkpoint sequence)
  -> hint_queue (guidance messages)
  -> student_performance (navigation speed, accuracy)

Student Deck:
  <- grid (rendered locally)
  <- hints (Cipher relays them)
  -> position_updates (every move)
  -> checkpoint_completion (when reached)

Linked Example: Training Session

Instructor is a veteran proficiency 95. Student is new operator proficiency 15.

Instructor designs a 10×10 grid with 5 checkpoints, intentionally challenging.
Student loads it. Cipher voice says: “Your instructor has prepared a challenge. Navigate carefully.”
Student explores. After 2 minutes, stuck at checkpoint 3. Cipher relays hint from Instructor: “You’re thinking in straight lines. Think around.”
Student reorients, takes a different route, reaches checkpoint 3. Cipher relays praise from Instructor: “Better. You’re learning.”
Student completes grid in 5 minutes. Proficiency +5 (bonus for learning from Instructor). Rep +2.
Instructor’s deck: rep +1 (for teaching).

Economics: Teaching is rewarded. Expert operators can run “master classes” and earn reputation for training new operators. Creates mentorship economy within the KN-86 culture.

MODULE 3: BLACK LEDGER — FORENSIC AUDIT CAPABILITY

3.1 Module Identity

Designation: FORENSIC AUDIT (MODULE CLASS: 0x03) Publisher: Bureau 9 Technical Services (no address on record) Profile: Investigation and financial reconstruction specialist module Operator Role: Corporate investigator, financial forensicist, data analyst Deck State Signature: Sets bit 2 in cartridge history bitfield on first load Loading Screen: Dead silence. Classification header types mechanically across the screen — “BUREAU 9 TECHNICAL SERVICES / CLASSIFICATION: UNCLASSIFIED / DISTRIBUTION: AUTHORIZED OPERATORS.” No animation. No logo. No sound. 2.8 seconds.

BLACK LEDGER transforms the Deckline into a forensic accounting workstation. The operator specializes in tracing financial flows, reconstructing transactions, exposing fraud, auditing corporate shell networks, and covering (or uncovering) money laundering schemes. It is operational forensics software—not a game about accounting, but the functional framework for financial intelligence work.

On First Load: The Mission Board generates AUDIT, RECONSTRUCTION, FORENSIC TRACE, and SHELL MAPPING contracts. The operator’s deck is marked as having audit capability. All future cross-module interactions check this bit: ICE BREAKER SABOTAGE contracts now have an automatic phase 2 (financial cover-up); DEPTHCHARGE underwater transactions become available for laundering operations.

3.2 Mission Template Architecture

Contract Classes

Contract Type	Description	Threat Range	Base Payout	Phases
AUDIT	Verify legitimacy of transaction chain; flag anomalies	1–3	500–1500 ¤	1–2
RECONSTRUCTION	Recover deleted/hidden transactions from account trees	2–4	1000–2500 ¤	2–3
FORENSIC TRACE	Follow money through shell accounts; expose final recipient	3–5	1500–4000 ¤	3–4
SHELL MAPPING	Diagram corporate ownership chains; identify beneficial owners	2–4	1200–3000 ¤	2–3

Template Structure (Procedural Generation)

AUDIT Contract:

account_tree_depth: 3–6 levels (checking account → sub-accounts → transactions)
transaction_count: 10–50 entries per account level
anomaly_type: unusual_transfer | timing_violation | amount_spike | currency_mismatch
operator_task: navigate tree, identify anomalies, flag them with QUOTE
time_limit: 5–10 turns (flexible; more turns = lower reward multiplier)
threat_level: 1–3 (corporate security sensitivity)
reward: 500 + (anomalies_found × 100) ¤
rep_gain: +1 per anomaly found; +0.5 per correct "safe" transaction verified

Example: ABC Corp audit. Operator navigates tree:

ABC Corp (checking account) $50M balance
  ├─ Operating Expenses $2M/month (normal)
  ├─ Payroll $1M/month (normal)
  ├─ Tax Reserve $5M (normal)
  ├─ ANOMALY: Cayman Islands Transfer $5M (flagged!)
  └─ ANOMALY: 3AM Wire to Offshore Subsidiary $2M (flagged!)

Operator uses CDR to toggle panes, CAR to inspect each transaction, QUOTE to mark anomalies. Identifies 2 anomalies, verifies 8 transactions as legitimate. Reward: 500 + 200 = 700 ¤.

RECONSTRUCTION Contract:

deleted_transactions: 5–15 transaction records have been erased from logs
operator_task: use account balance deltas, timestamp patterns, and counterparty records to infer missing transactions
evidence_clues: 2–3 fragments per deleted transaction (amount, party, approximate date)
operator_reconstruction: assemble fragments into coherent transaction sequence using CONS
time_limit: 10–20 turns (higher complexity)
threat_level: 2–4 (higher sensitivity; someone is hiding this)
reward: 1000 + (transactions_reconstructed × 150) ¤
rep_gain: +2 per reconstructed transaction; -2 per incorrect reconstruction (false positive)

Example: Shell Company Z has 8 deleted transactions. Operator finds clues:

Clue A: amount “$500K”, date “March 15”, counterparty “unknown”
Clue B: account delta ”-$500K” on March 15
Clue C: shell company A received equivalent amount on March 15

Operator uses CONS to build: ($500K transfer FROM Z TO A on March 15). Correct reconstruction. Rep +2. Repeat for 8 transactions. Total: rep +16, reward 2200 ¤.

FORENSIC TRACE Contract:

money_origin: $1M–$50M sum initiated at a "clean" company
money_destination: final recipient is hidden through 5–10 shell companies
operator_task: follow money through shell network, identify each transfer, locate final recipient
navigation_metaphor: money_flow is a directed graph; operator uses CAR (follow transaction) and CDR (move to next shell) to trace
time_limit: 20–40 turns (long, complex contract)
threat_level: 3–5 (highest sensitivity; this is active money laundering)
reward: 1500 + (shells_traversed × 300) ¤
rep_gain: +3 per shell correctly identified; -1 per wrong shell traversed (dead end)
complication: if ICE BREAKER in history, defensive ICE may be protecting shell network (ICE BREAKER phase 1 required to disable defenses before phase 2 audit)

Example: Operator must trace $10M from “Acme Corp” through 7 shells to final beneficiary “Handler LLC”.

Turn 1: Acme → Shell A ($10M). Operator CAR follows transaction.
Turn 2: Shell A → Shell B ($9.5M, with $0.5M “service fee” skimmed). Operator CDR navigates to Shell B.
…
Turn 13: Shell G → Handler LLC ($7.2M, after cumulative skimming). Operator reaches destination.

Reward: 1500 + (7 shells × 300) = 3600 ¤. Rep: +21 (if all shells identified correctly).

SHELL MAPPING Contract:

corporate_structure: 8–20 shell companies with complex ownership relationships
operator_task: build ownership tree; use CONS to structure hierarchy; identify beneficial owner (human behind all shells)
navigation_metaphor: CAR/CDR to navigate corporate hierarchy; QUOTE to mark shell relationships
time_limit: 15–25 turns
threat_level: 2–4 (depends on target's sensitivity)
reward: 1200 + (shells_mapped × 200) ¤
rep_gain: +2 per shell correctly positioned in ownership tree; +5 bonus if beneficial owner identified
complication: if DEPTHCHARGE in history, operator can trace money to submarine accounts (financial hidden assets)

3.3 Deck State Integration

SRAM Writes:

knowledge_index not affected (BLACK LEDGER is not epistemic)
logic_index increments by 1 per completed FORENSIC TRACE (rewards analytical thinking)
credit_balance increases significantly (BLACK LEDGER pays well; 500–4000 ¤ per contract)
reputation_score increases moderately to heavily (audit work compounds)
cartridge_history bit 2 set permanently
NEW: audit_log (8 bytes) — a hidden record of operator’s forensic findings, usable for future contracts and cross-module reputation

Reputation Thresholds (BLACK LEDGER Context):

Rep 0–4: AUDIT contracts only. Single account level. No shell complexity.
Rep 5–14: RECONSTRUCTION added. Simple deleted transactions (3–5 per contract).
Rep 15–24: FORENSIC TRACE added. Basic shell networks (3–5 shells).
Rep 25–49: SHELL MAPPING added. Complex ownership structures (10+ shells). Beneficial owner identification unlocks.
Rep 50+: EXCLUSIVE contracts: INVESTIGATION SUMMIT (largest corporate audit, highest payout), ADVERSARIAL AUDIT (competing with another operator to uncover fraud first), REGULATORY COOPERATION (government agency contracts for high payout + special status).

3.4 Cross-Module Interactions

With ICE BREAKER (Network Intrusion):

ICE BREAKER SABOTAGE contracts (especially financial system sabotage) automatically trigger BLACK LEDGER phase 2: cover-up audit.
2-phase mission: destroy financial system → audit the destruction to hide tracks.
Special mission type unlocks: “REGULATORY EVASION”—after sabotaging, construct false audit trails to make destruction look accidental.
Reward: +40% if both phases successful.

With NEONGRID (Grid Traversal):

PATTERN RECOGNITION training in NEONGRID teaches financial cipher patterns.
Operator with NEONGRID proficiency 50+: can “see” suspicious patterns at a glance (FORENSIC TRACE difficulty reduced 1 level).
Navigation speed in BLACK LEDGER account tree: +25% if NEONGRID in history.

With DEPTHCHARGE (Sonar/Submersible):

FORENSIC TRACE contracts can target underwater financial nodes (submarine accounts, deep-water money transfers).
Special mission: DEEP AUDIT—trace money that has been submerged (hidden in DEPTHCHARGE submarine accounts).
Operator with DEPTHCHARGE in history can access exclusive “offshore” shell networks (hidden from normal audits).
2-phase: submersible drone access phase (DEPTHCHARGE) → account audit phase (BLACK LEDGER).

Self-Reference:

Solo BLACK LEDGER: pure audit, no operational complications.
Paired with ICE BREAKER: high-stakes financial sabotage and evasion.
Paired with DEPTHCHARGE: offshore/submersible financial networks.

3.5 Multi-Phase Mission Design

Phase Architecture

BLACK LEDGER phases are sequential investigations. Each phase uncovers data that informs the next phase.

Example 2-Phase: AUDIT + RECONSTRUCTION (Fraud Discovery)

Phase 1 (BLACK LEDGER):

AUDIT a corporation’s books for anomalies.
Operator identifies 4 suspicious transactions (flagged with QUOTE).
Threat 2, payout 700 ¤.
Phase chain write: phase=1, mission=FRAUD_DISCOVERY, anomalies_found=4, total_amount=$2.3M.

Phase 2 (BLACK LEDGER, after cartridge reload or same load):

RECONSTRUCTION: reconstruct the 4 deleted transactions leading up to the identified anomalies.
Threat 3, higher complexity.
Operator must assemble evidence fragments into coherent fraud scheme.
Bonus condition: if reconstructed scheme matches preliminary audit findings, reward multiplier +1.5.
Payout: 2000 ¤ × 1.5 = 3000 ¤.
Rep gain: +2 + (4 reconstructions × 2) = +10.

Total: 3700 ¤, rep +12. Operator has uncovered a $2.3M fraud scheme. The company’s reputation (in-universe) takes a hit; operator’s reputation soars.

Example 3-Phase: FORENSIC TRACE (Full Money Laundering Investigation)

Phase 1 (BLACK LEDGER):

Identify dirty money inflow (AUDIT reveals unusual transfer amounts).
Threat 1, payout 500 ¤.
Phase chain: phase=1, mission=MONEY_LAUNDERING, source=$10M.

Phase 2 (BLACK LEDGER, possibly requires ICE BREAKER phase 1 for digital protection):

Trace money through shell network (FORENSIC TRACE).
Threat 3, payout 2200 ¤.
Operator traces $10M → Shell A → Shell B → … → Shell F → intermediate account.
Phase chain: phase=2, shells_traversed=6, money_remaining=$6.8M.

Phase 3 (BLACK LEDGER + DEPTHCHARGE optional):

Final destination analysis. If operator loads DEPTHCHARGE: money is traced to submarine account (deepwater financial haven via submersible drone). DEPTHCHARGE phase unlocks asymmetrically.
Threat 4, payout 3000 ¤.
Operator maps beneficial owner (human behind all shells).
Phase chain complete. Final rep: +15.

Total: 5700 ¤, rep +15. Operator has exposed a major money laundering operation.

3.6 Capability Progression

NOT difficulty levels, but operational mastery and investigative depth.

Rep 0–4 (Junior Analyst):

Access: single account audits, straightforward anomalies.
Deck capability: 3 active investigations max per session.
Mastery: learning account tree navigation, identifying obvious fraud (unusual amounts, timing).
Audio feedback: Cipher voice is instructive, points out anomalies.

Rep 5–14 (Investigator):

Access: multi-level account trees, deleted transaction reconstruction.
Deck capability: 5 active investigations; RECONSTRUCTION becomes primary focus.
Mastery: inferring missing data from context clues, pattern recognition in transaction sequences.
Audio feedback: Cipher voice becomes analytical; offers hypotheses.

Rep 15–24 (Senior Auditor):

Access: shell networks (3–5 layers), forensic traces across multiple companies.
Deck capability: 10 active investigations; long-term traces spanning weeks of real-time calendar.
Mastery: predicting money flows, understanding corporate structures, anticipating evasion techniques.
Audio feedback: Cipher voice is collegial; treats operator as peer investigator.

Rep 25–49 (Chief Investigator):

Access: massive shell networks (10+ layers), beneficial owner identification, adversarial audits.
Deck capability: unlimited investigations; can orchestrate multi-cartridge audit campaigns.
Mastery: writing custom audit templates, designing trap account networks, training junior operators.
Audio feedback: Cipher voice is rare; mostly silence, broken by occasional cryptic observations.

Rep 50+ (Legend):

Access: EXCLUSIVE contracts—INVESTIGATION SUMMIT (largest corporate structure ever), REGULATORY COOPERATION, ADVERSARIAL AUDIT.
Deck capability: government agency contracts, high-stakes financial warfare.
Mastery: setting industry-wide audit standards, exposing multi-billion-dollar frauds.
Audio feedback: Cipher voice returns, now philosophical. “You have seen the shape of hidden wealth. What will you do with that knowledge?“

3.7 Contract Economics

Base Payout Formula:

base_reward = threat_level × 300 ¤ (BLACK LEDGER baseline is higher than ICE BREAKER)
complexity_bonus = (account_depth × 50) + (shell_count × 75) ¤
accuracy_multiplier = (correct_findings / total_findings)
speed_multiplier = 1 + (turns_remaining / turns_limit) × 0.25
final_payout = (base_reward + complexity_bonus) × accuracy_multiplier × speed_multiplier

Examples:

Threat 1 AUDIT, 3 account levels, 3 anomalies found (all correct), 4/8 turns remaining: (300 + 150) × 1.0 × 1.125 = 506 ¤
Threat 3 RECONSTRUCTION, 4 transactions reconstructed (all correct), 8/15 turns: (900 + 200) × 1.0 × 1.167 = 1283 ¤
Threat 4 FORENSIC TRACE, 7 shells traced (all correct), 15/30 turns: (1200 + 525) × 1.0 × 1.25 = 2156 ¤
Threat 5 SHELL MAPPING, 15 shells, 20+ beneficial owner found, 20/35 turns: (1500 + 1125) × 1.0 × 1.43 = 3782 ¤

Risk/Reward Curve:

Threat	Base Reward	Failure Rep Hit	Rep Gain (Success)	Operator Profitability
1	300 ¤	-1	+1	250–350 ¤
2	600 ¤	-2	+2	450–750 ¤
3	900 ¤	-2	+3	600–1200 ¤
4	1200 ¤	-3	+4	800–1800 ¤
5	1500+ ¤	-3	+5	1000–3000+ ¤

Exclusive High-Rep Operations:

INVESTIGATION SUMMIT (rep 50+): 15,000 ¤ + regulatory prestige. Largest corporate audit ever. Takes 8 hours of real-time calendar to complete (weekly phases over 8 weeks).
ADVERSARIAL AUDIT (rep 30+): two operators compete to uncover fraud first. Winner gets 2000 ¤ + reputation trophy. Loser gets 500 ¤ consolation + reputation -2.
REGULATORY COOPERATION (rep 45+): government agency pays 5000 ¤ for audit results. High payout, zero risk (cannot fail; only incomplete phases cost rep).

3.8 Operator Workflow

A Typical BLACK LEDGER Session:

Case Selection (2 min): Operator loads BLACK LEDGER, reviews available audits on Mission Board. Chooses AUDIT, RECONSTRUCTION, or FORENSIC TRACE based on time available and risk appetite.
Initial Assessment (3 min): Account tree loads. Operator uses CAR to inspect account head, CDR to scroll through transactions. Cipher voice provides baseline context (“This corporation has $50M in operating accounts. Verify legitimacy.”).
Navigation & Inspection (10–20 min): Operator navigates account levels, marks suspicious transactions with QUOTE, verifies legitimate ones by examining counterparties, amounts, timing. Uses CDR at the pane level to toggle between panes (key BLACK LEDGER workflow).
Findings Assembly (5 min): Operator uses CONS to structure findings (if RECONSTRUCTION), or flags anomalies, or traces shell network. Assemble evidence into coherent narrative.
Report & Completion (2 min): Operator submits findings. Cipher voice delivers verdict. Payout awarded. Reputation adjusted. Contract archived in audit log.

Multi-Session Campaign (Multi-Module):

An operator with ICE BREAKER + BLACK LEDGER might pursue a high-stakes investigation:

Session 1 (ICE BREAKER, 25 min): Sabotage a corporation’s financial system.
Session 2 (BLACK LEDGER, 30 min): Audit the damage, construct false audit trails to hide sabotage.
Payout: Session 1: 1200 ¤. Session 2: 3000 ¤. Total: 4200 ¤. Rep: +6.

This is the “financial terrorism” campaign—destroy and cover up simultaneously.

3.9 Cipher Voice Integration

Cipher’s tone in BLACK LEDGER: forensic analyst, professional skepticism, increasing respect for operator insight.

On Load:

“BLACK LEDGER initialized. Corporate audit and forensic analysis suite online. I have 47 active cases pending. Which would you like to investigate?”

During AUDIT (Operator finds first anomaly):

“You found it. Transaction at 3AM to a Cayman account. That’s not normal business. Good eye.”

During RECONSTRUCTION (Operator makes error):

“That doesn’t fit. If $5M left the account on March 15, but there’s only $2M unaccounted for, your reconstruction is incomplete. Try again.”

During FORENSIC TRACE (Operator navigates multiple shells):

“You’re tracing money through 6 shell companies. I’m impressed. Most operators give up after 3. Keep going.”

On Mission Success (High Rep):

“You’ve exposed a $15M laundering scheme. This corporation’s executives are going to have a very bad day. You should be proud.”

On Beneficial Owner Identification:

“You found them. The human behind all these shells. Do you know who they are? Should I cross-reference this name against known criminal networks?”

Debrief (Rep 25+):

“Your techniques are evolving. You’re not just finding anomalies—you’re thinking like the criminals. Understanding their logic. That’s dangerous. But it’s also brilliant.”

3.10 Cell Architecture

BLACK LEDGER defines the account tree primitive:

CELL_TYPE ACCOUNT {
  ON_CAR: get_balance() -> returns amount (integer, cents)
  ON_CDR: get_sub_accounts() -> returns list of ACCOUNT
  ON_EVAL: audit_account() -> flags anomalies, returns ANOMALY list
};

CELL_TYPE TRANSACTION {
  ON_CAR: get_amount() -> returns integer (signed; negative=outflow)
  ON_CDR: get_counterparty() -> returns ACCOUNT or SHELL
  ON_EVAL: investigate() -> reveals transaction metadata (timestamp, description, hidden flags)
};

CELL_TYPE SHELL {
  ON_CAR: get_ownership() -> returns owner (human or SHELL)
  ON_CDR: get_related_shells() -> returns list of SHELL (known associates)
  ON_EVAL: expose() -> reveals beneficial owner if available
};

CELL_TYPE ANOMALY {
  ON_CAR: get_type() -> returns SYMBOL (UNUSUAL_TRANSFER | TIMING | AMOUNT_SPIKE)
  ON_CDR: get_severity() -> returns integer (1–5; higher = more suspicious)
  ON_EVAL: flag() -> marks anomaly as investigated; contributes to contract completion
};

Composition Example:

(ACCOUNT "ABC Corp" $50M balance
  (ACCOUNT "Operating" $2M
    (TRANSACTION -$50K "Salary Review" counterparty="employee")
    (TRANSACTION -$20K "Office Rent" counterparty="landlord")
    (ANOMALY TIMING_VIOLATION))
  (ACCOUNT "Tax Reserve" $5M
    (TRANSACTION -$1.5M "IRS Payment" counterparty="government"))
  (ACCOUNT "Cayman Subsidiary" $10M
    (ANOMALY UNUSUAL_TRANSFER)
    (SHELL "Handler LLC" (owner=??))))

Operator navigates with CAR/CDR, inspects with EVAL, flags with QUOTE. Fully navigable financial tree.

3.11 Sound Design as Interface

The YM2149 in BLACK LEDGER serves analytical feedback and suspicion indicators.

Voice 1 (Square Wave, ~800Hz): Baseline integrity. A continuous tone when operator has clean account in view. Frequency represents account stability:

Stable account: steady 800Hz tone
Suspicious account: tone wavers (+/- 50Hz variation)
Highly suspicious: tone drops to 400Hz (ominous)

Voice 2 (Sawtooth, ~400Hz): Transaction flow. Pulses when operator is reviewing transactions:

Legitimate transaction: clean pulse (100ms on/off)
Suspicious transaction: irregular pulse (gaps, stutter)
Anomaly detected: pulse accelerates

Voice 3 (Noise, variable): Alarm. Rare; only triggered when operator is close to exposing major fraud:

First shell identified: brief noise burst (200ms)
Pattern recognized: longer burst (500ms)
Beneficial owner close: sustained noise (scary)

Operational Feedback:

Clean account review: Voices 1+2 are harmonious (calming).
Suspicious pattern: Voice 1 wavers; Voice 2 stutters (building tension).
Anomaly flagged: Voice 3 burst (confirmation).
Fraud exposed: all three voices harmonize in a discordant minor key (dread), then resolve downward (relief).

Not entertainment. Pure investigative tension.

3.12 Link Protocol

Two KN-86 decks running BLACK LEDGER can link for competitive adversarial audits or collaborative investigation.

INVESTIGATOR A Role (Competitive):

Launches a FORENSIC TRACE contract.
Their progress is partially visible to Investigator B (can see shell count, not specifics).
Real-time position updates (which shell level they’re on).

INVESTIGATOR B Role (Competitive):

Sees same case, different starting point.
Cannot see Investigator A’s specific findings.
Can see which shells A has already traced (to avoid duplication).
Can see who’s ahead (progress race).

Data Flow (Competitive):

Investigator A Deck:
  -> shell_traced (shell_id, beneficiary_revealed)
  -> progress_percentage (how far into case)

Investigator B Deck:
  <- competitor_shells_mapped (know which to avoid)
  <- progress_indicator (who's winning)
  -> shell_traced (race to beneficial owner)

Data Flow (Collaborative):

Investigator A Deck:
  -> finding (shell_id, owner, connections)
  -> hypothesis (predicted beneficial owner)

Investigator B Deck:
  <- shared_finding (validates or contradicts)
  <- shared_hypothesis (collaborative analysis)
  -> corroborating_evidence (strengthen case)

Example: Competitive Audit

Two operators independently audit the same corporation. Same case. Different starting accounts.

Operator A (Investigator A): Starts from “Operating Accounts,” finds transfer to Shell X.
Operator B (Investigator B): Starts from “Tax Reserve,” finds transfer to Shell Y.
Race condition: Who traces their shell to the beneficial owner first?
Operator A reaches beneficial owner in 20 turns. Operator B reaches in 18 turns. Operator B wins. Reward: Operator B 2000 ¤ + trophy, Operator A 500 ¤ consolation.

This creates asynchronous competitive dynamics unique to paired modules.

MODULE 4: DEPTHCHARGE — SONAR / SUBMERSIBLE CAPABILITY

4.1 Module Identity

Designation: SONAR / SUBMERSIBLE (MODULE CLASS: 0x04) Publisher: Pacific Rim Dynamics (Yokohama) — Defense Signal Processing Division Profile: Underwater navigation and acoustic intelligence specialist module Operator Role: Submersible drone operator, acoustic analyst, deep-water salvage specialist Deck State Signature: Sets bit 3 in cartridge history bitfield on first load Loading Screen: Sonar sweep animation — radial line rotates clockwise with fading trail. PSG ping on each rotation (descending 2000-400Hz). Company name resolves in sweep center on third rotation. 2.5 seconds.

DEPTHCHARGE transforms the Deckline into an underwater combat and navigation workstation. The operator specializes in drone maneuvering, acoustic sensing, deep-water relay access, evasion, and underwater salvage operations. It is not a game about submarines—it is the operational framework for modeling underwater acoustic intelligence and submersible warfare workflows.

On First Load: The Mission Board generates SONAR SWEEP, SALVAGE, EVASION, and RELAY ACCESS contracts. The operator’s deck is marked as having submersible capability. All future cross-module interactions check this bit: ICE BREAKER SURVEILLANCE implants can be deployed on underwater relay stations; BLACK LEDGER FORENSIC TRACE operations can access underwater financial accounts (submarine shell companies); DEPTHCHARGE’s YM2149 sound becomes a cross-module operational asset. The deck’s sonar display IS the drone’s real-time sensor feed; the operator pilots the submersible remotely from their Deckline terminal at the surface.

4.2 Mission Template Architecture

Contract Classes

Contract Type	Description	Threat Range	Base Payout	Phases
SONAR SWEEP	Map deep-water acoustic signature; locate target or hazard	1–3	400–1200 ¤	1
SALVAGE	Recover specific object/data from seabed; manage risk vs. visibility	2–4	800–2400 ¤	2–3
EVASION	Evade surface hunter or rival drone operator; silence disciplines	2–5	1000–3500 ¤	1–2
RELAY ACCESS	Reach undersea communications relay; extract/corrupt data	3–4	1500–3000 ¤	2–3

Template Structure (Procedural Generation)

SONAR SWEEP Contract:

survey_area: 2D depth map (x = horizontal position, y = depth)
target_signature: acoustic fingerprint (frequency, duration, pattern)
background_noise: environmental interference (shipwreck sonar, whale sounds, thermal vents)
operator_task: move drone, ping sonar, identify target among noise
pings_available: 5–10 active sonar pings (each ping reveals some information, but creates noise/exposure)
time_limit: 15–25 turns
threat_level: 1–3 (higher threat = more interference, more hidden objects)
reward: 300 + (pings_used_efficiently × 50) ¤
rep_gain: +1 per successful target identification; -0.5 per wasted ping

Example: Operator searches for downed relay station. Background includes whale clicks, thermal vent rumble, and 3 shipwrecks with similar acoustic profiles.

Ping 1: Broad sweep. Operator hears 4 possible signatures.
Ping 2: Narrow band, 2kHz. Eliminates whale noise.
Ping 3: Focused on suspected area. Relay station found!
Payout: 300 + (3 × 50) = 450 ¤. Rep +3.

SALVAGE Contract:

target_object: data cache, equipment, or artifact at depth d
depth_range: 1–5 (deeper = higher pressure, higher difficulty, higher reward)
recovery_method: net (fast, loud), grabber (slow, silent), cutting torch (very loud, very fast)
time_pressure: salvage has timeout (object degrades if left at depth too long)
security_risk: rival drone operators may detect operation (if you're loud)
operator_task: choose method, navigate to depth, extract object, return to surface
threat_level: 2–4 (depends on depth and method choice)
reward: 500 + (depth × 300) ¤
rep_gain: +1 per depth level; +2 bonus if silent operation (no detection)
complication: if ICE BREAKER in history, relay stations at depth may have ICE defense; requires ICE phase first

Example: Salvage a $2M data cache at depth 4. Operator chooses net (fast): descend, grab, ascend in 6 turns. Loud operation; rival drone operator detects noise (threat escalates to 4). Operator must evade or fight. Risk vs. reward decision in real-time.

EVASION Contract:

pursuer: surface hunter (noisy, fast, limited depth) OR rival drone operator (quiet, smart, deep-capable)
operator_task: escape pursuit; silence disciplines critical
evasion_mechanics: slowing engines reduces detection, but slows movement; defensive maneuvers (tight turns) create acoustic signature
hiding_spots: thermal vents, shipwrecks, shallow water (hunter can't follow)
time_limit: 10–20 turns
threat_level: 2–5 (depends on pursuer intelligence)
reward: 700 + (turn_efficiency × 100) ¤
rep_gain: +3 per successful evasion; -2 if caught
complication: if BLACK LEDGER in history, underwater financial networks may be under surveillance; evasion creates audit trail

RELAY ACCESS Contract:

relay_station: undersea communications hub at depth 3–4
security: ICE defense, physical locks, acoustic alarm (triggers if broken carelessly)
operator_task: access relay, extract intelligence or corrupt data
data_extraction: same as ICE BREAKER EXTRACTION (data size, threat, time window)
acoustic_exposure: each action creates sonar signature; cumulative exposure increases hunter arrival risk
time_limit: 10–15 turns before hunter response
threat_level: 3–4 (highest in DEPTHCHARGE; combines acoustic exposure + data security)
reward: 1500 + (data_extracted × 200) ¤
rep_gain: +3 per successful relay access; -3 if detected and hunted
complication: if ICE BREAKER in history, relay may have dual security (physical + ICE); requires both modules

4.3 Deck State Integration

SRAM Writes:

knowledge_index not affected (DEPTHCHARGE is not epistemic)
logic_index increments by 1 per successful EVASION (rewards decision-making under pressure)
credit_balance increases moderately to heavily (DEPTHCHARGE pays 400–3500 ¤ per contract)
reputation_score increases with depth, evasion success, silent operations
cartridge_history bit 3 set permanently
NEW: acoustic_signature (2 bytes) — hidden stat encoding operator’s acoustic footprint. Accumulated based on how “loud” their operations are. Higher signature = more likely to be detected. Can be reduced by high-proficiency silent ops.

Reputation Thresholds (DEPTHCHARGE Context):

Rep 0–4: Shallow water only (depth 1–2). SONAR SWEEP contracts. Threat max 1.
Rep 5–14: Intermediate depth (depth 3). SALVAGE begins. Threat max 3.
Rep 15–24: Deep water (depth 4). EVASION becomes common. Acoustic awareness critical.
Rep 25–49: Extreme depth (depth 5). RELAY ACCESS available. Rival drone operator encounters.
Rep 50+: EXCLUSIVE contracts: DEEP ARCHAEOLOGY (recover ancient submarine artifacts), ACOUSTIC WARFARE (warfare between 3+ submersible drone operators), SILENT PROTOCOL (impossible evasion challenge).

4.4 Cross-Module Interactions

With ICE BREAKER (Network Intrusion):

RELAY ACCESS contracts can be ICE-defended. Requires 2-phase: DEPTHCHARGE phase 1 (navigate to relay), ICE BREAKER phase 2 (hack into relay).
ICE on relay has depth-dependent difficulty: deeper relays have more advanced ICE.
Reward increases 50% if both phases complete cleanly.

With BLACK LEDGER (Forensic Audit):

RELAY ACCESS can expose underwater financial networks (submarine accounts).
FORENSIC TRACE missions can target depth 5 “deep financial havens.”
Special mission type: MONEY RUNNING—smuggle cash via submersible drone while evading audit detection.
If caught during EVASION: automatic BLACK LEDGER phase 2 to cover the trail.

With NEONGRID (Grid Traversal):

SONAR SWEEP mapping uses same grid patterns as NEONGRID navigation.
Operator with NEONGRID proficiency 50+: reads sonar patterns more intuitively (SONAR SWEEP threat -1).
Acoustic signature management: high NEONGRID proficiency allows more efficient depth movements (lower acoustic cost).

Self-Reference:

Solo DEPTHCHARGE: pure underwater operations.
Paired with ICE BREAKER: underwater hacking missions unlock.
Paired with BLACK LEDGER: financial evasion and deep-water money operations unlock.

4.5 Multi-Phase Mission Design

Phase Architecture

DEPTHCHARGE phases are sequential depth-dependent operations. Each phase takes operator deeper, with accumulated acoustic signature.

Example 2-Phase: SONAR SWEEP + SALVAGE (Archaeological Dive)

Phase 1 (DEPTHCHARGE):

SONAR SWEEP at depth 2. Locate ancient submarine wreck.
Threat 1, payout 400 ¤.
Operator uses 5 pings, locates wreck efficiently.
Phase chain write: phase=1, mission=ARCHAEOLOGY_DIVE, target=wreck_id_47, acoustic_signature=+2.

Phase 2 (DEPTHCHARGE):

SALVAGE the wreck. Recover data cache from depth 4.
Threat 3, higher complexity.
Operator has already “announced” presence via Phase 1 pings; acoustic signature is +2 (elevated).
Rival drone operator may detect operation (15% chance, +1% per turn in Phase 2).
Operator chooses salvage method: silent (slow, 8 turns), loud (fast, 4 turns but +acoustic signature).
Payout: 500 + (depth 4 × 300) = 1700 ¤.
Rep gain: +1 (depth) + 2 (silent operation bonus) = +3.

Total: 2100 ¤, rep +4. Acoustic signature: +2 (lingers; increases detection risk in next DEPTHCHARGE mission).

Example 3-Phase: RELAY ACCESS (Full Underwater Infiltration)

Phase 1 (DEPTHCHARGE):

SONAR SWEEP to locate relay station at depth 3.
Threat 1, payout 400 ¤.
Phase chain: phase=1, mission=RELAY_INFILTRATION, relay_id=relay_77, acoustic_signature=+1.

Phase 2 (DEPTHCHARGE or ICE BREAKER):

Navigate to relay, dock (DEPTHCHARGE phase 2a: 5 turns of silent approach, acoustic signature +1 per turn if active).
OR if ICE BREAKER in history: require ICE BREAKER phase 2 to disable relay’s ICE defense first.
Threat 2 (DEPTHCHARGE acoustic challenge) or threat 3 (ICE BREAKER security).
Payout: 800 ¤ (DEPTHCHARGE) or 900 ¤ (ICE BREAKER).

Phase 3 (BLACK LEDGER optional):

Extract relay intelligence: financial data, communication logs, relay network map.
If BLACK LEDGER in history: operator audits extracted data, reconstructs financial network using relay.
Threat 2–3, payout 1500–2000 ¤.

Total (all three phases): 2700–3700 ¤, rep +8. Acoustic signature: +4 (very hot; next DEPTHCHARGE operation has detection risk).

4.6 Capability Progression

NOT difficulty levels, but drone piloting mastery and acoustic awareness.

Rep 0–4 (Drone Trainee):

Depth access: 1–2 only (safe, shallow).
Deck capability: 3 active operations per session.
Mastery: learning sonar interpretation, basic evasion.
Acoustic signature management: not relevant yet.
Audio feedback: Cipher voice is instructive. Sonar pings are clear, high-fidelity.

Rep 5–14 (Drone Pilot):

Depth access: 3 (intermediate).
Deck capability: 5 active operations.
Mastery: understanding acoustic signatures, choosing salvage methods wisely.
Acoustic signature: becomes visible stat; operator learns to manage it.
Audio feedback: Cipher voice becomes tactical. Sonar pings are more nuanced (operator must filter noise).

Rep 15–24 (Drone Commander):

Depth access: 4 (deep).
Deck capability: 10 active operations; 2 concurrent evasions.
Mastery: predicting rival drone operator behavior, silent operational discipline.
Acoustic signature: hidden; operator must estimate (creates tension).
Audio feedback: Cipher voice is collegial; treats operator as peer commander. Sonar is pure data; operator must interpret.

Rep 25–49 (Legendary Pilot):

Depth access: 5 (extreme).
Deck capability: unlimited; multi-cartridge underwater campaigns.
Mastery: writing custom evasion patterns, teaching acoustic warfare to other operators.
Acoustic signature: fully transparent; operator can predict detection probability per action.
Audio feedback: Cipher voice is rare; mostly sonar silence. When it speaks, it offers strategic insights.

Rep 50+ (Silent Legend):

Depth access: EXCLUSIVE deep (6+), forbidden depths.
Deck capability: government/corporate contracts.
Mastery: acoustic stealth is automatic; focus shifts to strategic objectives.
Acoustic signature: operator is a ghost; most operations leave no detectable trace.
Audio feedback: Cipher voice is mythical. “You are the silence. Fear you, the deep.”

4.7 Contract Economics

Base Payout Formula:

base_reward = threat_level × 250 ¤ (DEPTHCHARGE baseline is depth-weighted)
depth_bonus = depth_level × 200 ¤ (reward scales with risk)
acoustic_efficiency = (pings_saved × 50) + (silent_operations × 100) ¤
method_multiplier = 1.2 (silent) | 1.0 (standard) | 0.8 (loud)
final_payout = (base_reward + depth_bonus + acoustic_efficiency) × method_multiplier

Examples:

Threat 1 SONAR SWEEP, depth 2, 4/5 pings used efficiently, standard method: (250 + 400 + 50) × 1.0 = 700 ¤
Threat 3 SALVAGE, depth 4, silent method: (750 + 800 + 0) × 1.2 = 1860 ¤
Threat 4 EVASION, depth 5, loud (necessary for escape), 1 turn remaining: (1000 + 1000 + 0) × 0.8 = 1600 ¤
Threat 5 RELAY ACCESS, depth 5, silent approach + ICE breach, 8/15 turns: (1250 + 1000 + 350) × 1.2 = 3540 ¤

Risk/Reward Curve:

Threat	Base Reward	Failure Rep Hit	Rep Gain (Success)	Operator Profitability
1	250 ¤	-0.5	+1	200–300 ¤
2	500 ¤	-1.5	+2	350–700 ¤
3	750 ¤	-2	+3	500–1200 ¤
4	1000 ¤	-2.5	+4	700–1800 ¤
5	1250+ ¤	-3	+5	1000–3500+ ¤

Exclusive High-Rep Operations:

DEEP ARCHAEOLOGY (rep 50+): 8000 ¤ + ancient artifact (permanent deck upgrade). 12-hour real-time mission.
ACOUSTIC WARFARE (rep 40+): 3-way submersible duel (linked play with 2 other operators). Winner: 4000 ¤ + trophy. Loser: -1000 ¤ + reputation -3.
SILENT PROTOCOL (rep 50+): impossible evasion scenario. Reward 5000 ¤ if successful, reputation +5. Failure: reputation -5, cost 1000 ¤.

4.8 Operator Workflow

A Typical DEPTHCHARGE Session:

Pre-Dive Briefing (2 min): Operator loads DEPTHCHARGE, checks weather (environmental interference), reviews available contracts. Cipher voice provides tactical situation report.
Depth & Approach (3 min): Operator selects depth and target. Drone descends; acoustic signature accumulates slightly (+1 per depth level).
Active Mission (15–25 min depending on contract):
- SONAR SWEEP: operator pings strategically, filters noise, locates target (5–10 pings).
- SALVAGE: operator maneuvers to target, chooses recovery method (silent/standard/loud), executes extraction.
- EVASION: operator evades detection; real-time pursuit; audio cues critical.
- RELAY ACCESS: operator docks, hacks relay (if required), extracts data, escapes.
Ascent & Debrief (3 min): Drone surfaces. Cipher voice analyzes operation. Acoustic signature disclosed. Payout awarded. Reputation adjusted.
Transition (1 min): Operator either queues another DEPTHCHARGE mission or swaps cartridge.

Multi-Session Campaign (Multi-Module):

An operator with DEPTHCHARGE + ICE BREAKER + BLACK LEDGER might pursue a corporate espionage campaign:

Session 1 (DEPTHCHARGE, 20 min): Locate underwater relay station, navigate to depth 4, dock silently.
Session 2 (ICE BREAKER, 20 min): Hack relay’s ICE defense, extract financial data.
Session 3 (BLACK LEDGER, 25 min): Audit extracted data, reconstruct corporate financial network.
Payout: Session 1: 1200 ¤. Session 2: 1500 ¤. Session 3: 2500 ¤. Total: 5200 ¤. Rep: +9.

This is the corporate intelligence sweep—obtain, crack, analyze.

4.9 Cipher Voice Integration

Cipher’s tone in DEPTHCHARGE: tactical drone pilot, increasingly mystical about the depths.

On Load:

“Drone systems online. Pressure hull nominal. Ballast ready. Standing by for depth target, Operator.”

During SONAR SWEEP:

“Pinging. Listen to the returns. That signature at bearing 270 is your target. You’re getting close.”

Rival Drone Operator Detected:

“Contact. Another operator in the area. They’ve heard you. You have three options: dive deeper, run silent, or turn to engage. Choose.”

During EVASION (Pursuit Intensifies):

“They’re tightening the noose. You can lose them if you go dark—full silence—but you’ll be blind. No sonar. No sensors. Trust your nerve?”

During RELAY ACCESS:

“You’re at the relay. Physical dock locked. ICE is active. We have approximately 10 turns before the hunter arrives. Work fast.”

On Successful Evasion:

“You’re clear. You disappeared into the noise like a ghost. Well done, Operator.”

On Detection/Capture:

“They’ve got a lock on you. Torpedo inbound in 3 turns. Prepare for impact. Or accept capture. Your choice.”

High Rep, Mystical Comments:

“The deep has a rhythm. You’ve learned it. Now you’re part of it. The deep trusts you now. That’s rare.”

Rep 50+ debrief:

“You’ve heard the voice of the abyss and answered. The pressure that would crush other operators—it transforms you. You are becoming something else. Something silent. Something necessary.”

4.10 Cell Architecture

DEPTHCHARGE defines the depth/sonar primitive:

CELL_TYPE DEPTH {
  ON_CAR: get_pressure() -> returns pressure_bar (1–5; higher = more danger)
  ON_CDR: descend_deeper() -> returns DEPTH (next level down)
  ON_EVAL: ping_sonar() -> returns SONAR_RETURN list
};

CELL_TYPE SONAR_RETURN {
  ON_CAR: get_signature() -> returns frequency + duration (acoustic fingerprint)
  ON_CDR: get_bearing() -> returns compass bearing (0–359)
  ON_EVAL: investigate() -> reveals object type (target, shipwreck, thermal vent, rival drone operator)
};

CELL_TYPE DRONE {
  ON_CAR: get_position() -> returns (bearing, depth)
  ON_CDR: move_drone() -> changes position, generates acoustic signature
  ON_EVAL: perform_action() -> deploy tool, extract data, engage target
};

CELL_TYPE ACOUSTIC_OBJECT {
  ON_CAR: get_type() -> returns SYMBOL (RELAY_STATION | SALVAGE | RIVAL_SUB)
  ON_CDR: get_related_objects() -> returns nearby objects
  ON_EVAL: interact() -> access relay, grab salvage, or engage in evasion
};

Composition Example:

(DEPTH 3 pressure=3bar
  (SONAR_RETURN signature=2.1kHz bearing=270
    (ACOUSTIC_OBJECT RELAY_STATION
      (ICE_DEFENSE threat=3)
      (FINANCIAL_DATA size=4096)))
  (SONAR_RETURN signature=4.5kHz bearing=90
    (DRONE rival_operator="unknown"
      (POSITION bearing=95 depth=3)
      (INTENTION evasion | pursuit | standoff?)))
  (SONAR_RETURN signature=thermal_vent bearing=180
    (REFUGE quiet=high)))

Operator navigates with CAR/CDR, pings with EVAL, manages drone position with CONS. Fully navigable acoustic environment.

4.11 Sound Design as Interface

The YM2149 is THE interface in DEPTHCHARGE. Visuals are secondary. Sound is truth.

Voice 1 (Square Wave, 400–2000Hz variable): Sonar pings and returns. Operator sends pings; Cipher answers with acoustic signatures.

Operator pings: brief high-frequency chirp (3kHz, 50ms).
Sonar return: complex tonal profile that encodes object type, distance, bearing.
- Relay station: sustained 2.1kHz + harmonic overtones
- Rival drone: 1.5kHz pulse with signature noise (engine signature)
- Thermal vent: chaotic 3–5kHz white noise + bass rumble
- Shipwreck: metallic clangs + acoustic echoes

Voice 2 (Sawtooth, 200–800Hz variable): Drone thruster. Continuous bass tone represents engine throttle:

Stationary (ballast): 200Hz slow pulse (1 Hz frequency)
Cruising silent: 300Hz very slow pulse (0.5 Hz), low amplitude
Active (maneuvering): 500Hz pulse (2 Hz), medium amplitude
Full power (evasion): 800Hz pulse (4+ Hz), loud

Operator learns to “throttle” by listening to engine tone. Silent operations = barely audible engine.

Voice 3 (Noise, variable): Environmental interference and ambient ocean sounds.

Clear water: minimal noise
Thermal vent area: constant white noise (interference)
Shipwreck area: metallic creaks + acoustic echoes (multipath propagation)
Rival drone nearby: their engine signature bleeds through (warning)

Operational Feedback:

Descent: all three voices begin; bass (Voice 2) deepens as pressure increases.
Sonar ping: brief silence, then Voice 1 returns with acoustic echo (information-rich).
Silent approach: Voices 2+3 barely perceptible (operator must listen intently).
Evasion: Voice 2 (engine) becomes aggressive pulse; Voice 3 (interference) builds chaotically; Voice 1 (rival sub sonar) rings out like a hunter’s call.
Escape success: voices resolve to calm silence (relief).
Capture: all voices cut out suddenly (blackness).

Accessibility via Sound Alone:

An expert operator can run DEPTHCHARGE with eyes closed. Sonar returns are distinct acoustic patterns. Engine management is felt/heard. Evasion success is determined by audio cues alone.

4.12 Link Protocol

Two KN-86 decks running DEPTHCHARGE engage in asymmetric submersible drone warfare or cooperative operations.

OPERATOR A Role (Attacking Drone):

Launches mission: SALVAGE, RELAY ACCESS, or offensive EVASION.
Their position is hidden from OPERATOR B initially.
Can emit sonar pings (each ping reveals their position to OPERATOR B).
Objective: complete mission, escape without being hunted down.

OPERATOR B Role (Hunter/Defender):

Listens for OPERATOR A’s acoustic signature.
Can respond with sonar pings, deploy countermeasures, or pursuit.
Objective: intercept OPERATOR A, disrupt their mission, or force negotiation.

Data Flow:

Operator A Deck:
  -> sonar_ping (reveals position)
  -> acoustic_signature (engine, movement, tools)
  -> mission_progress (depth reached, time remaining)

Operator B Deck:
  <- acoustic_return (Operator A's signature)
  <- position_estimate (triangulated from pings)
  <- threat_assessment (is A a threat or neutral?)
  -> hunter_response (sonar counter-ping, pursuit vector, offer to negotiate)

Linked Example: Tense Standoff

Scenario: Operator A attempts RELAY ACCESS at depth 4. Operator B detects them.

Turn 1: Operator A pings to locate relay. Operator B hears ping; estimates bearing 270, depth 4.
Turn 2: Operator A navigates silently (engine quiet). Operator B launches counter-ping to confirm position. Operator A hears it—they’re detected.
Turn 3: Operator A has two choices: abort mission (embarrassing), or accept combat risk and continue.
Turn 4: Operator A reaches relay, begins hacking (takes 5 turns, but each turn = more acoustic exposure).
Turn 5–8: Operator B closes range, launches evasion maneuvers to trap Operator A.
Turn 9: Operator A completes hack (extracts data), pings to locate Operator B’s position.
Turn 10: Chase begins. Operator A flees toward thermal vent (acoustic cover). Operator B pursues.
Turn 12: Operator A reaches vent, goes silent. Operator B loses track in the noise.
Result: Operator A escapes with data (mission success). Reward: 2000 ¤ (mission) + 500 ¤ (evasion bonus) = 2500 ¤. Operator B: 400 ¤ (for detecting and pursuing; attempted intercept counts as partial success).

This creates asymmetric tension: one operator is hunter, one is hunted. Roles are fluid if they meet again.

CONCLUSION: ECOSYSTEM INTEGRATION

Cross-Module Synergies

The four launch modules form an integrated operational ecosystem. No single module is “complete” alone; together, they enable complex multi-phase missions and emergent gameplay strategies.

Example Campaign: “The Cayman Spiral”

A veteran operator with all 4 modules pursues a 5-phase corporate espionage operation:

DEPTHCHARGE Phase 1 (Drone Locates Relay): Navigate to underwater relay station. Threat 2, payout 600 ¤.
ICE BREAKER Phase 1 (Hack Relay ICE): Disable relay security. Threat 3, payout 1200 ¤.
BLACK LEDGER Phase 1 (Extract Financial Data): Audit relay records, identify shell company network. Threat 2, payout 1500 ¤.
BLACK LEDGER Phase 2 (Forensic Trace): Follow money through 8 shells to Cayman account. Threat 4, payout 3000 ¤.
DEPTHCHARGE Phase 2 (Evasion): Corporate hunter submarine pursues operator after financial breach detected. Threat 5, payout 3000 ¤.

Total Payout: 9300 ¤. Rep Gain: +15. Acoustic Signature: +6 (operator is very hot; future DEPTHCHARGE missions have 25% detection risk). Corporate Reputation Damage: immense (in-universe); operator becomes marked target.

This is late-game content: only possible with all modules, high rep, coordinated multi-phase planning, and acceptance of high risk.

The Persistent Deck

The Universal Deck State is the true protagonist. The operator is secondary. The deck—with its cartridge history, reputation, credit balance, acoustic signature, proficiency vector—is what evolves across all modules and all time.

Operators come and go (cartridge loads), but the deck endures, accumulating history, reputation, and personality through repeated operations.

By rep 50+, an operator’s deck is legendary:

Known to all other operators (via link cable culture).
Marked by hunters (ICE, submarines, corporate security).
Trusted by some, feared by others.
Capable of orchestrating operations impossible for lower-rep decks.

This is the long game: not victory, but legacy.

END OF CAPABILITY MODEL

Document Version 1.0 Kinoshita Consumer Electronics Design Archive KN-86 Deckline Launch Lineup (1988)