KN-86 Commerce & Navigation Modules — Full Gameplay Specifications

Three Capability Modules for the Kinoshita KN-86 Deckline

Version 1.0 | April 2026

CIPHER-LINE revision note (2026-04-24): Every “Cipher voice” quotation in this spec renders on the CIPHER-LINE OLED above the keyboard, not the main 80×25 grid. The full-sentence Cipher examples (e.g., “Markets are volatile today. Three contracts available.”) are illustrative of intent; actual CIPHER-LINE rendering is clipped fragments per the voice heuristic (e.g., volatile. three on board. / thin.). For vocabulary, productions, and mode-weight biases per module, see the standalone gameplay specs (SynthFence, Drift, Pathfinder) and docs/software/runtime/cipher-voice.md.

MODULE 1: SYNTHFENCE — MARKET OPERATIONS

1.1 Module Identity

Designation: MARKET OPERATIONS (MODULE CLASS: 0x06) Publisher: Meridian Systems (Hong Kong) Profile: Futures trading floor, commodity arbitrage, market manipulation detection Operator Role: Volatility trader, arbitrage specialist, market analyst Deck State Signature: Sets bit 5 in cartridge_history bitfield on first load Loading Screen: Global trade aesthetic. Screen fills rapidly with a scrolling stock ticker (real Hong Kong/Tokyo/Singapore exchange symbols, ASCII art). Price deltas flash in amber against black. A clean Meridian Systems wordmark assembles in the center over the chaos. Audio: rapid keyboard clicks, then three synthetic chords (C major, played by YM2149 all three voices in unison). 3.2 seconds total. No error messages. Pure efficiency.

SYNTHFENCE transforms the Deckline into a real-time trading terminal. The operator specializes in reading price feeds, executing commodity futures trades, detecting artificial market manipulation, and executing arbitrage across fragmented markets. This is not simulation—it is the functional framework for high-frequency financial operations. The screen is a Bloomberg terminal reimagined for an 80×25 amber terminal: price tickers, order books, profit/loss in real time, threat detection (regulatory alerts, manipulation traps).

On First Load: The Mission Board generates ARBITRAGE, VOLATILITY CAPTURE, MANIPULATION DETECTION, and FLASH TRADING contracts. The operator’s deck is marked as having market operations capability. All future cross-module interactions check this bit: BLACK LEDGER FORENSIC TRACE contracts now include market data trails; ICE BREAKER sabotage of financial networks triggers market collapse scenarios.

1.2 Mission Template Architecture

Contract Classes

Contract Type	Description	Threat Range	Base Payout	Phases
ARBITRAGE	Buy low in one market, sell high in another; lock in spread	1–2	800–2000 ¤	1–2
VOLATILITY CAPTURE	Time price swings; execute buy-low/sell-high pairs under time pressure	2–3	1200–2800 ¤	1–2
MANIPULATION DETECTION	Identify artificial price movement; trace to market manipulator; report	2–4	1500–3500 ¤	2–3
FLASH TRADING	Execute high-frequency trades in microsecond windows; outpace competitors	3–4	2000–5000 ¤	1–2

Template Structure (Procedural Generation)

ARBITRAGE Contract:

market_pair: (source_market, target_market) e.g., (Hong_Kong_Exchange, Singapore_Exchange)
commodity: energy | metals | agriculture | currency_pair
current_bid: random price within realistic range (e.g., crude oil $45–55/barrel)
current_ask: current_bid + random spread (e.g., $0.30–$0.75/barrel)
target_ask: current_ask × random markup (1.015 to 1.035 = 1.5%–3.5% gross spread)
order_size: 100–5000 units (operator chooses contract size; larger = higher risk if margin call)
time_limit: 8–15 turns (market moves continuously; window closes)
threat_level: 1–2 (low regulatory pressure; straightforward execution)
margin_requirement: 10%–20% of order value (ties up credit balance)
reward_formula: (target_ask - current_ask) × order_size × 100 ¤ base + speed_bonus
rep_gain: +0.5 per successful arbitrage; -1 if margin call triggered
complication: if DEPTHCHARGE in history, can arbitrage underwater/submarine commodity flows

Example: Crude Oil Arbitrage

Hong Kong spot price: $48.50/barrel, 500 barrel contract
Singapore bid: $48.75/barrel (current spread: $0.25)
Operator’s target: $49.10/barrel (gross spread: $0.60 per barrel)
Margin lock: 10% × (48.50 × 500) = 2425 ¤ tied up
Operator executes BUY at 48.50, immediately queues SELL at 49.10
Market cooperates: Singapore prices move to 49.10 within 4 turns
Profit: 0.60 × 500 = 300 ¤ gross; minus 2425 margin lock release = 300 ¤ net
Rep: +0.5 (small but reliable)

VOLATILITY CAPTURE Contract:

price_oscillation: price swings by random ±2%–±8% per turn (faster at higher threat)
observation_window: 3–5 turns before operator must act
operator_task: predict the swing direction; buy at predicted low; sell at predicted high
decision_point: use INFO keypress to read price history (last 10 turns); predict next swing
timing_precision: if operator catches within ±1 tick, reward ×1.5; if catches ±2 ticks, ×1.0; if misses window, ×0.5
time_limit: 12–20 turns (market accelerates; pressure increases)
threat_level: 2–3 (regulatory watches volatility trading for manipulation)
order_size: 200–3000 units
reward_formula: (peak_price - buy_price) × order_size × 100 ¤ + volatility_bonus (if caught within ±1 tick)
rep_gain: +1 per successful volatility capture; -2 if operator times it poorly (catches wrong direction)

Example: Energy Volatility

Turn 1–3: Price oscillates $50–$52 (minor swings)
Turn 4: Price spikes to $55 (operator detects pattern; INFO reveals: strong upward momentum)
Turn 5: Operator decides this is the spike peak; SELLS predicted position
Turn 6–8: Price corrections to $52, then to $48 (operator was right)
Profit: ($55 − $48) × 1500 units × 100 ¤ = massive payout (operator caught the wave perfectly)
Rep: +2 (high-skill timing)

MANIPULATION DETECTION Contract:

market_scenario: artificial price movement (pump-and-dump, spoofing, layering)
operator_task: identify the manipulation pattern; trace to manipulator; gather evidence
evidence_layers: 4–8 data points that form a coherent manipulation narrative
analysis_framework: use CDR to traverse time series; use INFO to zoom into suspicious clusters; use QUOTE to mark evidence
time_limit: 15–25 turns (investigation-paced, not action-paced)
threat_level: 2–4 (if you report manipulation, regulatory retaliation may follow)
reward_formula: 1500 ¤ base + (evidence_points_gathered × 200) ¤ + (manipulator_reputation_damage × 50) ¤
rep_gain: +2 per evidence point; +5 bonus if manipulator is correctly identified
complication: if BLACK LEDGER in history, operator can trace manipulator's shell companies
complication: if ICE BREAKER in history, operator can detect defensive ICE protecting manipulation evidence

Example: Spoofing Detection

Operator observes XYZ commodity price at $75
Large buy orders appear (500+ units) → price jumps to $78
Orders suddenly cancel → price crashes to $74
Pattern repeats 3 times in 12 turns
Operator marks: (1) fake buy order, (2) price spike, (3) order cancellation, (4) price crash
Four evidence points gathered; operator concludes: “Spoofing pattern detected”
Operator uses CDR to navigate market data and finds: all orders originate from “Phantom Capital LLC”
Reward: 1500 + (4 × 200) + (reputation_damage bonus) = 2300+ ¤
Rep: +13 (high investigation skill)

FLASH TRADING Contract:

high_frequency_scenario: multiple markets operating in parallel; price quotes update every 0.5–1.0 turns
operator_task: execute rapid-fire trades (buy/sell pairs) to lock in microsecond arbitrage windows
time_pressure: extreme; each turn advances market state; delays cost money
decision_speed: operator must CAR into order book, select price, EVAL to execute; all within 1–2 game turns
competitor_pressure: if ICE BREAKER in history, defensive systems may slow order routing
order_queue: 5–10 trades must execute in sequence; missing one breaks the chain
time_limit: 10–15 turns (very short, very intense)
threat_level: 3–4 (regulators are watching flash trading for market manipulation)
reward_formula: (spread_width × order_size × trades_executed) × 100 ¤ + speed_bonus (complete all trades within time limit)
rep_gain: +2 per successful trade in sequence; -1 per failed trade (missed window)
penalty: if trades break chain (one fails), entire contract fails (cascading loss)

Example: Flash Trading Sequence

Turn 1: BUY 1000 units at $100.00 (locked)
Turn 2: SELL 1000 units at $100.05 (profit: $50)
Turn 3: BUY 500 units at $99.95 (market corrects)
Turn 4: SELL 500 units at $100.10 (profit: $75)
Turn 5: BUY 750 units at $100.00 (third wave)
Turn 6: SELL 750 units at $100.08 (profit: $60)
All trades executed within 6 turns; total profit: $185 base + speed bonus = 250+ ¤
Rep: +6 (three successful rapid trades)

1.3 Deck State Integration

SRAM Writes:

credit_balance — updated in real-time as trades execute; can increase significantly (2000–5000 ¤) or decrease rapidly (margin calls, failed arbitrage)
reputation_score — increases moderately per successful trade (+0.5 to +2 depending on contract complexity)
volatility_index NEW — hidden stat tracking operator’s exposure to market chaos; ranges 0–100; at 75+, regulatory contracts appear; at 100, market crash scenario triggered
cartridge_history bit 5 set permanently
audit_log — BLACK LEDGER can query this to track money flows post-SYNTHFENCE

Reputation Thresholds (SYNTHFENCE Context):

Rep 0–4: ARBITRAGE only. Simple market pairs. Single commodity. No manipulation contracts.
Rep 5–14: VOLATILITY CAPTURE added. Two-commodity trades. Price swings ±2%–±4%.
Rep 15–24: MANIPULATION DETECTION added. Real market data trails. Simple spoofing detection.
Rep 25–49: FLASH TRADING added. High-frequency multi-market scenarios. Complex manipulation patterns (layering, front-running).
Rep 50+: EXCLUSIVE: MARKET CRASH SCENARIO (largest volatility spike in history; operator profits during chaos or loses everything), REGULATORY EVASION (hide manipulation evidence from authorities), CORPORATE SABOTAGE (coordinate market crashes with ICE BREAKER sabotage of financial systems for maximum impact).

1.4 Cross-Module Interactions

With BLACK LEDGER (Forensic Audit):

FORENSIC TRACE contracts can include “market data forensics”—trace money flows through commodity trades.
2-phase mission: execute suspicious trades in SYNTHFENCE → audit the money in BLACK LEDGER.
Special mission: MONEY LAUNDERING—use commodity arbitrage to obscure transaction origins.
Reward: +50% if both phases successful; operator becomes known for “laundering via commodity trades.”

With ICE BREAKER (Network Intrusion):

ICE BREAKER SABOTAGE contracts targeting financial networks trigger SYNTHFENCE phase 2: MARKET DISRUPTION (sabotage exchange systems → execute flash trades into the resulting chaos).
2-phase: disable exchange ICE → execute rapid trades while market is confused (market data stale, orders execute at advantageous rates).
Special mission: FLASH CRASH TRIGGER—cause artificial market crash via coordinated ICE sabotage + flash trading volume.
Reward: +60% payout if both phases timed precisely.

With DEPTHCHARGE (Sonar/Maritime):

ARBITRAGE contracts can target “underwater commodity flows”—submarine resource shipments (rare metals, oil).
2-phase: use DEPTHCHARGE sonar to locate shipment → execute SYNTHFENCE trades predicting delivery timing.
Special mission: PIRACY ARBITRAGE—detect underwater shipment routes; trade in advance of delivery; profit from supply chain disruption.
Operator with DEPTHCHARGE in history: can arbitrage submarine accounts (hidden from normal markets); exclusive high-payout VOLATILITY CAPTURE contracts appear.

With PATHFINDER (Route Planning):

ARBITRAGE contracts include “geographic arbitrage”—prices vary by delivery location.
2-phase: plan delivery route in PATHFINDER → execute arbitrage in SYNTHFENCE based on route timing.
Special mission: SUPPLY CHAIN ARBITRAGE—predict delivery delays; trade commodity futures accordingly.
Operator with PATHFINDER in history: ARBITRAGE difficulty reduced (can visualize supply chain delays).

Self-Reference:

Solo SYNTHFENCE: pure trading, no operational complications.
Paired with BLACK LEDGER: money laundering via commodities.
Paired with ICE BREAKER: market sabotage + chaos trading.
Paired with DEPTHCHARGE: underwater commodity markets.
Paired with PATHFINDER: geographic supply chain arbitrage.

1.5 Multi-Phase Mission Design

Phase Architecture

SYNTHFENCE supports two primary phase structures:

LINEAR PHASES (Arbitrage → Settlement):

DISCOVERY: Operator scans market feeds; identifies price spread.
EXECUTION: Operator executes buy/sell sequence.
SETTLEMENT: Orders settle; credits transfer; profit/loss calculated.

INVESTIGATION PHASES (Manipulation Detection → Reporting):

EVIDENCE GATHERING: Operator analyzes market data; marks suspicious patterns.
CORRELATION: Operator traces evidence to source (manipulator identity).
REPORTING: Operator files regulatory report; receives reward if evidence is solid.

Worked Example 1: Simple Arbitrage (2-Phase)

