Initialize Mission 4: Critical Failure

Create M4 infrastructure defense mission initialization: - Water treatment facility SCADA attack scenario - ENTROPY Cell: Critical Mass - SecGen: Vulnerability Analysis (Nmap/Nessus, distcc, sudo Baron) - Estimated playtime: 60-80 minutes - Difficulty: Intermediate (Tier 2) New mechanics introduced: - Hostile NPCs (first combat encounter) - Item drops from defeated enemies - Time-pressure objectives (30-min timer) - Multi-system investigation Educational focus: - Cyber-Physical Systems (SCADA/ICS security) - Security Operations (vulnerability scanning, threat hunting) - Systems Security (privilege escalation) Campaign connections: - Cross-cell coordination (Critical Mass + Social Fabric) - The Architect's infrastructure initiative - Setup for Task Force Null (M5-10) Mission represents transition from reconnaissance to active crisis response with combat. First mission with time pressure and hostile combatants. Ready for Stage 1 development.
2026-02-20 13:50:46 +00:00 · 2026-01-14 09:46:33 +00:00
parent 02e519e3fe
commit ac8e319560
1 changed files with 426 additions and 0 deletions
--- a/planning_notes/overall_story_plan/mission_initializations/m04_critical_failure/README.md
+++ b/planning_notes/overall_story_plan/mission_initializations/m04_critical_failure/README.md
@@ -0,0 +1,426 @@
+# Mission 4: "Critical Failure" - Development Preparation
+
+**Mission ID:** m04_critical_failure
+**Title:** Critical Failure
+**Status:** 🔄 READY FOR STAGE 0 INITIALIZATION
+**Prepared:** 2025-12-28
+**Development Process:** 9-Stage Scenario Development Workflow
+
+---
+
+## Executive Summary
+
+Mission 4 "Critical Failure" is an infrastructure defense mission where players must prevent a catastrophic attack on a water treatment facility's SCADA systems. This mission introduces hostile NPCs (combat), time-pressure objectives, and multi-system investigation while reinforcing all previously learned mechanics.
+
+**Key Metrics (Target):**
+- **Difficulty:** Intermediate (Mission 4 of Season 1)
+- **Estimated Playtime:** 60-80 minutes
+- **ENTROPY Cell:** Critical Mass
+- **SecGen Scenario:** "Vulnerability Analysis" (Nmap/Nessus scanning, distcc + sudo Baron privilege escalation)
+- **CyBOK Areas:** Cyber-Physical Systems, Security Operations, Systems Security
+- **New Mechanics:** Hostile NPCs (combat), item drops from enemies, time-pressure objectives, multi-system investigation
+
+---
+
+## Mission Overview from Season 1 Arc
+
+### Story Premise
+
+Water treatment facility's SCADA systems show suspicious activity. SAFETYNET suspects ENTROPY's Critical Mass cell is planning infrastructure attack. Player must infiltrate facility, secure systems, and prevent contamination crisis—all while facility remains operational.
+
+### Core Challenges (Break Escape)
+
+- **All previous mechanics** (lockpicking, guards, RFID, social engineering)
+- **Hostile NPCs** (NEW) - ENTROPY operatives already infiltrated facility
+- **Multi-stage investigation** - identify which systems compromised
+- **Time pressure** - prevent scheduled attack
+
+### VM Challenge Integration
+
+**SecGen "Vulnerability Analysis":**
+- Scan SCADA network to identify vulnerabilities
+- Exploit distcc vulnerability to access compromised systems
+- Escalate privileges using sudo Baron vulnerability
+- Secure systems and identify attack timeline
+
+**Narrative Context:**
+- Critical Mass has already compromised facility systems
+- Player must identify attack vector before scheduled chemical dosing attack
+- VM challenges represent accessing and securing critical infrastructure
+- Scanning and exploitation simulate defensive penetration testing under crisis
+
+### Educational Objectives (CyBOK)
+
+- **Cyber-Physical Systems:** SCADA security, ICS vulnerabilities, critical infrastructure
+- **Security Operations:** Vulnerability scanning, threat hunting, defensive operations
+- **Systems Security:** Privilege escalation, system hardening
+
+### Narrative Arc (3 Acts)
+
+**Act 1: Undercover Emergency (15-20%)**
+- Emergency briefing - Critical Mass cell detected
+- Infiltrate as "emergency security auditor"
+- Discover facility already compromised
+
+**Act 2: Investigation & Combat (50-60%)**
+- Combat hostile ENTROPY operatives (first physical combat)
+- Secure server room access
+- Scan SCADA network
+- Discover scheduled chemical dosing attack
+- Exploit vulnerable systems to gain access and identify attack vector
+
+**Act 3: Crisis & Choice (20-30%)**
+- Race against time to disable attack
+- Choice - subtle disabling (ENTROPY doesn't know) vs. obvious shutdown (secure but alerts cell)
+- Confront or capture ENTROPY field team
+- Consequences of choice affect facility operations
+
+### Key NPCs
+
+- **Robert Chen** (Facility Manager) - Initially suspicious of player, becomes ally
+- **"Voltage" & Team** (Critical Mass operatives) - Hostile combatants, can be captured
+- **Agent 0x99** (Remote support) - Provides real-time intelligence during crisis
+
+---
+
+## Game Mechanics Introduced
+
+12. **Hostile NPCs (combat)** - First combat encounter with ENTROPY operatives
+13. **Item drops from defeated enemies** - Keycards, passwords, intelligence docs
+14. **Time-pressure objectives** - 30-minute in-game timer for critical path
+15. **Multi-system investigation** - Correlate evidence from SCADA, network, and physical systems
+
+---
+
+## LORE Opportunities
+
+- **Critical Mass Operational Plans** - Reference "OptiGrid Solutions" cover company
+- **Cross-Cell Coordination** - Attack coordinated with Social Fabric disinformation (prepare public panic narrative)
+- **Test Run Documentation** - Communications show attack is "test run" for larger operation
+- **The Architect's Infrastructure Initiative** - Reference to broader ENTROPY infrastructure strategy
+
+---
+
+## Moral Complexity
+
+**Major Choice:** Capture operatives for intel (risk attack proceeding) vs. stop attack immediately (operatives escape)
+
+**Secondary Choice:** Publicly expose facility vulnerabilities (protect public, damage facility reputation) vs. quiet patch (facility reputation intact, public uninformed of risk)
+
+**Tertiary Consideration:** SCADA security is woefully inadequate—is the real villain the facility's negligence?
+
+---
+
+## Success Outcomes
+
+- **Full Success:** Attack prevented, operatives captured, vulnerabilities patched, no public panic
+- **Partial Success:** Attack prevented but operatives escape, or minor contamination occurred
+- **Minimal Success:** Attack prevented but significant consequences (public panic, facility damage)
+
+---
+
+## Connection to Campaign Arc
+
+- **MAJOR REVELATION:** Critical Mass coordinating with Social Fabric (M1 cell) for combined infrastructure + disinformation attack
+- Pattern confirmed: ENTROPY cells working together under coordination
+- "The Architect" now central focus of investigation
+- Sets up infrastructure theme for later missions
+
+**Post-Mission Debrief Revelation:**
+SAFETYNET intelligence shows similar coordinated attacks planned globally. The Architect is coordinating multi-cell operations on unprecedented scale. Player is assigned to "Task Force Null" - hunting The Architect.
+
+---
+
+## Technical Requirements
+
+### SCADA/ICS Environment
+
+**Facility Systems:**
+- Water treatment SCADA control systems
+- Chemical dosing automation
+- Monitoring and telemetry systems
+- Facility network infrastructure
+
+**Security Concerns:**
+- Legacy systems with known vulnerabilities
+- Air-gapped networks (theoretically)
+- Limited security monitoring
+- Operational necessity vs. security trade-offs
+
+### VM Network Topology
+
+**Network Segments:**
+- Corporate IT network (entry point)
+- SCADA control network (target)
+- Safety/monitoring systems (secondary)
+- Backup/maintenance systems (intelligence source)
+
+**Key Services:**
+- distcc vulnerable service (exploitation target)
+- sudo Baron privilege escalation (access control bypass)
+- Nmap/Nessus scanning context (vulnerability assessment)
+
+---
+
+## Combat System Requirements
+
+### Hostile NPC Behaviors
+
+**"Voltage" (Leader):**
+- Alert and tactical
+- Calls for backup if player detected
+- Attempts to trigger attack if cornered
+
+**Field Operatives (2-3):**
+- Patrol patterns in facility
+- Guard critical systems
+- Drop keycards and intelligence when defeated
+
+### Combat Mechanics
+
+**Player Options:**
+- Stealth takedowns (non-lethal, silent)
+- Direct combat (faster but alerts others)
+- Avoidance (slower but safest)
+
+**Consequences:**
+- Alerted operatives trigger faster attack timeline
+- Defeated operatives drop useful items
+- Captured operatives provide intelligence
+
+---
+
+## Time Pressure System
+
+### Timer Mechanics
+
+**30-Minute In-Game Timer:**
+- Visible countdown on screen
+- Attack triggers at 00:00
+- Tension increases as timer depletes
+
+**Time Extensions:**
+- Disable attack staging systems (+5 minutes)
+- Capture operative and extract info (+3 minutes)
+- Find attack timeline documents (+2 minutes)
+
+**Failure State:**
+- Attack succeeds if timer reaches zero
+- Partial contamination event occurs
+- Mission failure but not game over (continue with consequences)
+
+---
+
+## Room Design Considerations
+
+### Facility Layout (7-8 Rooms)
+
+1. **Main Entrance/Security** - Entry point, security checkpoint
+2. **Administration Offices** - Robert Chen's office, employee areas
+3. **Control Room** - SCADA monitoring, critical systems
+4. **Server Room** - Network infrastructure, VM access point
+5. **Chemical Storage** - Dosing systems (attack target)
+6. **Treatment Floor** - Water treatment tanks and equipment
+7. **Maintenance Wing** - Backup systems, hostile NPC stronghold
+8. **Outdoor Access** (Optional) - Emergency exit, perimeter
+
+### Critical Path
+
+**Minimum Required:**
+1. Enter facility (social engineering or stealth)
+2. Locate compromised systems (investigation)
+3. Access server room (lockpicking/RFID)
+4. Scan and exploit network (VM challenges)
+5. Identify attack vector
+6. Disable attack mechanism (final challenge)
+7. Confront or evade operatives
+
+---
+
+## Asset Requirements
+
+### Character Models
+
+**NPCs:**
+- Robert Chen (Facility Manager) - Professional, stressed
+- Agent 0x99 (Phone/Radio) - Remote support
+- Voltage (Critical Mass Leader) - Tactical, hostile
+- Critical Mass Operatives (×3) - Combat NPCs
+
+**Player:**
+- Combat animations (takedown, combat, defeat)
+
+### Environment Assets
+
+**Industrial Facility:**
+- SCADA control panels and monitors
+- Chemical storage tanks
+- Water treatment equipment
+- Industrial office spaces
+- Server racks and network equipment
+
+**UI Elements:**
+- Timer display
+- Combat indicators
+- System status monitors
+- Alert levels
+
+### Sound Design
+
+**Combat:**
+- Takedown sounds
+- Alert notifications
+- Operative communications
+- Weapon/tool sounds (non-lethal)
+
+**Environment:**
+- Machinery hum
+- Water processing sounds
+- Chemical pump sounds
+- Alarm systems
+
+---
+
+## Narrative Tone & Themes
+
+### Tone Shifts
+
+**Opening:** Urgent crisis response, professional
+**Mid-Game:** Escalating tension, paranoia (facility already compromised)
+**Combat:** Action-thriller intensity
+**Climax:** Race-against-time desperation
+**Resolution:** Reflection on infrastructure vulnerability
+
+### Thematic Elements
+
+**Primary Theme:** Critical infrastructure vulnerability in digital age
+**Secondary Theme:** Cross-cell ENTROPY coordination (escalation from previous missions)
+**Tertiary Theme:** Responsibility—whose fault is inadequate security?
+
+**Questions Raised:**
+- Is stopping individual attacks enough when infrastructure is fundamentally insecure?
+- Should players expose vulnerabilities publicly to force change?
+- Are profit-driven corners cut worth the security risks?
+
+---
+
+## Integration with Previous Missions
+
+### Callbacks & Connections
+
+**From M1 (First Contact):**
+- Social Fabric mentioned in coordination documents
+- Similar "acceptable losses" calculation for contamination
+- Public panic strategy mirrors Operation Shatter
+
+**From M2 (Ransomed Trust):**
+- Similar crisis response scenario
+- Infrastructure targeting pattern established
+- Facility manager parallels hospital CTO's desperation
+
+**From M3 (Ghost in the Machine):**
+- Zero Day Syndicate potentially supplied exploits to Critical Mass
+- Coordination between ENTROPY cells now explicit
+- The Architect's role in planning confirmed
+
+### Cross-Mission Consequences
+
+**If M3 Victoria was recruited as double agent:**
+- Victoria provides warning about Critical Mass operation
+- Player arrives earlier, more time to prepare
+
+**If M2 ransom was paid:**
+- Financial trail connects to Critical Mass funding
+- Additional intelligence available
+
+---
+
+## Development Roadmap Reference
+
+### Stage Sequence (9-Stage Process)
+
+- **Stage 0:** Mission initialization (this document) ✓
+- **Stage 1:** Narrative structure and story arc
+- **Stage 2:** Atmosphere and environment design
+- **Stage 3:** Character development and NPC design
+- **Stage 4:** Player objectives and task structure
+- **Stage 5:** Room design and puzzle layout
+- **Stage 6:** LORE fragments and collectibles
+- **Stage 7:** Ink dialogue scripting
+- **Stage 8:** Validation and quality review
+- **Stage 9:** Scenario assembly and implementation
+
+---
+
+## Critical Innovations in M4
+
+### New Elements
+
+1. **Combat System** - First mission with hostile NPCs requiring combat
+2. **Time Pressure** - Real-time countdown affecting player decisions
+3. **Multi-System Investigation** - Correlate evidence from physical, network, and SCADA systems
+4. **Item Drops** - Defeated enemies drop useful items
+5. **Crisis Decision-Making** - Choose between tactical and strategic outcomes
+
+### Risk Mitigation
+
+**Combat Difficulty:**
+- Make stealth viable alternative to combat
+- Provide multiple approaches to each combat encounter
+- Ensure defeat doesn't equal game over
+
+**Timer Stress:**
+- Provide clear feedback on remaining time
+- Allow time extensions through gameplay
+- Make timer pause during critical dialogues/cutscenes
+
+**SCADA Complexity:**
+- Abstract technical details appropriately for gameplay
+- Provide in-game tutorials for SCADA concepts
+- Make VM challenges accessible to intermediate players
+
+---
+
+## Success Criteria
+
+### Gameplay Metrics
+
+- **Completable:** 95%+ of playtesters complete mission in 60-80 minutes
+- **Engaging Combat:** 80%+ report combat was fair and enjoyable
+- **Time Pressure:** 70%+ report timer created tension without frustration
+- **Moral Choice:** 50/50 split on major choice (indicates balanced options)
+
+### Educational Objectives
+
+- **SCADA/ICS Awareness:** Players understand critical infrastructure vulnerabilities
+- **Defensive Mindset:** Players think like defenders, not just attackers
+- **Vulnerability Scanning:** Players learn proper use of Nmap/Nessus
+- **Privilege Escalation:** Players understand sudo vulnerabilities
+
+### Narrative Quality
+
+- **Cross-Cell Coordination:** Players recognize pattern of ENTROPY cooperation
+- **Rising Stakes:** Players feel urgency and higher stakes than M1-3
+- **NPC Relationships:** Robert Chen arc feels authentic and earned
+- **Campaign Impact:** Post-mission debrief sets up "Task Force Null" for M5-10
+
+---
+
+## Next Steps
+
+1. **Proceed to Stage 1:** Develop detailed 3-act narrative structure
+2. **Character Development:** Flesh out Robert Chen, Voltage, and operative personalities
+3. **Combat Design:** Design combat encounters and stealth alternatives
+4. **Timer Mechanics:** Specify exact time budgets and extension conditions
+5. **VM Integration:** Map SecGen scenarios to narrative context
+6. **SCADA Research:** Ensure realistic but accessible portrayal of water treatment SCADA
+
+---
+
+**Mission Status:** Ready for Stage 0 → Stage 1 transition
+**Development Priority:** High (Core season 1 escalation mission)
+**Estimated Development Time:** 120-150 hours (combat system + SCADA complexity)
+
+---
+
+*Mission 4 initialization complete. This mission represents the transition from reconnaissance-focused missions to active crisis response with combat elements. Successfully implementing M4 establishes the combat system and time-pressure mechanics that will be refined in M7-10.*