Problem definition
Difficulty reading handoffs between progression stages.
View all bottlenecksGAME DECISION MAP
Subnautica 2
Design direction
Show current results and next actions at outcome touchpoints first, revealing conditions, reasons and existing entry relationships progressively as needed.
View all mechanismsRead the recurring-flow summary
Explore a new underwater planet → scan fragments and blueprints and gather resources → craft gear and survival equipment → build a seabase and apply Biomod upgrades → expand depth and range with vehicles → optionally share the world and base in up to four-player co-op → use acquired knowledge and assets to enter deeper biomes and continue exploration.
REASONING IN THIS GAME
Selected designs and judgment conditions
Selected principles and the game-local design6 design records
These entries describe the selected design. Design selection is distinct from actual application and effect validation. The classified objects below retain their own roles and connections.
Layered growth handoff
Canonical vehicle-state contract
canonical role–right contract
layered current-state digest
canonical compatibility–recovery contract
chosen-stop-valid return cue
Goals and residual processing
Initial IFR · goal direction
Realign rules, exposure, sequence and feedback at the result-to-next-goal junction.
Final IFR · design goal
Reveal existing result touchpoints progressively as current results and selectable next actions, conditions or reasons, and existing gate relationships.
Recurring Structures
Detailed Repeating Structures
What repeats and keeps the system moving?
1 analysis items · Read the method
Core classification and definition · Compounding Growth
Compounding Growth
Explore a new underwater planet → scan fragments and blueprints and gather resources → craft gear and survival equipment → build a seabase and apply Biomod upgrades → expand depth and range with vehicles → optionally share the world and base in up to four-player co-op → use acquired knowledge and assets to enter deeper biomes and continue exploration.
Outputs strengthen assets, capabilities, or access and open a stronger next cycle.
View pattern definition →Core Core Exploration Loop
Explore → scan/collect → craft/build → expand base/vehicle → descend deeper → unlock story/biomes.
- Evidence
- Source Described
- Outcome basis
- Design Evidence
Core classification and definition · Transition and Handoff Break
Transition and Handoff Break
The affected flow runs through result → goal → action → outcome → return; its limiting point is the exploration crafting growth result handoff.
The result of one step does not connect to the next action, return, or reinvestment decision.
View pattern definition →Core scan
The affected flow runs through result → goal → action → outcome → return; its limiting point is the exploration crafting growth result handoff.
- Evidence
- Classification Confirmed
- Outcome basis
- Design Evidence
Supporting Allocation and Coordination Failure · Cooperation
The affected flow runs through Host flag → right → action/result → rejoin; its limiting point is the cooperation entry handoff.
- Evidence
- Classification Confirmed
- Outcome basis
- Design Evidence
Supporting Transition and Handoff Break · Vehicle Growth Exploration
The affected flow runs through ID → condition → upgrade/depth → continue; its limiting point is the vehicle growth exploration handoff.
- Evidence
- Classification Confirmed
- Outcome basis
- Design Evidence
Supporting Transition and Handoff Break · Roadmap Liveops
The affected flow runs through exposed/unexposed → patch return; its limiting point is the roadmap liveops return handoff.
- Evidence
- Classification Confirmed
- Outcome basis
- Design Evidence
Supporting update–save
The affected flow runs through affected version cohort → outcome; its limiting point is the version save return handoff.
- Evidence
- Classification Confirmed
- Outcome basis
- Design Evidence
Supporting Transition and Handoff Break · Content Exploration
The affected flow runs through intent → activity/hibernate/return; its limiting point is the content exploration return handoff.
- Evidence
- Classification Confirmed
- Outcome basis
- Design Evidence
Contradictions
Contradiction Patterns
What must improve, and what must remain protected?
6 analysis items · Read the method
Core classification and definition · Action and Return Continuity vs System Depth and Throughput
Action and Return Continuity vs System Depth and Throughput
Across feedback, improve Complexity Vs Convenience while preserving Freedom Vs Control.
Continuity to the next action, return, or reinvestment must improve while route diversity, strategic depth, and throughput remain protected.
View pattern definition →Core Core Contradiction
Across feedback, improve Complexity Vs Convenience while preserving Freedom Vs Control.
- Evidence
- Classification Confirmed
- Outcome basis
- Design Evidence
Supporting Freedom Vs Control / Speed Vs Integrity
Across Host/non-host → save/rejoin, improve Freedom Vs Control while preserving Speed Vs Integrity.
- Evidence
- Classification Confirmed
- Outcome basis
- Design Evidence
Supporting Complexity Vs Convenience / Freedom Vs Control
Across canonical vehicle identity material → unlock → depth → dock → completion chain, improve Complexity Vs Convenience while preserving Freedom Vs Control.
- Evidence
- Classification Confirmed
- Outcome basis
- Design Evidence
Supporting Stability Vs Volatility / Speed Vs Integrity
Across Roadmap → build → Hotfix → patch contact → return, improve Stability Vs Volatility while preserving Speed Vs Integrity.
- Evidence
- Classification Confirmed
- Outcome basis
- Design Evidence
Supporting Stability Vs Volatility / Speed Vs Integrity
Across update load → recovery → continuation, improve Stability Vs Volatility while preserving Speed Vs Integrity.
- Evidence
- Classification Confirmed
- Outcome basis
- Design Evidence
Supporting Freedom Vs Control / Stability Vs Volatility
Across completion durable next-goal/purpose save continuity, improve Freedom Vs Control while preserving Stability Vs Volatility.
- Evidence
- Classification Confirmed
- Outcome basis
- Design Evidence
Solution Mechanisms
Solution Mechanisms
Which intervention mechanism changes the condition?
6 analysis items · Read the method
Core classification and definition · Layered and Progressive Disclosure
Layered and Progressive Disclosure
Apply Layered and Progressive Disclosure across feedback while preserving the protected value.
Separate complex meaning, rules, and strategy into layers and reveal only the depth needed at each moment.
View pattern definition →Core Layered and Progressive Disclosure · Core
Apply Layered and Progressive Disclosure across feedback while preserving the protected value.
- Evidence
- Solution Link Confirmed
- Outcome basis
- Design Evidence
Supporting Context Asset and Authority Isolation · Attachment
Apply Context Asset and Authority Isolation across canonical vehicle while preserving the protected value.
- Evidence
- Solution Link Confirmed
- Outcome basis
- Design Evidence
Supporting canonical role–right contract
Apply Context Asset and Authority Isolation across canonical role right contract while preserving the protected value.
- Evidence
- Solution Link Confirmed
- Outcome basis
- Design Evidence
Supporting layered current-state digest
Apply Layered and Progressive Disclosure across layered current-state digest while preserving the protected value.
- Evidence
- Solution Link Confirmed
- Outcome basis
- Design Evidence
Supporting canonical compatibility–recovery contract
Apply Loss Trust and Entitlement Buffer across canonical compatibility recovery contract while preserving the protected value.
- Evidence
- Solution Link Confirmed
- Outcome basis
- Design Evidence
Supporting chosen-stop-valid return cue
Apply Route and Return Handoff across chosen-stop-valid return cue while preserving the protected value.
- Evidence
- Solution Link Confirmed
- Outcome basis
- Design Evidence
Solution Compositions
Solution Compositions
How should interventions be combined and sequenced?
8 analysis items · Read the method
Core classification and definition · Single-Track Localized Bundle
Single-Track Localized Bundle
Connect 1 source-declared mechanism across feedback as Single-Track Localized Bundle.
Combine a core intervention with stabilizing or accelerating support within one problem track and keep its impact localized.
View pattern definition →Core Layered and Progressive Disclosure · Core Composition
Connect 1 source-declared mechanism across feedback as Single-Track Localized Bundle.
- Evidence
- Solution Link Confirmed
- Outcome basis
- Design Evidence
Supporting Context Asset and Authority Isolation · Attachment Composition
Connect 1 source-declared mechanism across canonical vehicle as Single-Track Localized Bundle.
- Evidence
- Solution Link Confirmed
- Outcome basis
- Design Evidence
Supporting canonical role–right contract Composition
Connect 1 source-declared mechanism across canonical role right contract as Single-Track Localized Bundle.
- Evidence
- Solution Link Confirmed
- Outcome basis
- Design Evidence
Supporting layered current-state digest Composition
Connect 1 source-declared mechanism across layered current-state digest as Single-Track Localized Bundle.
- Evidence
- Solution Link Confirmed
- Outcome basis
- Design Evidence
Supporting canonical compatibility–recovery contract Composition
Connect 1 source-declared mechanism across canonical compatibility recovery contract as Single-Track Localized Bundle.
- Evidence
- Solution Link Confirmed
- Outcome basis
- Design Evidence
Supporting chosen-stop-valid return cue Composition
Connect 1 source-declared mechanism across chosen-stop-valid return cue as Single-Track Localized Bundle.
- Evidence
- Solution Link Confirmed
- Outcome basis
- Design Evidence
Supporting Parallel Solution-Mechanism Composition
Connect 6 source-declared mechanisms across feedback as Core-First Branch-Sequential Portfolio.
- Evidence
- Classification Confirmed
- Outcome basis
- Design Evidence
Supporting Parallel Solution-Mechanism Composition
Connect 6 source-declared mechanisms across feedback as Parallel Local Contracts with Independent Rollback.
- Evidence
- Classification Confirmed
- Outcome basis
- Design Evidence