Mission: “TOKYO-MUMBAI CRUDE ARBITRAGE”

Operator needs to profit from price differential between Tokyo and Mumbai exchanges
Phase 1 (DISCOVERY): Scan price feeds; identify spread
- Tokyo spot: $48.20/barrel
- Mumbai bid: $48.95/barrel
- Operator marks: 0.75/barrel gross spread
Phase 2 (EXECUTION): Execute buy in Tokyo, sell in Mumbai
- Buy 1000 barrels at 48.20 (tied capital: $48,200)
- Sell 1000 barrels at 48.95 (profit: $750 gross)
- Minus margin lock 10% = $750 net
- Settlement: +750 ¤, rep +1

Duration: 8 game turns (2–3 minutes real time)

Worked Example 2: Manipulation Detection + Reporting (3-Phase)

Mission: “TUNGSTEN SPOOFING INVESTIGATION”

Operator detects artificial price movement; must gather evidence and report
Phase 1 (OBSERVATION): Scan price data; spot suspicious pattern
- Turn 1–3: Tungsten oscillates $120–$122 (normal volatility)
- Turn 4: Large buy order (5000 units) → price spikes to $128
- Turn 5: Order cancels → price crashes to $119
- Pattern repeats turns 6–8
- Operator marks: spoofing pattern detected; evidence count = 2 (spoof + crash)
Phase 2 (ANALYSIS): Trace orders to source; use BLACK LEDGER capability if available
- Orders originate from shell company “Vertex Trading”
- Operator CAR into order history; identifies 6 additional evidence points
- Total evidence: 8 points; confidence high
Phase 3 (REPORTING): File regulatory report; receive reward
- Regulatory panel reviews evidence; pays out 1500 + (8 × 200) = 3100 ¤
- Rep: +16 (investigation skill)
- BLACK LEDGER integration: Operator can CONS the evidence with shell company data to create STRONGER case (Rep +25 instead)

Duration: 18 game turns (5–7 minutes real time)

Worked Example 3: Cross-Module (ICE BREAKER + SYNTHFENCE)

Mission: “MARKET SABOTAGE + CHAOS TRADING”

Operator sabotages financial network; then exploits resulting market confusion
Phase 1 (ICE BREAKER): Intrude into exchange network; disable price feed systems
- Standard ICE BREAKER intrusion; objective = corrupt price data feeds
- Operator extracts/sabotages specific data; network marks exchange as “unreliable”
Phase 2 (SYNTHFENCE): Execute flash trades while market data is corrupted
- Market participants see stale/incorrect prices
- Operator sees TRUE prices (via private data feed) and executes rapid-fire trades
- Market correction happens; operator’s stale-price trades execute at massive profit
- Example: operator knows XYZ is $100 true price, but market shows $95 (stale data)
  - Buy 5000 units at $95
  - Market corrects; XYZ jumps to $100
  - Sell at $100; profit: $25,000 ¤ gross (minus execution risk)
- Reward: 2000 ¤ base + 3000 ¤ chaos bonus = 5000 ¤ total
- Rep: +5 (high-risk coordination)

Duration: 20 game turns (split across two cartridge loads; OODA loops run in parallel if swapped)

1.6 Capability Progression

Proficiency Tiers (SYNTHFENCE-Specific):

Tier 1: Apprentice (Rep 0–4, Proficiency 0–15)

Market feeds show simplified data (only bid/ask, no depth)
Spread calculation is manual (operator must use numpad to calculate profit)
Time limits are generous (15–20 turns per contract)
Audio: YM2149 Voice 1 plays slow tones; prices “sing” at low frequency (easy to follow)
Cipher voice: verbose, instructive (“You’re looking at a $0.50 spread. Buy low, sell high. Execute.”)

Tier 2: Novice (Rep 5–14, Proficiency 16–35)

Market feeds include order book depth (bid/ask stacks visible)
Spread calculation is automated; operator reads it directly
Time limits tighten (12–15 turns per contract)
Audio: YM2149 Voice 2 (data flow) accelerates; price movement becomes a rhythm operator can follow
Cipher voice: professional, occasional hints (“This market is thin. Wide spreads. Easy pickings.”)

Tier 3: Competent (Rep 15–24, Proficiency 36–55)

Market feeds include real-time depth; operator can visualize order flow
Operator can predict short-term price movement from order book shape (Orient skill)
Time limits: 8–12 turns (fast-paced)
Audio: Voice 3 (environmental chaos) reflects market sentiment; operator learns to “hear” manipulation
Cipher voice: minimal (“Market’s crowded. Execution window: 3 turns.”)

Tier 4: Expert (Rep 25–49, Proficiency 56–75)

Market data includes micro-movements (tick-by-tick)
Operator can spot manipulation patterns in real-time (no Orient assist needed)
Time limits: 5–8 turns (very fast)
Audio: all three YM2149 voices create a harmonic “market song”; operator learns to play by ear
Cipher voice: cryptic (“The market breathes. You know the rhythm.”)

Tier 5: Master (Rep 50+, Proficiency 76+)

Market feeds are abstract; operator reads them as pure data flow (not visual)
Operator executes trades without conscious decision-making; somatic skill
Time limits: 3–5 turns (extreme speed)
Audio: operator’s keypresses become part of the YM2149 mix (music and input merge)
Cipher voice: silent, except for rare congratulations (“You are the market.”)

1.7 Contract Economics

Payout Formula:

base_reward = type_bonus + (profit_amount × 0.15)
profit_amount = (final_price - entry_price) × units × 100 ¤
speed_bonus = (time_remaining / time_limit) × base_reward × 0.25
accuracy_multiplier = (correct_decisions / total_decisions)
final_payout = (base_reward + speed_bonus) × accuracy_multiplier

Examples:

Arbitrage (Crude Oil, 500 units):
- Base: 800 ¤
- Entry: $48.50, Exit: $49.10
- Profit: (49.10 − 48.50) × 500 × 100 = 30,000 ¤ scale value (not payout; scale is internal)
- Profit contribution: (0.60 × 100) = 60 ¤ to base
- Total base: 800 + 60 = 860 ¤
- Time: completed in 6 turns of 12-turn limit; speed bonus: (6/12) × 860 × 0.25 = 107.50 ¤
- Accuracy: 1.0 (no mistakes)
- Final: 967.50 ¤
Volatility Capture (Energy, 1500 units, ±1 tick timing):
- Base: 1200 ¤
- Entry: $50.00, Exit: $55.25
- Profit: (55.25 − 50.00) × 150 = 787.50 ¤ scale
- Profit contribution: (5.25 × 50) = 262.50 ¤
- Total base: 1200 + 262.50 = 1462.50 ¤
- Speed bonus: completed in 10 turns of 18-turn limit: (8/18) × 1462.50 × 0.25 = 162.50 ¤
- Accuracy: 1.0 (caught timing perfectly within ±1 tick)
- Final: 1625 ¤
Manipulation Detection (Tungsten Spoofing, 8 evidence points):
- Base: 1500 ¤
- Profit contribution: (8 × 200) = 1600 ¤
- Total base: 3100 ¤
- Speed bonus: completed in 16 turns of 20-turn limit: (4/20) × 3100 × 0.25 = 155 ¤
- Accuracy: 0.95 (one false evidence point out of 9 gathered)
- Final: 3100 × 0.95 + 155 = 3100 ¤ (accuracy penalty balanced by base bonus)
Flash Trading (5 trades, all successful):
- Base: 2000 ¤
- Per-trade profit: $185 total (as calculated in template)
- Profit contribution: (185 × 10) = 1850 ¤
- Total base: 3850 ¤
- Speed bonus: completed in 6 turns of 10-turn limit: (4/10) × 3850 × 0.25 = 385 ¤
- Accuracy: 1.0 (all trades executed flawlessly)
- Final: 4235 ¤

Risk/Reward Curve Table:

Contract Type	Threat	Base Pay	Time Limit	Profit Potential	Rep Gain	Risk
ARBITRAGE	1–2	800–1500 ¤	12–15 turns	20–30% of base	+0.5–1	Low
VOLATILITY	2–3	1200–2000 ¤	15–20 turns	30–50% of base	+1–2	Medium
MANIPULATION	2–4	1500–2500 ¤	18–25 turns	40–80% of base	+2–5	Medium-High
FLASH TRADING	3–4	2000–3500 ¤	8–12 turns	50–100% of base	+2–3	High

Exclusive High-Rep Operations:

MARKET CRASH SCENARIO (Rep 50+, volatility_index 75+): Largest opportunity; operator profits during market collapse or loses everything. Base: 5000 ¤, profit up to 10,000 ¤ if executed perfectly. Rep: +10 if successful, -5 if failed (massive downside).
REGULATORY EVASION (Rep 50+, audit_log present): Operator must hide evidence of manipulation from regulators while profiting from the manipulation. 3-phase contract (manipulate → profit → hide evidence). Base: 3000 ¤, requires BLACK LEDGER module loaded. Rep: +5 (high-risk coordination).
CORPORATE SABOTAGE COMBO (Rep 50+, ICE BREAKER in history): Coordinate market crash with network sabotage. Base: 6000 ¤. Reward: up to 15,000 ¤ if timed perfectly (both systems collapse in sync). Rep: +8. This is the most lucrative solo contract but requires two cartridges loaded (hot swap).

1.8 Operator Workflow

Typical Single-Session (45 min):

Pre-Session Check (2 min): Load SYNTHFENCE. Scan market feeds. Check reputation tier. Cipher voice: “Markets are volatile today. Three contracts available.”
Contract Selection (1 min): Operator reviews ARBITRAGE, VOLATILITY CAPTURE, and MANIPULATION DETECTION options. Chooses VOLATILITY CAPTURE (medium risk, good rep gain).
Execution (25 min): Operator runs VOLATILITY CAPTURE contract. INFO keypress to read price history. Orient: predict the next swing. CAR to enter order, execute buy. Wait for predicted peak. CDR to navigate to sell opportunity. Execute sell. Profit locked. Repeat for 2–3 cycles if time permits.
Analysis & Debrief (3 min): Cipher voice: “You captured three volatility peaks. Excellent pattern recognition. Proficiency +3.” Credits awarded: 1625 ¤. Rep: +2.
Optional Second Contract (15 min if time): Operator can run ARBITRAGE (quick, reliable) or MANIPULATION DETECTION (longer investigation). Chooses quick ARBITRAGE for a second profit cycle. Completes in 8 turns; profit: 967.50 ¤. Rep: +1.

Total Session Earnings: 2592.50 ¤, Rep +3. Proficiency +3. Time investment: 45 minutes.

Multi-Session Campaign (1 week):

Day 1: Two ARBITRAGE sessions. Earn 2000 ¤, Rep +2. Total rep: 2.
Day 2: One VOLATILITY CAPTURE session. Earn 1625 ¤, Rep +2. Total rep: 4. Tier advances to Novice (rep 5 threshold approaching).
Day 3: One MANIPULATION DETECTION session (tutorial-level). Earn 2100 ¤, Rep +3. Total rep: 7. Tier: Novice unlocked.
Day 4: Two quick ARBITRAGE sessions. Earn 2000 ¤, Rep +2. Total rep: 9.
Day 5: VOLATILITY CAPTURE (now faster/easier with Novice tools). Earn 1800 ¤, Rep +2. Total rep: 11.
Day 6: MANIPULATION DETECTION (complex pattern). Earn 3100 ¤, Rep +5. Total rep: 16. Tier: Competent unlocked.
Day 7: One FLASH TRADING session (new contract type; high risk, high reward). Earn 4235 ¤, Rep +3. Total rep: 19.

Week Summary: 17,000+ ¤ earned, Rep +19, Proficiency +12. Operator advances two tiers and is now eligible for exclusive high-rep contracts.

Expert Operator (Rep 50+) Routine:

Weekly: one MARKET CRASH SCENARIO (1–2 hours, 10,000 ¤ payout if successful).
Bi-weekly: one REGULATORY EVASION contract with BLACK LEDGER (3-phase, 3000+ ¤).
Monthly: CORPORATE SABOTAGE COMBO with ICE BREAKER (hot-swap, 6000+ ¤ base, up to 15,000 ¤ if perfect).
Maintenance: occasional ARBITRAGE sessions for steady income (500–1000 ¤ per session, minimal time).

1.9 Cipher Voice Integration

Cipher’s tone in SYNTHFENCE: professional market analyst, increasingly competitive at high rep.

On Load (Apprentice):

“SYNTHFENCE initialized. You’re now connected to global markets. Hong Kong. Tokyo. Mumbai. Singapore. London. New York. Prices are moving. Let’s make money.”

During ARBITRAGE (Apprentice):

“Tokyo crude at $48.20. Mumbai at $48.95. That’s a spread. You see it? Buy low, sell high. Simple.”

During VOLATILITY CAPTURE (Novice):

“Price is oscillating. Two-minute chart shows: peak at $55, valley at $48. Next peak coming in… [PAUSE] three turns. Will you be ready?”

During MANIPULATION DETECTION (Competent):

“These orders don’t make sense. Buy order appears, price spikes, order cancels. That’s spoofing. Classic Vertex Trading signature. You’re seeing the pattern. Good.”

At Rep 50+ (Expert, MARKET CRASH SCENARIO):

“Volatility index at 78. Markets are brittle. One sharp move, everything cascades. Want to profit from the fall? Or do you think you can prevent it? Either way, there’s money in motion.”

Failure (Margin Call):

