Facility Escape (Chapter 2) — Studio Status

Current State: Designed

Facility Escape Chapter 2 is designed but not implemented. Real, locked infrastructure from July. New design from tonight’s session. Real open items remain.

Locked Infrastructure (July)

Real, working, locked infrastructure from July:

  • turnEngine — the turn-based game loop
  • guardAI — AI behavior for facility guards
  • physicsEngine — spatial simulation
  • roomGenerator — procedural room generation
  • levelSolver — a genuinely sophisticated level solver with real Dijkstra search, difficulty scoring, and degenerate-room rejection

Five Locked Design Pillars

Five design pillars are locked, including:

  • “Telecast, Not Ambush” — the core stealth philosophy
  • “One Body, Not a Fleet” — the player is a single agent, not a squad

New Design (Tonight’s Session)

Three new design elements:

Loud Meter

A floor-wide alarm state modeled on FF7’s Shinra Tower Invasion. The Loud meter tracks how much noise the player has made across the entire floor, not just in the current room. This creates a real tension between speed (more noise) and stealth (less progress).

Rush System

A fortify-the-same-room mechanic. When a Rush is triggered, the player fortifies their current room and defends it. The goal never changes — the player still needs to reach the exit, but the Rush creates a real, localized combat encounter that must be resolved before continuing.

Trinity Siege RPS Skeleton Reuse

Trinity Siege’s RPS (rock-paper-scissors) skeleton is reused for Rush-enemy resolution only — not as a broad game system. This preserves the “One Body, Not a Fleet” pillar: the RPS determines how the player’s single-agent loadout interacts with the Rush enemies, not a fleet-vs-fleet combat simulation.

Real, Explicitly Open

Three items are real, explicitly open — none decided:

  1. Exit-reachability during Rush — can the player reach the exit while a Rush is active, or must the Rush be resolved first?
  2. Real intensity curve — how does the Loud meter and Rush frequency scale across the chapter?
  3. Discrete-juncture placement — at what specific junctures do Rush events occur?

Canon Proposal

A real thread was proposed to the wider canon via Signal. This is a design proposal, not a locked decision — the canon may or may not incorporate it.


← Back to Studio Status · Back to Projects*