“You leveraged too much. Market moved against you. Margin call triggered. You’ve lost $5,000 in tied capital. Walk it off. Come back when you’re ready.”

Success (Manipulation Report Filed):

“Regulatory panel reviewed your evidence. Eight points, solid chain. Vertex Trading is under investigation. You’re being paid for your whistle-blow. And they’re being charged. Justice, market-style.”

Domain Vocabulary (CIPHER_DOMAIN):

arbitrage, spread, bid, ask, spot_price, futures, margin_call, leverage, volatility
candlestick, moving_average, resistance, support, breakout, reversion
spoofing, layering, front_running, pump_and_dump, flash_crash, circuit_breaker
long_position, short_position, hedge, delta_neutral, gamma_risk
Hong_Kong_Exchange, Tokyo_Stock_Exchange, Singapore_Exchange, Mumbai_NSE
commodity, crude_oil, metals, agriculture, energy, currency_pair

1.10 Cell Architecture

SYNTHFENCE defines the market order primitive:

CELL_TYPE MARKET_FEED {
  ON_CAR: get_current_price() -> returns PRICE_POINT
  ON_CDR: get_price_history() -> returns list of PRICE_POINT (last 10 ticks)
  ON_EVAL: subscribe() -> locks operator's attention to this feed; starts observation window
};

CELL_TYPE PRICE_POINT {
  ON_CAR: get_bid() -> returns number (ask price)
  ON_CDR: get_ask() -> returns number (bid price)
  ON_EVAL: calculate_spread() -> returns (ask − bid); formatted as decimal
};

CELL_TYPE ORDER_BOOK {
  ON_CAR: get_top_level() -> returns (bid_volume, ask_volume)
  ON_CDR: get_depth() -> returns list of PRICE_LEVEL (top 5 bids, top 5 asks)
  ON_EVAL: submit_order(side, price, size) -> creates ORDER or rejects if price out-of-touch
};

CELL_TYPE ORDER {
  ON_CAR: get_status() -> returns (pending | filled | partial | cancelled)
  ON_CDR: get_execution_price() -> returns actual price (may differ from submitted price)
  ON_EVAL: cancel() -> attempts to cancel order; may fail if already filled
};

CELL_TYPE TRADE_RESULT {
  ON_CAR: get_profit() -> returns (sell_price − buy_price) × volume
  ON_CDR: get_execution_time() -> returns turns_elapsed
  ON_EVAL: settle() -> credits are transferred; profit locked
};

Composition Example (Simple Arbitrage):

(MARKET_OPERATIONS
  (MARKET_FEED "Tokyo Crude"
    (PRICE_POINT 48.50 bid, 48.51 ask)
    (PRICE_HISTORY [...]))
  (ORDER_BOOK "Tokyo Depth"
    (PRICE_LEVEL $48.50, 1000 contracts)
    (PRICE_LEVEL $48.49, 500 contracts))
  (ORDER buy-1000-at-48.50)
  (MARKET_FEED "Mumbai Crude"
    (PRICE_POINT 48.95 bid, 48.96 ask))
  (ORDER sell-1000-at-48.95)
  (TRADE_RESULT profit=$0.45/barrel = $450 gross))

Operator CAR into Tokyo feed, reads current price, CAR into order book depth, submits BUY. Then CDR to Mumbai feed, submits SELL. EVAL settles trade, calculates profit.

1.11 Sound Design as Interface

YM2149 in SYNTHFENCE: price movement as tempo, volume as rhythm, threat as dissonance.

Voice 1 (Square Wave): Price movement. Frequency = current_price / 100 Hz (normalized to audible range).

Current price $50/barrel → Voice 1 plays at 500 Hz
Current price $48/barrel → Voice 1 plays at 480 Hz
Operator learns to “hear” prices rising/falling
Rise = ascending pitch; fall = descending pitch

Voice 2 (Sawtooth): Order book activity (volume). Frequency = total_volume / 1000 × 1000 Hz.

Light trading (100 contracts) → 100 Hz (quiet hum)
Heavy trading (5000 contracts) → 5000 Hz (would be clipped; saturates at max)
Voice 2 pulses with every order submission; operator learns to “feel” market activity

Voice 3 (Noise + Envelope): Regulatory/threat activity. When manipulation is detected or regulatory system activates:

Dissonant tone (e.g., 333 Hz + 666 Hz beating) plays
Envelope is sharp attack (regulatory intervention detected)
Operator learns to “fear” Voice 3 dissonance

Key Audio Events:

SPREAD IDENTIFIED: Voice 1 makes a major third interval (price1 to price2 ratio). Operator recognizes spread aurally before seeing numbers. 200ms duration.
ORDER SUBMISSION: Voice 2 jumps to peak frequency (order size reflected in volume). Sharp attack. Operator knows large order hit market.
ORDER FILL: Voices 1 + 2 converge (price and volume merge). Harmonic reinforcement. Operator senses successful execution.
MANIPULATION DETECTED: Voice 3 plays dissonant tritone (augmented fourth). Repeated at 200ms intervals. Operator learns to “hear” spoofing pattern.
MARGIN CALL: All voices drop in volume by 50%. Voice 1 plays falling scale (C → G → E, descending). Operator senses financial distress.
PROFIT LOCKED: Rising major arpeggio (C → E → G → C’, major chord). Operator’s reward signal.
VOLATILITY PEAK: Voice 1 reaches maximum pitch (price spike). All voices spike simultaneously. Operator learns to anticipate peaks by monitoring Voice 1’s rise.
REGULATORY APPROVAL: Slow, confident bass tone (C2, 65 Hz). Plays once when manipulation report is filed and approved. Operator’s “justice” signal.

1.12 Link Protocol

SYNTHFENCE has asymmetric linked play for competitive trading:

TRADER A Role (Primary):

Submits market manipulation scheme (spoofs, layers, or front-runs)
Sends scheme data to Trader B’s deck via cable
Trader B must detect the manipulation and report it
Real-time: Trader A sees Trader B’s investigation progress

TRADER B Role (Investigator):

Receives market feed (with hidden manipulation embedded)
Analyzes data; attempts to detect scheme
Submits evidence package
Receives judgment: correct/incorrect

Data Flow:

Trader A Deck:
  -> market_feed (with embedded manipulation)
  -> scheme_type (e.g., "spoofing")
  -> scheme_parameters (order sizes, timings, prices)
  -> investigator_progress (real-time view of Trader B's findings)

Trader B Deck:
  <- market_feed (rendered locally)
  <- ticks (market updates, shows manipulation in action)
  -> analysis_results (evidence gathered, conclusion submitted)

Linked Example: Competitive Manipulation Detection

Trader A (Expert) designs spoofing scheme:

Large buy orders (5000 units) appear at $100.00
Orders cancel after price spikes to $102.00
Fake orders repeat 3 times over 12 turns

Trader A sends scheme to Trader B’s deck (Novice). Trader B sees:

Prices oscillating $100 → $102 → $99 on a 3-turn cycle
Unusual order book shape (large orders appearing then vanishing)

Trader B must identify:

Pattern type: spoofing vs. layering vs. front-running
Manipulator signature: which shell company
Motivation: pump-and-dump target price, profit target

If Trader B correctly identifies all 3 points within 10 turns: SUCCESS. Trader B earns 2500 ¤, Rep +5. Trader A gets Rep +1 for quality scheme design.

If Trader B fails to identify: FAILURE. Trader A’s manipulation succeeds; Trader A earns 1500 ¤, Rep +2 (profit from successful manipulation).

Economics: Teaching/designing manipulation schemes for others earns reputation. Expert operators can become “market scheme designers” and earn credits by teaching Novices how markets work—both offense (how to manipulate) and defense (how to detect).

MODULE 2: DRIFT — SIGNAL TRACKING

2.1 Module Identity

Designation: SIGNAL TRACKING (MODULE CLASS: 0x07) Publisher: Cascade Softworks (Seattle) Profile: Radio frequency location, dead-drop protocols, signal triangulation Operator Role: RF technician, signal analyst, covert communications specialist Deck State Signature: Sets bit 6 in cartridge_history bitfield on first load Loading Screen: Pacific Northwest maritime aesthetic. Sonar ping sequence (3-4 pings from YM2149 Voice 1, decreasing in frequency, mimicking underwater sonar). ASCII art of radio tower with rotating antenna beam sweeps across screen. Cascade Softworks wordmark assembles as beam passes over. No colors, pure amber on black. Clean, technical. 2.5 seconds. Audio: authentic sonar-like pulses, then silence. Professional. No drama.

DRIFT transforms the Deckline into an RF analysis and location workstation. The operator specializes in triangulating radio transmitter positions, intercepting dead-drop communications, detecting counter-surveillance signals, and mapping covert communication networks. The screen is a sonar display reimagined for RF: signal strength maps, bearing indicators, frequency waterfall displays, triangulation geometry rendered in real-time ASCII art.

On First Load: The Mission Board generates TRIANGULATION, SIGNAL INTERCEPTION, DEAD-DROP PROTOCOL, and COUNTER-SURVEILLANCE contracts. The operator’s deck is marked as having signal tracking capability. All future cross-module interactions check this bit: PATHFINDER route-planning can now include “avoid surveillance corridors”; DEPTHCHARGE sonar becomes cross-compatible with RF (underwater hydrophones + surface RF signals).

2.2 Mission Template Architecture

Contract Classes

Contract Type	Description	Threat Range	Base Payout	Phases
TRIANGULATION	Locate RF transmitter using multiple receiver points; calculate position	1–2	700–1500 ¤	1–2
SIGNAL INTERCEPTION	Detect, decode, and record covert radio communications	2–3	1000–2200 ¤	2–3
DEAD-DROP PROTOCOL	Identify dead-drop locations via signal pattern matching; intercept handoff	2–4	1200–3000 ¤	2–4
COUNTER-SURVEILLANCE	Detect counter-surveillance signals; map surveillance network; evade	3–5	1500–4000 ¤	2–3

Template Structure (Procedural Generation)

TRIANGULATION Contract:

target_transmitter: random identity (e.g., "Rogue Node 7", "Unknown Beacon X")
broadcast_frequency: 400–900 MHz (realistic RF band)
signal_strength_at_receiver_1: random (−80 to −40 dBm)
signal_strength_at_receiver_2: random (−80 to −40 dBm)
signal_strength_at_receiver_3: random (−80 to −40 dBm)
receiver_locations: three known fixed points (e.g., building rooftop, water tower, radio mast)
operator_task: use bearing + strength data from each receiver to triangulate transmitter position
accuracy_target: locate transmitter within ±200 meters (higher accuracy = higher reward)
time_limit: 6–12 turns (calculation-paced)
threat_level: 1–2 (simple geometry, no active counter-measures)
reward_formula: base_reward + (accuracy_bonus: if within ±100m, ×1.5; within ±50m, ×2.0)
rep_gain: +0.5 per correct triangulation; −1 if position is wildly off (>500m error)
complication: if PATHFINDER in history, operator can immediately route to target location
complication: if ICE BREAKER in history, operator can detect and suppress counter-surveillance signals

Example: Locate Rogue Node 7

Receiver 1 (downtown tower, 41.3°N 71.5°W): signal bearing 045°, strength −62 dBm
Receiver 2 (waterfront mast, 41.25°N 71.6°W): signal bearing 315°, strength −58 dBm
Receiver 3 (hills, 41.4°N 71.4°W): signal bearing 225°, strength −72 dBm
Operator uses INFO to read bearing data; visualizes three bearing lines
Operator CAR into triangulation calculator; inputs three bearings
System calculates intersection point; transmitter is at (41.32°N 71.48°W)
Operator’s estimate: (41.33°N 71.49°W) = 1.5 km error
Accuracy multiplier: within ±200m? No. But within ±2km, so ×1.0 (no bonus)
Reward: 700 ¤
Rep: +0.5

SIGNAL INTERCEPTION Contract:

target_signal: encrypted or plaintext radio transmission
broadcast_schedule: periodic (every 30–120 seconds game time = every 2–8 turns)
operator_task: detect signal; capture frequency; decode if possible; record content
coding_type: plaintext (100% success) | light_encryption (70% success, operator guesses key) | heavy_encryption (20% success, requires BLACK LEDGER integration or ICE BREAKER key extraction)
signal_content: coded message with operational meaning (e.g., "PACKAGE READY AT NORTH POINT" = dead-drop handoff scheduled)
time_limit: 15–25 turns (extended; requires patience)
threat_level: 2–3 (signal exists; counter-surveillance may detect your receiver)
reward_formula: base_reward + (encryption_bonus: if decoded, ×1.5–2.0 depending on difficulty)
rep_gain: +1 per signal captured; +2 per successful decode; −2 per failed decode (wrong guess on encryption key)
complication: if PATHFINDER in history, operator can immediately route to location mentioned in intercept
complication: if BLACK LEDGER in history, operator can correlate signal with financial transactions (double reward if match found)

Example: Intercept “Courier Network” Signal

Turn 1: Operator sets up receiver (EVAL on receiver cell)
Turn 3: Signal detected at 456.2 MHz; strength −58 dBm
Operator CAR into signal, marks it (QUOTE)
Turn 5: Signal repeats; operator records frequency
Turns 8–12: Operator monitors signal for 3 cycles; pattern emerges (message repeats every 30 seconds)
Turn 13: Operator attempts to decode; tries key “COURIER” via numpad entry
Success: message decodes to “PACKAGE READY AT NORTH POINT THURSDAY 0200 LOCAL”
Operator records message; contract complete
Reward: 1000 + (encryption bonus 1.5) = 1500 ¤
Rep: +1 (captured) + 2 (decoded) = +3

DEAD-DROP PROTOCOL Contract:

drop_location: fixed or variable (depends on signal pattern)
signal_pattern: series of short transmissions that encode drop location/timing
operator_task: monitor signals; identify pattern; predict when/where drop occurs; intercept handoff
pattern_complexity: 3–8 signal pulses, each encoding data (e.g., pulse count = hour of drop, frequency = location code)
operator_analysis: use CDR to traverse signal sequence; use CONS to assemble location code; use EVAL to predict drop timing
complication: counter-surveillance may detect you monitoring the drop
time_limit: 20–30 turns (long, requires pattern assembly)
threat_level: 2–4 (active counter-measures may deploy if you're detected)
reward_formula: base_reward + (location_accuracy: if predicted correctly, ×1.5; if you intercept actual drop, ×3.0)
rep_gain: +2 per correct pattern element; +5 if you intercept drop package; −3 if you alert counter-surveillance
complication: if PATHFINDER in history, operator can calculate optimal route to drop location before intercept
complication: if ICE BREAKER in history, operator can disable surveillance systems before drop (2-phase mission)

Example: Intercept Dead-Drop Handoff

Signals detected: 3 pulses (short-short-short), then 5 pulses (short-short-short-short-short), then 2 pulses
Operator interprets: 3 pulses = 3 hours, 5 pulses = location code 5 (warehouse district), 2 pulses = Tuesday
Current time: Monday 22:00. Drop predicted: Tuesday 01:00 at location code 5
Operator has 2 game-hours to prepare (20 turns)
Operator uses PATHFINDER (if loaded) to identify fastest route to location code 5
Turn 19: Operator arrives at location code 5
Turn 20: Counter-agent arrives with package; handoff occurs
Operator intercepts: detains counter-agent (narrative resolution); recovers package
Package contains: $2,000 ¤ equivalent in documents/credits
Reward: 1200 + 1800 (intercept bonus) = 3000 ¤
Rep: +5 (pattern decoded) + 5 (package intercepted) = +10

COUNTER-SURVEILLANCE Contract:

threat_scenario: operator is being hunted via RF surveillance (counter-surveillance signals)
operator_task: detect counter-surveillance signals; map surveillance network; evade and/or disable
surveillance_types: 3–5 different counter-surveillance signals (each encodes spotter location, alert status, interception priority)
operator_challenge: move through territory while avoiding detection; identify surveillance nodes
consequence: if detected, counter-surveillance escalates (new signals activate, alert spread)
time_limit: 20–30 turns (extended cat-and-mouse scenario)
threat_level: 3–5 (active, aggressive counter-measures)
reward_formula: base_reward + (evasion_bonus: if undetected throughout, ×2.0; if detected but escape, ×1.0; if captured, ×0)
rep_gain: +3 per surveillance node identified; +5 if operator escapes undetected; −5 if captured by counter-surveillance
complication: if ICE BREAKER in history, operator can disable surveillance nodes via network (cyber + physical evasion, 2-phase)
complication: if PATHFINDER in history, operator can calculate optimal evasion route

Example: Evade Counter-Surveillance Network

Operator detects 5 RF signals in the environment (surveillance nodes)
Node 1 (downtown): scanning frequency 200–400 MHz, high alert status
Node 2 (waterfront): scanning 400–600 MHz, medium alert
Node 3 (hills): scanning 600–800 MHz, low alert
Node 4 (airport): broad scanning, very high alert (critical node)
Node 5 (warehouse): narrow scanning 450 MHz, low alert
Operator’s task: navigate from safe house to extraction point without being detected by all 4 nodes simultaneously
Operator plots route that stays in “blind spots” between surveillance beams
Turn 5: Moves through downtown, avoids Node 1 (low alert status = beam is elsewhere)
Turn 10: Moves waterfront, narrowly misses Node 2 (alert rises to medium)
Turn 15: Operator takes detour to avoid Node 4 (critical node)
Turn 20: Reaches extraction point undetected by majority
Operator escapes; counter-surveillance doesn’t activate full network
Reward: 1500 + 3000 (evasion bonus) = 4500 ¤
Rep: +15 (nodes identified + escape) = +15

2.3 Deck State Integration

SRAM Writes:

credit_balance — modest increases (700–4000 ¤ per contract)
reputation_score — moderate increases (+0.5 to +5 per contract)
signal_library NEW — hidden stat tracking operator’s knowledge of signal signatures; ranges 0–50; unlocks exclusive high-rep contracts at 40+
cartridge_history bit 6 set permanently
threat_index NEW — counter-surveillance awareness; rises with COUNTER-SURVEILLANCE contracts; affects other modules’ threat calculations

Reputation Thresholds (DRIFT Context):

Rep 0–4: TRIANGULATION only. Simple 3-point triangulation. No encryption.
Rep 5–14: SIGNAL INTERCEPTION added. Plaintext messages. Simple patterns.
Rep 15–24: DEAD-DROP PROTOCOL added. 3–4 signal pulses. Basic pattern matching.
Rep 25–49: COUNTER-SURVEILLANCE added. 3–5 surveillance nodes. Evasion tactics.
Rep 50+: EXCLUSIVE: HUNTER NETWORK (detect and track sophisticated surveillance AI), SIGNAL SPOOFING (transmit false signals to confuse counter-surveillance), NETWORK MAPPING (build complete RF network diagram for a city).

2.4 Cross-Module Interactions

With PATHFINDER (Route Planning):

TRIANGULATION contracts automatically unlock routing to target location (operator can CAR into route planner; PATHFINDER calculates fastest path).
DEAD-DROP PROTOCOL: operator can pre-calculate evasion routes using PATHFINDER data.
2-phase: triangulate location → plan extraction route.
Operator with PATHFINDER in history: signal location tasks reduced 1 difficulty level.

With DEPTHCHARGE (Sonar/Maritime):

RF signals can originate from underwater (submarine communications).
TRIANGULATION contracts include “underwater RF sources”—hydrophones + RF detection.
2-phase: detect underwater signal via DEPTHCHARGE sonar → triangulate position via DRIFT RF.
Special mission: MARITIME SURVEILLANCE—detect spy submarine RF emissions.
Operator with DEPTHCHARGE in history: can detect submerged RF sources; exclusive underwater signal contracts.

With ICE BREAKER (Network Intrusion):

COUNTER-SURVEILLANCE signals are defended by network-deployed ICE (defensive jamming systems).
2-phase: hack ICE BREAKER to disable counter-surveillance network → evade undefended surveillance.
Special mission: CYBER-PHYSICAL EVASION—disable surveillance via ICE BREAKER while physically evading via DRIFT.
Reward: +60% if both phases coordinated.

With SYNTHFENCE (Market Operations):

Signal intercepts may reveal market manipulation schemes (traders using encrypted channels).
SIGNAL INTERCEPTION can detect market-related dead-drops (financial data handoffs).
Special mission: FINANCIAL INTELLIGENCE—intercept communications related to market manipulation, sell intel to BLACK LEDGER.
Operator with SYNTHFENCE in history: can correlate intercepted signals with market data (rep bonus +3 per signal).

Self-Reference:

Solo DRIFT: pure RF analysis and location work.
Paired with PATHFINDER: signal location + evasion routing.
Paired with DEPTHCHARGE: underwater + surface RF detection.
Paired with ICE BREAKER: cyber + physical evasion.
Paired with SYNTHFENCE: market intelligence intercepts.

2.5 Multi-Phase Mission Design

Phase Architecture

DRIFT supports three primary phase structures:

DETECTION → ANALYSIS → LOCATION (Triangulation):

DETECTION: Operator sets up receivers; detects signal.
ANALYSIS: Operator gathers bearing/strength data from multiple points.
LOCATION: Operator calculates transmitter position.

MONITORING → DECODING → EXPLOITATION (Signal Interception):

MONITORING: Operator detects and records signal.
DECODING: Operator attempts to decrypt/decode message.
EXPLOITATION: Operator uses message content (e.g., schedules dead-drop, routes shipments).

PATTERN → PREDICTION → INTERCEPT (Dead-Drop):

PATTERN: Operator identifies signal pattern encoding location/timing.
PREDICTION: Operator calculates when/where drop occurs.
INTERCEPT: Operator arrives at location; intercepts handoff.

DETECTION → EVASION → ESCAPE (Counter-Surveillance):

DETECTION: Operator identifies surveillance nodes.
EVASION: Operator plots safe route through blind spots.
ESCAPE: Operator reaches extraction point undetected.

Worked Example 1: Simple Triangulation (1-Phase)

Mission: “LOCATE ROGUE NODE 7”

Receiver 1: bearing 045°, strength −62 dBm
Receiver 2: bearing 315°, strength −58 dBm
Receiver 3: bearing 225°, strength −72 dBm
Operator triangulates: (41.32°N 71.48°W)
Operator’s position estimate: (41.33°N 71.49°W) = 1.5 km error
Reward: 700 ¤
Rep: +0.5
Duration: 8 turns

Worked Example 2: Dead-Drop Detection + Intercept (3-Phase, 30 turns)

Mission: “OPERATION MIDNIGHT COURIER”

Phase 1 (SIGNAL DETECTION): Operator monitors for courier network signals. Detects 3-pulse, 5-pulse, 2-pulse sequence over 8 turns.
Phase 2 (PATTERN ANALYSIS): Operator interprets pattern. 3 pulses = 3 hours, 5 pulses = location code 5 (warehouse district), 2 pulses = Tuesday. Current time: Monday 22:00. Prediction: drop at Tuesday 01:00 at warehouse code 5. Analysis complete; rep +5.
Phase 3 (INTERCEPT): Operator routes to warehouse code 5 (using PATHFINDER if loaded). Operator arrives turn 22. Turn 23: counter-agent arrives. Operator intercepts; package recovered. Reward: 1200 + 1800 = 3000 ¤. Rep: +10 total.

Cross-Module (PATHFINDER + DRIFT):

Phase 1 (DRIFT): Detect pattern, predict location.
Phase 2 (PATHFINDER): Plan optimal route to warehouse.
Phase 3 (DRIFT): Execute intercept at predicted location/time.
Reward: 3000 ¤ base + 500 ¤ path bonus (if route perfectly timed) = 3500 ¤. Rep: +12.

Worked Example 3: Counter-Surveillance Evasion (2-Phase, 25 turns)

Mission: “EVADE HUNTER NETWORK”

Phase 1 (SURVEILLANCE MAPPING): Operator detects 5 RF nodes. Uses INFO to build node map. Maps nodes 1–5 with bearings and alert levels. Rep +3.
Phase 2 (EVASION): Operator plots route from safe house → extraction point while avoiding detection.
- Moves through downtown: avoids Node 1 (1 turn vulnerable, node alert low)
- Moves waterfront: nearly detected by Node 2 (2 turns vulnerable, node alert medium, operator succeeds by narrow margin)
- Detours to avoid Node 4 (critical surveillance; high risk)
- Reaches extraction point: undetected
- Escape successful; counter-surveillance doesn’t activate full network
- Rep: +5 (escape bonus)
Total Reward: 1500 + 3000 (evasion bonus) = 4500 ¤
Total Rep: +8

Cross-Module (ICE BREAKER + DRIFT):

Phase 1 (DRIFT): Map surveillance network; identify critical nodes.
Phase 2 (ICE BREAKER): Hack counter-surveillance control system; disable Node 4 (critical blocker).
Phase 3 (DRIFT): Evade remaining nodes; extract.
Reward: 4500 ¤ base + 1000 ¤ cyber coordination = 5500 ¤. Rep: +10.

2.6 Capability Progression

Proficiency Tiers (DRIFT-Specific):

Tier 1: Apprentice (Rep 0–4, Proficiency 0–15)

Signal detection is manual; operator must press INFO repeatedly to detect signals
Bearing calculation shown as visual diagram (lines drawn on screen)
Time limits are generous (15–20 turns)
Audio: YM2149 Voice 1 (ping tone) plays at detected frequency; operator learns to “hear” RF signals
Cipher voice: instructive (“You’re hearing a signal at 456 MHz. Three receivers around you. Listen to the bearing from each. What’s your triangulation?”)

Tier 2: Novice (Rep 5–14, Proficiency 16–35)

Signal detection is automatic; signals appear in receiver cell automatically
Bearing calculation is automated; operator reads it from display
Time limits: 12–15 turns
Audio: Voice 2 (bearing tone) plays at angle-proportional frequency; operator learns to interpret bearing by ear
Cipher voice: professional (“Bearing 045 from Node 1. 315 from Node 2. Calculate intersection.”)

Tier 3: Competent (Rep 15–24, Proficiency 36–55)

Multiple signals visible simultaneously; operator can track 3–4 signals in parallel
Bearing calculation is near-instant; operator reads it directly without calculation step
Time limits: 8–12 turns
Audio: all three YM2149 voices encode different signals simultaneously; operator learns multi-signal tracking by ear
Cipher voice: sparse (“That’s a hunter. You know what to do.”)

Tier 4: Expert (Rep 25–49, Proficiency 56–75)

Signal data is abstract; operator reads it as pure sonar-like display (dots + bearing lines, no calculation needed)
Operator can predict signal location from pattern alone (no explicit triangulation needed)
Time limits: 5–8 turns
Audio: operator’s keystrokes become part of the YM2149 mix; signal tracking becomes rhythmic
Cipher voice: cryptic (“The signal sings. Are you listening?”)

Tier 5: Master (Rep 50+, Proficiency 76+)

Sonar display is abandoned; operator navigates by sound alone (YM2149 voices encode all signal data)
Operator executes intercepts, evasions, and triangulations without conscious decision-making
Time limits: 2–5 turns (extreme speed)
Audio: operator and YM2149 are synchronized; signal tracking is pure somatic skill
Cipher voice: silent approval (“You are the antenna.”)

2.7 Contract Economics

Payout Formula:

base_reward = type_bonus + (accuracy_bonus × base_reward × multiplier)
accuracy_multiplier = based on detection/decode/evasion success rate
speed_bonus = (time_remaining / time_limit) × base_reward × 0.20
final_payout = (base_reward + speed_bonus)

Examples:

Triangulation (Locate Rogue Node 7, 1.5 km error):
- Base: 700 ¤
- Accuracy: within ±2 km = no bonus (multiplier ×1.0)
- Time: completed in 8 turns of 10-turn limit; speed bonus: (2/10) × 700 × 0.20 = 28 ¤
- Final: 728 ¤
Signal Interception (Decode “Courier Network”, successful decode):
- Base: 1000 ¤
- Encryption bonus: (decoded complex message) = ×1.5
- Total base: 1000 × 1.5 = 1500 ¤
- Speed bonus: completed in 13 turns of 20-turn limit; (7/20) × 1500 × 0.20 = 105 ¤
- Final: 1605 ¤
Dead-Drop Intercept (Full package recovery, undetected):
- Base: 1200 ¤
- Intercept bonus: ×2.0 (full package recovered)
- Total base: 2400 ¤
- Speed bonus: completed in 20 turns of 30-turn limit; (10/30) × 2400 × 0.20 = 160 ¤
- Final: 2560 ¤
Counter-Surveillance Evasion (Undetected escape):
- Base: 1500 ¤
- Evasion bonus: ×2.0 (undetected throughout)
- Total base: 3000 ¤
- Speed bonus: completed in 25 turns of 30-turn limit; (5/30) × 3000 × 0.20 = 100 ¤
- Final: 3100 ¤

Risk/Reward Curve Table:

Contract Type	Threat	Base Pay	Time Limit	Accuracy Bonus	Rep Gain	Risk
TRIANGULATION	1–2	700–1000 ¤	8–12 turns	0–1.5×	+0.5–1	Low
SIGNAL INTERCEPT	2–3	1000–1500 ¤	15–20 turns	0–2.0×	+1–3	Medium
DEAD-DROP	2–4	1200–2000 ¤	20–30 turns	0–3.0×	+2–5	Medium-High
COUNTER-SURVEILLANCE	3–5	1500–2500 ¤	20–30 turns	0–2.0×	+3–5	High

Exclusive High-Rep Operations:

HUNTER NETWORK DETECTION (Rep 50+, threat_index 40+): Detect sophisticated AI-driven surveillance system. Base: 3500 ¤, up to 6000 ¤ if operator maps entire network. Rep: +8.
SIGNAL SPOOFING (Rep 50+, signal_library 40+): Transmit false signals to confuse counter-surveillance. Requires ICE BREAKER capability to jam defender responses. Base: 3000 ¤. Rep: +6.
CITY-SCALE NETWORK MAPPING (Rep 50+): Map all RF signals across entire city; create comprehensive signal atlas. Base: 4000 ¤, rep: +10. Unlock permanent “signal knowledge bonus” (+0.5 × payout per future contract).

2.8 Operator Workflow

Typical Single-Session (45 min):

Pre-Session Check (2 min): Load DRIFT. Scan RF environment. Cipher voice: “RF is quiet. Three triangulation jobs posted. You want to hunt or observe?”
Contract Selection (1 min): Operator chooses TRIANGULATION + SIGNAL INTERCEPTION (mixed work, 30 min total).
First Contract: TRIANGULATION (12 min):
- Operator sets up receivers (EVAL on receiver cells)
- Detects target signal at 456.2 MHz
- Gathers bearing data: 045° (Node 1), 315° (Node 2), 225° (Node 3)
- CAR into triangulation calculator; submits bearings
- System calculates position; operator’s estimate within ±100m (high accuracy)
- Reward: 700 + (bonus 1.5) = 1050 ¤
- Rep: +1
Second Contract: SIGNAL INTERCEPTION (15 min):
- Operator sets up receiver; monitors signal
- Detects repeating pattern (message repeats every 30 seconds)
- Operator records 3 message cycles (9 turns of monitoring)
- Attempts decode; tries key “OPERATIVE” (correct)
- Message decodes: “PACKAGE READY WAREHOUSE 3 SATURDAY 1800”
- Reward: 1000 + (encryption bonus 1.5) = 1500 ¤
- Rep: +3
Debrief (3 min): Cipher voice: “Two good jobs. You’re developing pattern recognition. Proficiency +2.” Credits: 2550 ¤. Rep: +4.

Total Session Earnings: 2550 ¤, Rep +4. Proficiency +2. Time: 45 minutes.

Multi-Session Campaign (2 weeks):

Day 1–2: Three TRIANGULATION contracts. Earn 3000 ¤, Rep +3. Total rep: 3.
Day 3–4: Two SIGNAL INTERCEPTION contracts. Earn 3000 ¤, Rep +5. Total rep: 8. Tier: Novice (Rep 5) reached.
Day 5–6: One DEAD-DROP contract (new type). Earn 2500 ¤, Rep +8. Total rep: 16. Tier: Competent (Rep 15) reached.
Day 7: Two TRIANGULATION + one SIGNAL INTERCEPTION (quick earners). Earn 3000 ¤, Rep +4. Total rep: 20.
Day 8–10: COUNTER-SURVEILLANCE (new type) + two DEAD-DROP contracts. Earn 7000+ ¤, Rep +15. Total rep: 35.
Day 11–14: Mixture of all contract types; earn additional 6000 ¤, Rep +8. Total rep: 43. Tier: Expert (Rep 25) reached. Signal Library: 42 (unlock exclusive contracts).

Two-Week Summary: 28,000+ ¤ earned, Rep +43, Signal_Library +42. Operator reaches Expert tier and unlocks exclusive HUNTER NETWORK and SIGNAL SPOOFING contracts.

Expert Operator (Rep 50+) Routine:

Weekly: one HUNTER NETWORK DETECTION (high-stakes AI surveillance). 1–2 hours, 6000 ¤ payout if successful.
Bi-weekly: one SIGNAL SPOOFING contract (transmit false signals). 3000+ ¤.
Monthly: CITY-SCALE NETWORK MAPPING (long-term project). 4000 ¤ + permanent signal knowledge bonus.
Maintenance: occasional TRIANGULATION for steady income (1000 ¤ per session, minimal time).

2.9 Cipher Voice Integration

Cipher’s tone in DRIFT: patient technician, increasingly mystical at high rep.

On Load (Apprentice):

“DRIFT initialized. You’re now listening to the RF spectrum. Signals are everywhere. Hidden messages. Covert networks. Location data. Let’s learn to hear.”

During TRIANGULATION (Apprentice):

“Three receivers. Three bearings. Where do the lines intersect? That’s your target.”

During SIGNAL INTERCEPTION (Novice):

“That signal is repeating. A message inside noise. Record it. Three cycles should be enough.”

During DEAD-DROP (Competent):

“The pattern is the message. Count the pulses. Three. Then five. Then two. What do those numbers mean? Location. Time. Date.”

During COUNTER-SURVEILLANCE (Expert):

“You’re being hunted. I detect five RF nodes in your area. Each one has a blind spot. Find the spaces between the beams. Move through the dark.”

At Rep 50+ (Master, HUNTER NETWORK):

“There’s an intelligence system watching the city. An AI. It learns. It adapts. It predicts your movements. Can you hear it thinking? Can you think faster?”

Success (Package Intercepted):

“You caught them. Courier with package. Mission complete. Your reputation precedes you.”

Failure (Detected by Counter-Surveillance):

“They saw you. RF node detected your receiver. Network is escalating. Run. Now.”

Domain Vocabulary (CIPHER_DOMAIN):

triangulation, bearing, frequency, transmitter, receiver, RF_signal, dBm, MHz
dead_drop, dead_drop_location, handoff, courier, package, message, encryption
spoofing, jamming, counter_surveillance, surveillance_node, RF_network, hunter, AI
sonar, ping, hydrophone, underwater_signal, submarine_RF
detection, interception, evasion, escape, extraction
encryption_key, plaintext, ciphertext, decode, encode, pattern_matching

2.10 Cell Architecture

DRIFT defines the RF receiver primitive:

CELL_TYPE RECEIVER {
  ON_CAR: get_frequency() -> returns MHz value (e.g., 456.2)
  ON_CDR: get_bearing() -> returns degrees (e.g., 045)
  ON_EVAL: record_signal() -> stores signal data; triggers time-based sampling
};

CELL_TYPE SIGNAL {
  ON_CAR: get_strength() -> returns dBm (−80 to −40 typical)
  ON_CDR: get_frequency_list() -> returns list of detected frequencies
  ON_EVAL: analyze() -> returns SIGNAL_ANALYSIS
};

CELL_TYPE SIGNAL_ANALYSIS {
  ON_CAR: get_pattern() -> returns (repeating | one_shot | streaming)
  ON_CDR: get_encryption_type() -> returns (plaintext | light_encryption | heavy_encryption)
  ON_EVAL: extract_message() -> attempts decode; returns MESSAGE or ENCRYPTED_DATA
};

CELL_TYPE TRIANGULATION {
  ON_CAR: get_receiver_list() -> returns list of RECEIVER (3 minimum)
  ON_CDR: get_bearing_list() -> returns list of bearings (one per receiver)
  ON_EVAL: calculate_position() -> returns GPS_COORDINATE
};

CELL_TYPE GPS_COORDINATE {
  ON_CAR: get_latitude() -> returns degrees_N
  ON_CDR: get_longitude() -> returns degrees_W
  ON_EVAL: compare(operator_estimate) -> returns accuracy_error_km
};

CELL_TYPE SURVEILLANCE_NODE {
  ON_CAR: get_frequency() -> returns MHz (scanning frequency)
  ON_CDR: get_alert_level() -> returns (low | medium | high)
  ON_EVAL: get_detection_cone() -> returns bearing + width (e.g., 045° ±30°)
};

Composition Example (Triangulation):

(SIGNAL_TRACKING
  (RECEIVER "Node 1" 456.2MHz bearing-045 strength-62dBm)
  (RECEIVER "Node 2" 456.2MHz bearing-315 strength-58dBm)
  (RECEIVER "Node 3" 456.2MHz bearing-225 strength-72dBm)
  (TRIANGULATION
    (BEARING_LINE Node-1 045°)
    (BEARING_LINE Node-2 315°)
    (BEARING_LINE Node-3 225°))
  (GPS_COORDINATE 41.32°N 71.48°W))

Operator CAR into receiver; reads frequency + bearing. Navigates through receivers. Uses TRIANGULATION cell to assemble bearings. EVAL calculates position.

2.11 Sound Design as Interface

YM2149 in DRIFT: RF signals as pure tone, bearing as direction, signal strength as volume.

Voice 1 (Square Wave): Signal frequency. Frequency = RF_frequency / 1,000,000 × 500 Hz (normalized to 300–3000 Hz).

456.2 MHz signal → Voice 1 plays at 228 Hz
Operator learns to “hear” different RF signals as distinct tones
456 MHz sounds different from 789 MHz (operator develops RF tone recognition)

Voice 2 (Sawtooth): Signal bearing. Frequency = bearing_angle / 360 × 1000 Hz + 500 Hz (offset to avoid zero).

Bearing 000° (north) → 500 Hz
Bearing 090° (east) → 750 Hz
Bearing 180° (south) → 1000 Hz
Bearing 270° (west) → 750 Hz (wraps)
Operator learns to “hear” bearing as pitch (north=low, east/west=mid, south=high)

Voice 3 (Noise, variable envelope): Signal strength and alert status.

Strong signal (−40 dBm) → Voice 3 plays loudly (noise floor high)
Weak signal (−80 dBm) → Voice 3 is quiet (barely audible)
Counter-surveillance alert → Voice 3 plays harsh, dissonant chirp (warning tone)

Key Audio Events:

SIGNAL DETECTED: Voice 1 plays target frequency; lasts 1 second; operator knows signal is present.
BEARING LOCKED: Voice 2 jumps to bearing-proportional frequency; holds steady. Operator knows bearing is stable.
TRIANGULATION POINT SET: All three voices converge (harmonic alignment). Operator senses “lock.”
INTERSECTION CALCULATED: Major chord (C−E−G) plays. Operator’s position solved.
DECRYPTION STARTED: Voice 2 accelerates (scanning encryption key space); stuttering effect. Operator senses active decryption.
DECRYPTION SUCCESS: Voice 2 locks into steady tone; Voice 1 plays triumphant rise. Operator knows message is decoded.
COUNTER-SURVEILLANCE DETECTED: Voice 3 plays dissonant tritone (alarm); repeats. Operator immediately recognizes threat.
EVASION SUCCESSFUL: All three voices fade to silence (stealth achieved). Operator senses undetected passage.

2.12 Link Protocol

DRIFT has asymmetric linked play for collaborative location:

TRACKER Role (Primary):

Plants a “transmitter” at a secret location
Sends receiver coordinates (not transmitter location) to HUNTER deck via cable
Sends signal frequency + initial bearing hints
Real-time: TRACKER sees HUNTER’s triangulation progress

HUNTER Role (Seeker):

Receives receiver coordinates
Receives signal frequency + bearings (as triangulation updates)
Must calculate transmitter location
Submits guess; receives accuracy feedback

Data Flow:

Tracker Deck:
  -> receiver_coordinates (lat/lon of each receiver)
  -> signal_frequency (MHz)
  -> bearing_sequence (updated each turn as Tracker moves)
  -> hunter_triangulation_progress (real-time view of Hunter's calculations)

Hunter Deck:
  <- receiver_coordinates (rendered locally)
  <- signal_frequency (detected by receivers)
  <- bearings (updated as Tracker moves; creates dynamic problem)
  -> triangulation_guess (location submitted)
  -> analysis_results (error distance from actual transmitter)

Linked Example: Collaborative Triangulation

Tracker (Expert) hides a transmitter at (41.35°N 71.51°W). Sends three receiver locations to Hunter’s deck (Novice).

Hunter receives:

Receiver 1: (41.30°N 71.50°W)
Receiver 2: (41.40°N 71.50°W)
Receiver 3: (41.35°N 71.55°W)
Signal frequency: 456.2 MHz
Initial bearing from Node 1: 045°

Turn 1: Hunter calculates bearing from Node 2 (CAR into Node 2 receiver). Bearing appears: 315°. Turn 2: Hunter calculates bearing from Node 3. Bearing: 225°. Turn 3: Hunter plots three bearing lines; calculates intersection (41.35°N 71.51°W). Turn 4: Hunter submits guess: (41.34°N 71.52°W) = 1.4 km error.

Tracker’s deck shows: Hunter is 1.4 km off. If within ±100m, TRACKER earns rep +3 (for designing good problem). HUNTER earns rep +2 (for solving it).

Competitive Variant: TRACKER deliberately moves during transmission (simulating a mobile transmitter). HUNTER must triangulate a moving target. Extreme difficulty; high rep gain for success.

MODULE 3: PATHFINDER — ROUTE PLANNING

3.1 Module Identity

Designation: ROUTE PLANNING (MODULE CLASS: 0x08) Publisher: Meridian Systems (Hong Kong) Profile: Logistics optimization, convoy management, supply chain planning Operator Role: Logistics planner, supply chain coordinator, convoy commander Deck State Signature: Sets bit 7 in cartridge_history bitfield on first load Loading Screen: Global logistics aesthetic. Map assembles piece-by-piece (Tetris-style) showing Hong Kong, Singapore, Mumbai, Shanghai nodes. Each node connects with lines. A cargo container icon rotates at center. Meridian Systems wordmark appears beneath. Audio: subtle mechanical clicks (Tetris-like block placement sounds), then three synthetic chord resolved in C major. 2.8 seconds. No urgency, pure efficiency.

PATHFINDER transforms the Deckline into a logistics and route planning workstation. The operator specializes in optimizing delivery routes, managing convoy timing, coordinating multi-stop supply chains, and adapting routes when conditions change (roadblocks, threats, delays). The screen is a logistics dispatch center: nodes, routes, time windows, threat corridors, convoy status in real-time.

On First Load: The Mission Board generates ROUTE OPTIMIZATION, CONVOY MANAGEMENT, SUPPLY CHAIN COORDINATION, and THREAT EVASION contracts. The operator’s deck is marked as having route planning capability. All future cross-module interactions check this bit: DRIFT signal tracking now includes “route-aware interception” (signal locations correlate to route waypoints); SYNTHFENCE arbitrage now includes “geographic supply chain timing” (monitor commodity delivery timing to arbitrage effectively).

3.2 Mission Template Architecture

Contract Classes

Contract Type	Description	Threat Range	Base Payout	Phases
ROUTE OPTIMIZATION	Plan optimal path from source → destination; minimize time/fuel/threat	1–2	600–1400 ¤	1–2
CONVOY MANAGEMENT	Coordinate multi-vehicle transport; time synchronization; mutual support	2–3	1000–2200 ¤	2–3
SUPPLY CHAIN COORD	Multi-stop delivery chain; optimize sequence; handle interdependencies	2–4	1200–3000 ¤	2–4
THREAT EVASION	Navigate hostile territory; avoid surveillance/ambush; adapt in real-time	3–5	1500–4000 ¤	2–3

Template Structure (Procedural Generation)

ROUTE OPTIMIZATION Contract:

source_location: random city (Hong Kong, Singapore, Mumbai, Shanghai, Bangkok)
destination_location: different city (10–2000 km distance)
cargo_type: general_goods | hazardous_materials | high_value | perishable
payload_mass: 100–10,000 kg (affects fuel cost, vehicle wear)
time_window: flexible (operator has 20–40 turns) or strict (10–20 turns, premium payout if met)
threat_corridor: 0–3 dangerous regions along route (piracy, military, regulatory)
operator_task: plan route using CAR (enter waypoint) / CDR (traverse to next waypoint)
optimization_target: minimize time + fuel + threat exposure
complication: if DRIFT in history, operator can avoid known surveillance corridors
complication: if ICE BREAKER in history, operator can detect & disable checkpoints via cyber
time_limit: varies (15–30 turns depending on distance/threat)
threat_level: 1–2 (straightforward optimization)
reward_formula: base_reward + (time_bonus: if within time window, ×1.25; if early, ×1.5) + (fuel_efficiency: if under fuel budget, ×1.2) + (threat_avoidance: if no incidents, ×1.1)
rep_gain: +0.5–1 per successful delivery; −1 if delayed; −2 if cargo compromised

Example: Hong Kong → Bangkok Delivery

Cargo: general goods, 5000 kg
Time window: flexible (30 turns available; can be done in 15)
Optimal route: Hong Kong (start) → Guangzhou (6 turns) → Hunan (4 turns) → Laos (3 turns) → Bangkok (2 turns) = 15 turns total
Fuel efficiency: tight routing = 20% under budget
Threat: no surveillance corridors on optimal path
Operator calculates route; executes in 14 turns (early bonus)
Reward: 600 + (time bonus 1.5) + (fuel bonus 1.2) + (threat avoidance 1.1) = 600 × 4.3 = 600 + (miscalculation example; actual formula: base + additive bonuses) = 600 + 150 (time) + 120 (fuel) + 60 (threat) = 930 ¤
Rep: +1

CONVOY MANAGEMENT Contract:

convoy_composition: 2–4 vehicles, each with own speed, capacity, vulnerability
vehicle_types: truck (fast, fragile) | armored_vehicle (slow, resilient) | support_truck (medium, critical for convoy cohesion)
synchronization_requirement: vehicles must stay within 2-turn proximity (convoy loses firepower if separated)
rendezvous_points: 3–5 predetermined waypoints where convoy must regroup
operator_task: plan synchronized movement; time each vehicle's departure; coordinate arrivals at rendezvous
timing_precision: if all vehicles arrive within ±1 turn of rendezvous time, cohesion maintained; if ±2 turns, reduced firepower; if >2 turns, convoy fragment
threat_scenario: 2–4 ambush points along route; convoy is vulnerable if separated
time_limit: 20–30 turns (coordination-paced)
threat_level: 2–3 (interdependencies create pressure)
reward_formula: base_reward + (cohesion_bonus: if convoy stays unified, ×1.5; if fragmented, ×0.8) + (speed_bonus: if early, ×1.2)
rep_gain: +1 per successful convoy synchronized; −3 if convoy fragments; −2 per vehicle lost
complication: if BLACK LEDGER in history, operator can monitor cargo value (financial tracking)
complication: if SYNTHFENCE in history, operator can time convoy arrival to market windows (arbitrage timing)

Example: Multi-Vehicle Convoy to Port Authority

3 vehicles: Truck A (fast, 100 kg/turn), Armored B (slow, 50 kg/turn but resilient), Support C (medium, 75 kg/turn)
Distance: 50 km equivalent (requires ~15 turns if all move at same speed)
Rendezvous: 3 points (turn 5, turn 10, turn 15)
Vehicle timing:
- Truck A: departs turn 1; reaches rendezvous 1 at turn 4 (early, but waits for others)
- Armored B: departs turn 1; reaches rendezvous 1 at turn 6 (late by 2, cohesion reduced)
- Support C: departs turn 1; reaches rendezvous 1 at turn 5 (on time)
Operator manages timing; can delay Truck A or accelerate Armored B
Operator decides: delay Truck A by 1 turn → all arrive rendezvous 1 at turn 5 (perfect cohesion)
Continue coordinating rendezvous 2 + 3
All vehicles arrive destination on turn 15 (synchronized)
Reward: 1000 + (cohesion 1.5) + (speed 1.2) = 1000 + 500 + 200 = 1700 ¤
Rep: +2

SUPPLY CHAIN COORDINATION Contract:

supply_chain: 3–5 sequential deliveries, each dependent on previous
node_sequence: Node A (start) → Node B (intermediate, must deliver goods from A) → Node C (intermediate, must have goods from B) → Node D (final destination)
timing_interdependency: if delivery to Node B is late, subsequent nodes are delayed (cascade)
operator_task: optimize entire chain; balance time at each node with interdependencies
time_windows: each node has a "safe window" (e.g., Node B must receive goods between turns 8–12)
threat: multiple threat corridors; operator must choose which to prioritize
time_limit: 30–40 turns (long, complex)
threat_level: 2–4 (cascading failures possible)
reward_formula: base_reward + (on_time_delivery: per node, ×1.1–1.2) + (chain_efficiency: if no cascade delays, ×1.3)
rep_gain: +1 per node delivered on-time; +3 bonus if entire chain perfect
complication: if DRIFT in history, operator can route to avoid signal interception nodes
complication: if SYNTHFENCE in history, operator can time deliveries to market peaks (maximize commodity value)

Example: 4-Node Supply Chain (Semiconductor Parts)

Node A (Hong Kong): start; 500 units to deliver
Node B (Singapore, turns 10–14): receive 500 units from A
Node C (Bangkok, turns 20–24): receive 300 units from B (remaining 200 goes elsewhere)
Node D (Manila, turns 35–40): receive all remaining units from B + C
Operator plans:
- Turn 1–10: Hong Kong → Singapore (10 turns, on-time)
- Turn 11–20: Singapore → Bangkok (9 turns; arrives turn 20, within window)
- Turn 15–35: Singapore → Manila (20 turns)
- Turn 21–40: Bangkok → Manila (10 turns; arrives turn 31, within window)
All deliveries on-time; no cascade
Reward: 1200 + (on-time ×1.1 per node = 1.4 total) + (chain efficiency 1.3) = 1200 × 2.7 = 3240 ¤ (approximation; actual: 1200 + bonuses per node)
Rep: +4 (all nodes on-time + chain perfect bonus)

THREAT EVASION Contract:

threat_scenario: operator must navigate territory with active threats (military checkpoints, pirate zones, surveillance)
threat_types: 4–6 threat zones with different characteristics
  - MILITARY_CHECKPOINT: roadblock at fixed location; can be bypassed by detour (time cost) or passed through (risk of inspection/confiscation)
  - PIRATE_ZONE: mobile threat; randomly positioned; can be detected via DRIFT intelligence or avoided via evasion route
  - SURVEILLANCE_CORRIDOR: RF monitoring; detected via DRIFT signals; evade by taking alternate route
  - TOLL_AUTHORITY: mandatory passage; can be bribed (credit cost), negotiated (rep cost), or avoided (long detour)
operator_task: plan route through threat landscape; adapt in real-time if threats move
real_time_threat_updates: threats may escalate or move; operator receives updates each turn
operator_options: fight (lose credits/cargo), evade (time cost), negotiate (rep cost), bribe (credit cost), hack (if ICE BREAKER loaded)
time_limit: 25–35 turns (reactive, adaptive)
threat_level: 3–5 (highest; threats are active and persistent)
reward_formula: base_reward + (threat_avoidance: per threat avoided, ×1.1) + (cargo_integrity: if no confiscation, ×1.3) + (speed_bonus: if under time, ×1.1)
rep_gain: +2 per threat successfully evaded; +1 per threat negotiated; −1 per threat fought (cargo loss); −2 if cargo confiscated
complication: if DRIFT in history, operator can detect threats in advance (surveillance signals)
complication: if ICE BREAKER in history, operator can disable checkpoints via cyber sabotage
complication: if SYNTHFENCE in history, operator can bribe officials with insider trading profits (credit cost reduced)

Example: Navigate War Zone

Route: Port A → Conflict Zone → Port B (30 km, requires ~15–20 turns)
Threats detected:
- Military checkpoint (turn 8, fixed location)
- Pirate zone (turns 12–16, mobile; position uncertain)
- Toll authority (turn 18, fixed)
- Surveillance zone (turns 5–10, RF detection)
Operator’s strategy:
- Turn 1–5: Navigate under radar (avoid surveillance)
- Turn 6–8: Take detour around military checkpoint (+3 turn cost)
- Turn 9–14: Navigate pirate zone carefully (use DRIFT signals if loaded to detect pirate positions)
- Turn 15–18: Pass through toll authority; negotiate instead of paying (−1 rep, +0 credit cost)
- Turn 19–20: Final push to Port B
All threats evaded; cargo intact
Reward: 1500 + (threat avoidance ×1.1 per threat = ×1.4) + (cargo integrity 1.3) + (speed 1.1) = 1500 × 3.8 (approximation) = 1500 + 700 (avoidance bonuses) + 400 (cargo) + 100 (speed) = 2700 ¤
Rep: +6 (threats evaded + negotiation)

3.3 Deck State Integration

SRAM Writes:

credit_balance — increases significantly (600–4000 ¤ per contract)
reputation_score — increases moderately (+0.5 to +3 per contract)
logistics_index NEW — hidden stat tracking operator’s supply chain knowledge; ranges 0–50; at 40+, unlock exclusive contracts
cartridge_history bit 7 set permanently
threat_map NEW — cumulative knowledge of threat corridors; used by future contracts to generate more realistic threat placements

Reputation Thresholds (PATHFINDER Context):

Rep 0–4: ROUTE OPTIMIZATION only. Single-vehicle, single-stop. No threats.
Rep 5–14: CONVOY MANAGEMENT added. 2 vehicles. Basic synchronization.
Rep 15–24: SUPPLY CHAIN COORDINATION added. 3–4 nodes. Basic interdependencies.
Rep 25–49: THREAT EVASION added. Multiple threat types. Adaptive scenario.
Rep 50+: EXCLUSIVE: WARZONE LOGISTICS (operate in active conflict zones), DIPLOMATIC CONVOY (high-value, high-visibility), UNDERGROUND SUPPLY NETWORK (illegal goods, maximum complexity).

3.4 Cross-Module Interactions

With DRIFT (Signal Tracking):

THREAT EVASION contracts can include “surveillance corridor avoidance.”
DRIFT signals reveal threat locations in advance.
2-phase: detect threat signals via DRIFT → evade route via PATHFINDER.
Operator with DRIFT in history: threat detection difficulty reduced; operator receives automatic alerts when entering surveillance zones.

With SYNTHFENCE (Market Operations):

ROUTE OPTIMIZATION can include “time the arrival to market peaks” (commodity arbitrage).
CONVOY MANAGEMENT can include “transport high-value goods timed to market volatility.”
2-phase: predict market movement via SYNTHFENCE → time delivery route via PATHFINDER → profit from timing advantage.
Operator with SYNTHFENCE in history: can arbitrage cargo value based on delivery timing; exclusive “market window” contracts.

With BLACK LEDGER (Forensic Audit):

SUPPLY CHAIN COORDINATION can include “track money flows through supply chain” (financial forensics).
2-phase: route goods + track financial transaction → audit money trail.
Special mission: MONEY LAUNDERING LOGISTICS—route physical goods to launder financial transactions.
Operator with BLACK LEDGER in history: can hide financial trails through logistics networks.

With ICE BREAKER (Network Intrusion):

THREAT EVASION can include “disable checkpoint ICE via network sabotage.”
2-phase: hack checkpoint system via ICE BREAKER → disable physical checkpoint → proceed via PATHFINDER.
Special mission: CYBER-PHYSICAL SABOTAGE—coordinate network attack with logistics evasion.
Reward: +50% if both phases perfectly timed.

Self-Reference:

Solo PATHFINDER: pure logistics and route optimization.
Paired with DRIFT: threat detection + evasion routing.
Paired with SYNTHFENCE: market-timed logistics.
Paired with BLACK LEDGER: money laundering via supply chain.
Paired with ICE BREAKER: cyber sabotage + physical evasion.

3.5 Multi-Phase Mission Design

Phase Architecture

PATHFINDER supports four primary phase structures:

PLANNING → EXECUTION → COMPLETION (Route Optimization):

PLANNING: Operator analyzes start/end nodes; calculates optimal route.
EXECUTION: Operator navigates each waypoint in sequence.
COMPLETION: Cargo arrives; reward calculated.

COORDINATION → SYNCHRONIZATION → ARRIVAL (Convoy Management):

COORDINATION: Operator assigns departure times to each vehicle.
SYNCHRONIZATION: Operator monitors each vehicle; adjusts timing at rendezvous points.
ARRIVAL: All vehicles reach destination synchronized; reward multiplied by cohesion.

PLANNING → MULTI-LEG EXECUTION → FINAL COMPLETION (Supply Chain):

PLANNING: Operator maps entire 4–5 node chain; calculates time windows.
MULTI-LEG: Operator executes each leg; monitors interdependencies.
COMPLETION: All nodes delivered on-time; cascade avoided.

THREAT DETECTION → EVASION → ESCAPE (Threat Evasion):

THREAT DETECTION: Operator identifies active threats via DRIFT signals or direct observation.
EVASION: Operator plots safe route through threat landscape; adapts in real-time as threats move.
ESCAPE: Operator reaches destination with cargo intact.

Worked Example 1: Simple Route Optimization (1–2 Phase)

Mission: “HONG KONG → BANGKOK DELIVERY”

Phase 1 (PLANNING): Operator analyzes map; identifies optimal route.
- Hong Kong → Guangzhou (6 turns) → Hunan (4 turns) → Laos (3 turns) → Bangkok (2 turns)
- Total: 15 turns (within 30-turn time window)
Phase 2 (EXECUTION): Operator navigates route.
- Executes in 14 turns (early); completes under time window
- No threats on optimal path
Reward: 600 + 150 (time bonus) + 120 (fuel bonus) + 60 (threat avoidance) = 930 ¤
Rep: +1
Duration: 16 turns

Worked Example 2: Convoy Synchronization (2–3 Phase)

Mission: “MULTI-VEHICLE SYNC CONVOY”

Phase 1 (COORDINATION): Operator assigns departure times.
- Truck A: depart turn 1
- Armored B: depart turn 0 (early, slow vehicle)
- Support C: depart turn 1
Phase 2 (SYNCHRONIZATION): Operator monitors movements; adjusts timing.
- Turn 5: Rendezvous 1 (all vehicles within ±1 turn; cohesion maintained)
- Turn 10: Rendezvous 2 (Armored B arrives turn 11, ±1 tolerance; cohesion maintained)
- Turn 15: Rendezvous 3 (perfect arrival)
Phase 3 (ARRIVAL): All vehicles reach destination turn 15 (synchronized).
Reward: 1000 + 500 (cohesion) + 200 (speed) = 1700 ¤
Rep: +2
Duration: 15 turns

Worked Example 3: Supply Chain Coordination (3–4 Phase, 30+ turns)

Mission: “4-NODE SEMICONDUCTOR SUPPLY CHAIN”

Phase 1 (PLANNING): Operator maps node sequence and time windows.
- A (start) → B (turns 10–14) → C (turns 20–24) → D (turns 35–40)
- Plan: A→B 10 turns, B→C 9 turns (arrive turn 20), B→D 20 turns, C→D 10 turns (arrive turn 31)
Phase 2–4 (MULTI-LEG EXECUTION):
- Leg A→B (turns 1–10): execute; arrive turn 10 (within window)
- Leg B→C (turns 11–20): execute; arrive turn 20 (within window)
- Leg B→D (turns 11–31): parallel track; coordinate with Leg B→C
- Leg C→D (turns 21–31): execute; arrive turn 31 (within window)
All nodes on-time; no cascade failures
Reward: 1200 + (on-time bonuses) + (chain efficiency 1.3) = 2700+ ¤
Rep: +4 (all nodes on-time + perfect chain bonus)
Duration: 35 turns

Worked Example 4: Threat Evasion (2–3 Phase, 25+ turns)

Mission: “NAVIGATE WAR ZONE”

Phase 1 (THREAT DETECTION): Operator identifies threats.
- Military checkpoint (turn 8, fixed)
- Pirate zone (turns 12–16, mobile)
- Toll authority (turn 18, fixed)
- Surveillance zone (turns 5–10, RF-based)
Phase 2 (EVASION): Operator plots safe route.
- Turns 1–5: navigate under radar (avoid surveillance)
- Turns 6–8: take detour around military checkpoint (+3 turn cost)
- Turns 9–14: navigate pirate zone (use DRIFT signals if loaded)
- Turns 15–18: negotiate toll authority (−1 rep, no credit cost)
- Turns 19–20: final push to destination
Phase 3 (ESCAPE): Cargo arrives intact.
Reward: 1500 + (threat avoidance bonuses) + (cargo integrity 1.3) = 2700+ ¤
Rep: +6 (threats evaded + negotiation)
Duration: 20 turns

3.6 Capability Progression

Proficiency Tiers (PATHFINDER-Specific):

Tier 1: Apprentice (Rep 0–4, Proficiency 0–15)

Route options shown as simple linear list (A → B → C)
Operator manually selects each waypoint (no pathfinding; simple traversal)
Time estimates are hidden; operator learns through trial
Audio: YM2149 Voice 1 (tempo) plays slow, steady tone; operator learns route “tempo”
Cipher voice: instructive (“Pick a waypoint. CAR into it. See how long it takes. That’s your route time.”)

Tier 2: Novice (Rep 5–14, Proficiency 16–35)

Route options shown as a map (ASCII art; visual waypoints)
Time estimates are visible for each leg
Operator can see threat corridors marked on map
Audio: Voice 2 (distance/time) modulates frequency as operator plans (higher pitch = longer route)
Cipher voice: professional (“This route is 15 turns. That one’s 20 but avoids the checkpoint. You choose.”)

Tier 3: Competent (Rep 15–24, Proficiency 36–55)

Route optimization is semi-automated; operator reviews top 3 optimal routes
Operator can see real-time threat updates on map
Convoy synchronization is visual (time windows shown graphically)
Audio: Voice 3 (threat) reflects active threat count; more threats = louder dissonance
Cipher voice: sparse (“The direct route is 12 turns but passes through pirate zone. Detour adds 5 turns. Decide.”)

Tier 4: Expert (Rep 25–49, Proficiency 56–75)

Route optimization is fully automatic; operator reviews single optimal route
Operator can see detailed threat analysis (threat severity, evasion difficulty)
Convoy dynamics are abstract; operator manages timing without conscious calculation
Audio: all three YM2149 voices encode route data simultaneously; operator reads route “by ear”
Cipher voice: cryptic (“The path sings. Listen to its length.”)

Tier 5: Master (Rep 50+, Proficiency 76+)

Route planning is unconscious; operator executes optimal route without reviewing it
Convoy management is somatic; operator times vehicles intuitively
Threat evasion is reaction-based; operator adapts to threats automatically
Audio: operator’s keypresses are synchronized with YM2149; route execution becomes musical
Cipher voice: silent, except for rare nod (“You are the road.”)

3.7 Contract Economics

Payout Formula:

base_reward = distance_bonus + complexity_bonus
time_bonus = (time_remaining / time_limit) × base_reward × 0.20
efficiency_bonus = (fuel_saved / fuel_budget) × base_reward × 0.15
threat_bonus = (threats_avoided / total_threats) × base_reward × 0.25
final_payout = base_reward + time_bonus + efficiency_bonus + threat_bonus

Examples:

Route Optimization (Hong Kong → Bangkok):
- Base: 600 ¤ (distance 15 turns)
- Time bonus: executed in 14 turns of 30-turn window; (16/30) × 600 × 0.20 = 64 ¤
- Efficiency bonus: used 20% less fuel than budget; 0.20 × 600 × 0.15 = 18 ¤
- Threat bonus: avoided all threat corridors; 1.0 × 600 × 0.25 = 150 ¤
- Final: 600 + 64 + 18 + 150 = 832 ¤
Convoy Synchronization (3 vehicles):
- Base: 1000 ¤ (3-vehicle coordination)
- Cohesion bonus: perfect synchronization (all arrivals within ±1 turn); ×1.5 multiplier = +500 ¤
- Time bonus: completed in 15 turns of 20-turn window; (5/20) × 1000 × 0.20 = 50 ¤
- Final: 1000 + 500 + 50 = 1550 ¤
Supply Chain (4-node):
- Base: 1200 ¤ (4-node complexity)
- On-time delivery bonus: all 4 nodes on-time; ×1.1 per node = ×1.4 total = +480 ¤
- Chain efficiency bonus: no cascade delays; ×1.3 = +360 ¤
- Time bonus: completed in 35 turns of 40-turn window; (5/40) × 1200 × 0.20 = 30 ¤
- Final: 1200 + 480 + 360 + 30 = 2070 ¤
Threat Evasion (War Zone):
- Base: 1500 ¤ (high-threat scenario)
- Threat avoidance bonus: 4 of 5 threats evaded; (4/5) × 1500 × 0.25 = 300 ¤
- Cargo integrity bonus: no confiscation; ×1.3 = +450 ¤
- Time bonus: completed in 20 turns of 30-turn window; (10/30) × 1500 × 0.20 = 100 ¤
- Final: 1500 + 300 + 450 + 100 = 2350 ¤

Risk/Reward Curve Table:

Contract Type	Threat	Base Pay	Time Limit	Bonus Potential	Rep Gain	Risk
ROUTE OPTIMIZATION	1–2	600–900 ¤	20–30 turns	30–50% of base	+0.5–1	Low
CONVOY MANAGE	2–3	1000–1500 ¤	20–25 turns	40–60% of base	+1–2	Medium
SUPPLY CHAIN	2–4	1200–1800 ¤	30–40 turns	50–80% of base	+2–4	Medium-High
THREAT EVASION	3–5	1500–2500 ¤	20–35 turns	40–70% of base	+2–6	High

Exclusive High-Rep Operations:

WARZONE LOGISTICS (Rep 50+, threat_map 40+): Operate in active conflict zone. Base: 3500 ¤, up to 8000 ¤ if all cargo reaches destination. Rep: +8.
DIPLOMATIC CONVOY (Rep 50+, reputation 50+): High-profile, high-visibility transport. Base: 4000 ¤. Rep: +10 (or −10 if mission fails; massive swing).
UNDERGROUND SUPPLY NETWORK (Rep 50+, illegal_goods_index present): Transport illegal goods through multiple jurisdictions. Base: 3000 ¤, up to 8000 ¤ if successful. Rep: +8 (or −8 if caught). Highly risky, highly rewarding.

3.8 Operator Workflow

Typical Single-Session (40 min):

Pre-Session Check (2 min): Load PATHFINDER. Review contract board. Cipher voice: “Three routes open. Hong Kong, Singapore, Mumbai. Time is money.”
Contract Selection (1 min): Operator chooses ROUTE OPTIMIZATION (quick, reliable).
Mission Execution (22 min):
- Operator plans route: Hong Kong → Guangzhou → Hunan → Laos → Bangkok (15 turns planned)
- Executes route; navigates waypoints
- Completes in 14 turns (1 turn early)
- Reward: 832 ¤
- Rep: +1
Optional Second Contract (15 min): Operator can run another ROUTE OPTIMIZATION or attempt CONVOY MANAGEMENT (longer, more complex).
- Chooses CONVOY MANAGEMENT (2-vehicle, 3 rendezvous)
- Plans synchronization carefully
- Executes in 12 turns
- Reward: 1400 ¤
- Rep: +1.5
Debrief (2 min): Cipher voice: “Two efficient runs. Your logistics skills are improving. Proficiency +2.” Total credits: 2232 ¤. Rep: +2.5.

Total Session Earnings: 2232 ¤, Rep +2.5. Proficiency +2. Time: 40 minutes.

Multi-Session Campaign (2 weeks):

Day 1–2: Three ROUTE OPTIMIZATION contracts. Earn 2500 ¤, Rep +2. Total rep: 2.
Day 3–4: Two CONVOY MANAGEMENT contracts. Earn 2800 ¤, Rep +3. Total rep: 5. Tier: Novice (Rep 5) reached.
Day 5–6: One SUPPLY CHAIN contract (new type). Earn 2000 ¤, Rep +3. Total rep: 8.
Day 7: Two quick ROUTE OPTIMIZATION (warm-up). Earn 1500 ¤, Rep +1. Total rep: 9.
Day 8–10: THREAT EVASION contracts (new type). Earn 5000+ ¤, Rep +10. Total rep: 19. Tier: Competent (Rep 15) reached.
Day 11–14: Mixture of all contract types; earn 6000+ ¤, Rep +8. Total rep: 27. Tier: Expert (Rep 25) reached. Logistics_Index: 35.

Two-Week Summary: 20,000+ ¤ earned, Rep +27, Logistics_Index +35. Operator reaches Expert tier and approaches exclusive contract eligibility.

Expert Operator (Rep 50+) Routine:

Weekly: one WARZONE LOGISTICS (high-stakes, 1–2 hours, 8000 ¤ if successful).
Bi-weekly: one DIPLOMATIC CONVOY (high-visibility, 4000+ ¤).
Monthly: UNDERGROUND SUPPLY NETWORK (long-term, illegal goods, 3000–8000 ¤).
Maintenance: occasional ROUTE OPTIMIZATION for steady income (800–1000 ¤ per session, minimal time).

3.9 Cipher Voice Integration

Cipher’s tone in PATHFINDER: pragmatic logistics advisor, increasingly philosophical at high rep.

On Load (Apprentice):

“PATHFINDER initialized. You’re now responsible for cargo. Pick a route. Time matters. Money matters more. Let’s move product.”

During ROUTE OPTIMIZATION (Apprentice):

“Hong Kong to Bangkok. 15 turns if you go direct. 20 turns if you detour around the checkpoint. Which is worth the risk?”

During CONVOY MANAGEMENT (Novice):

“Three vehicles. Different speeds. You need them synchronized at rendezvous points. One’s late, you lose firepower. Time them right.”

During SUPPLY CHAIN (Competent):

“Four nodes. Five days window. One late delivery cascades to all the others. Plan your sequence carefully.”

During THREAT EVASION (Expert):

“Five threats in your territory. Military. Pirates. Toll authority. Surveillance. Surveillance. You need to navigate through them without losing cargo. Or lose minimal cargo. Or bribe your way through. Or hack the checkpoint. Your call.”

At Rep 50+ (Master, WARZONE):

“The war is moving. Checkpoints shift. You’re not just reading terrain anymore. You’re reading conflict. The route is the metaphor. The road teaches.”

Success (Perfect Convoy Sync):

“All vehicles arrived within one turn. Perfect synchronization. That’s not logistics anymore. That’s music.”

Failure (Cargo Confiscated):

“They took the cargo at checkpoint seven. You miscalculated. Mission failed. Walk it off. There’s another run waiting.”

Domain Vocabulary (CIPHER_DOMAIN):

route, waypoint, rendezvous, checkpoint, threat_corridor, safe_passage
convoy, vehicle, synchronization, cohesion, fragmentation, mutual_support
cargo, payload, supply_chain, delivery, on_time, cascade, interdependency
threat, ambush, pirate, military, surveillance, toll_authority, evasion
logistics, optimization, efficiency, time_window, threat_map, geography
departure, arrival, timing, coordination, adaptation, disruption

3.10 Cell Architecture

PATHFINDER defines the logistics primitive:

CELL_TYPE ROUTE {
  ON_CAR: get_waypoint_list() -> returns list of WAYPOINT
  ON_CDR: get_next_waypoint() -> returns WAYPOINT
  ON_EVAL: optimize() -> calculates shortest/safest route; returns OPTIMIZED_ROUTE
};

CELL_TYPE WAYPOINT {
  ON_CAR: get_location() -> returns (lat, lon)
  ON_CDR: get_adjacent_waypoints() -> returns list of WAYPOINT
  ON_EVAL: arrive() -> updates cargo status; checks time window
};

CELL_TYPE CONVOY {
  ON_CAR: get_vehicle_list() -> returns list of VEHICLE
  ON_CDR: get_next_rendezvous() -> returns RENDEZVOUS_POINT
  ON_EVAL: synchronize() -> checks cohesion; applies cohesion_bonus or cohesion_penalty
};

CELL_TYPE VEHICLE {
  ON_CAR: get_speed() -> returns turns_per_leg
  ON_CDR: get_capacity() -> returns cargo_units
  ON_EVAL: depart(time) -> schedules departure; returns travel_time
};

CELL_TYPE RENDEZVOUS_POINT {
  ON_CAR: get_location() -> returns (lat, lon)
  ON_CDR: get_arrival_window() -> returns (earliest_turn, latest_turn)
  ON_EVAL: check_cohesion() -> returns (all_on_time | some_late | fragmented)
};

CELL_TYPE THREAT {
  ON_CAR: get_type() -> returns (MILITARY | PIRATE | TOLL | SURVEILLANCE)
  ON_CDR: get_location() -> returns (lat, lon) or (if mobile, current_position)
  ON_EVAL: evade() -> calculates detour_cost; returns (success | failure)
};

CELL_TYPE THREAT_EVASION {
  ON_CAR: get_threat_list() -> returns list of THREAT
  ON_CDR: get_safe_corridor() -> returns alternate_route
  ON_EVAL: navigate() -> attempts safe passage; returns (cargo_intact | cargo_damaged | capture)
};

Composition Example (Simple Route):

(LOGISTICS_OPERATION
  (ROUTE
    (WAYPOINT "Hong Kong" 22.3N 114.2E)
    (WAYPOINT "Guangzhou" 23.1N 113.3E turn-6)
    (WAYPOINT "Hunan" 28.2N 113.0E turn-10)
    (WAYPOINT "Laos" 18.8N 104.6E turn-13)
    (WAYPOINT "Bangkok" 13.7N 100.5E turn-15))
  (CARGO 5000kg general_goods)
  (TIME_WINDOW 30-turns flexible))

Operator CAR into route; navigates each waypoint. CDR to move to next waypoint. EVAL at each waypoint to check arrival and update cargo status.

3.11 Sound Design as Interface

YM2149 in PATHFINDER: route rhythm as tempo, distance as frequency, threat as dissonance.

Voice 1 (Square Wave): Route distance/time. Frequency = route_length / 20 × 500 Hz (normalized).

15-turn route → 375 Hz (mid-range tone)
30-turn route → 750 Hz (higher pitch)
8-turn route → 200 Hz (low pitch)
Operator learns to “hear” route length before viewing display

Voice 2 (Sawtooth): Progression through route. Frequency increases as operator advances through waypoints.

At start: 300 Hz
At 25% progress: 400 Hz
At 50% progress: 500 Hz
At 75% progress: 600 Hz
At destination: 700 Hz (arrival note)
Operator learns to “feel” progress by ear; can navigate with eyes closed

Voice 3 (Noise + Envelope): Threat activity. Voice 3 plays dissonant tones when threats are nearby.

Threat detected: dissonant tritone (alarm)
Threat avoided: Voice 3 drops out (relief)
Threat engaged: harsh noise burst (warning)

Key Audio Events:

ROUTE LOADED: Voice 1 plays at distance-proportional frequency; holds steady. Operator knows route length.
WAYPOINT REACHED: Voice 2 rises to next pitch level (25% progress, 50%, etc.). Operator senses completion milestone.
CONVOY SYNCHRONIZATION: All three voices converge (harmonic alignment) at each rendezvous point. Operator hears “cohesion.”
CONVOY FRAGMENT: Voice 1 + 2 diverge (harmonic split); Voice 3 plays warning dissonance. Operator immediately senses synchronization loss.
THREAT DETECTED: Voice 3 plays dissonant tone (−−− tritone, warning). Operator learns to recognize threat aurally before seeing display.
THREAT EVADED: Voice 3 drops out; silence. Operator senses safe passage.
DESTINATION REACHED: Rising major arpeggio (C → E → G → C’); all three voices converge. Operator’s “arrival” reward signal.
CARGO CONFISCATED: All voices stop abruptly; replaced by falling minor arpeggio (dissonant resolution). Operator’s “failure” signal.

3.12 Link Protocol

PATHFINDER has asymmetric linked play for logistics coordination:

DISPATCHER Role (Primary):

Plans multi-vehicle supply chain
Sends waypoint sequence and time windows to OPERATOR deck via cable
Sends threat corridor map (real-time updates)
Real-time: DISPATCHER sees OPERATOR’s vehicle synchronization progress

OPERATOR Role (Executor):

Receives waypoint sequence
Receives time windows for each waypoint
Receives threat corridor map
Must execute synchronized delivery; report status in real-time

Data Flow:

Dispatcher Deck:
  -> waypoint_sequence (list of delivery nodes)
  -> time_windows (safe arrival window for each waypoint)
  -> threat_corridor_map (active threats, RF signals, toll authority)
  -> vehicle_synchronization_data (real-time view of operator's convoy timing)

Operator Deck:
  <- waypoint_sequence (rendered locally as map)
  <- time_windows (deadline notifications)
  <- threat_corridor_map (displayed as hazard zones)
  -> synchronization_status (vehicle arrivals, timing, cohesion)

Linked Example: Multi-Operator Supply Chain

Dispatcher (Expert) plans a 3-stop supply chain:

Stop A (Hong Kong): Dispatcher loads 500 units; assigns window 0–12 turns
Stop B (Singapore): Dispatcher assigns window 15–20 turns (B must receive goods from A, then forward to C)
Stop C (Bangkok): Dispatcher assigns window 25–35 turns (C receives goods from B)

Operator (Novice) receives sequence + windows on deck:

Sees waypoints: Hong Kong → Singapore → Bangkok
Sees time windows: A (0–12), B (15–20), C (25–35)
Sees threat corridor: pirate zone near Singapore (turns 18–22)

Operator executes:

Departs Hong Kong turn 0 with 500 units
Arrives Singapore turn 10 (within window 15–20? No, too early. Operator must wait at waypoint or find alternate route)
Decides: wait at Singapore until turn 15 (allows turnaround time before B→C leg)
Departs Singapore turn 15 with remaining units (some distributed at B; some forwarded to C)
Arrives Bangkok turn 25 (within window 25–35)
All deliveries on-time; Operator earns rep +2; Dispatcher earns rep +1 (for good logistics planning)

Cooperative Variant: Multiple operators coordinate on same supply chain. Operator A handles Hong Kong → Singapore; Operator B handles Singapore → Bangkok. Real-time handoff at Singapore requires both operators’ timing synchronization. High coordination difficulty; high rep gain for success.

END OF SPECIFICATIONS

Total Document: ~15,000 words across three complete modules.

Each module includes:

Full identity and context (1.1)
Comprehensive mission template architecture with 4 contract types and 2+ worked examples per type (1.2)
Deck state integration and reputation thresholds (1.3)
Cross-module interaction matrix (1.4)
Multi-phase mission design with 3+ worked examples (1.5)
5-tier capability progression (1.6)
Detailed contract economics with worked examples and risk/reward curves (1.7)
Operator workflow (single-session and multi-session examples) (1.8)
Cipher voice integration with 6–8 example lines and domain vocabulary (1.9)
Cell architecture in C-style pseudocode with composition examples (1.10)
YM2149 sound design as interface (1.11)
Link protocol with worked examples (1.12)

All modules follow ICE Breaker quality bar: emergent gameplay, OODA-loop thinking, sound as information, procedural generation with personality, session structures respecting operator time, and cross-module interactions that are additive, never subtractive.