Problem definition
Discontinuity in the wording linking growth purposes, costs and next actions.
View all bottlenecksGAME DECISION MAP
Love and Deepspace
Design direction
Connect goals, states, costs and recovery, and multiple next actions on growth and challenge screens, preserving free access, relationship and combat depth, and choice.
View all mechanismsRead the recurring-flow summary
Follow Main Story and companion combat → farm Bounty Hunt, Core Hunt, Trials, and daily tasks → strengthen Memories and Protocores and prepare Stellactrum formations → unlock Affinity, Date, Voice, Home, and Photo relationship content → acquire limited Memories through Wish, shops, exchanges, and events → return to story, combat, and relationship progression.
REASONING IN THIS GAME
Selected designs and judgment conditions
Selected principles and the game-local design5 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.
Growth-decision capsule
Wish decision and residual-value contract
Event-end to regular-play return contract
Challenge-readiness and safety-preview contract
Companion-combat result-to-corrective-feedback contract
Goals and residual processing
Initial IFR · goal direction
Realign rules, exposure and sequence connecting growth goals, costs, recovery and next actions, recovering volition and value while preserving trust.
Final IFR · design goal
Connect goals, state, costs or recovery and multiple next actions through information layers and consistent state grammar within existing growth and challenge surfaces.
Recurring Structures
Detailed Repeating Structures
What repeats and keeps the system moving?
6 analysis items · Read the method
Core classification and definition · External Calendar
External Calendar
Follow Main Story and companion combat → farm Bounty Hunt, Core Hunt, Trials, and daily tasks → strengthen Memories and Protocores and prepare Stellactrum formations → unlock Affinity, Date, Voice, Home, and Photo relationship content → acquire limited Memories through Wish, shops, exchanges, and events → return to story, combat, and relationship progression.
Events, operating schedules, and live operations reactivate participation, exchange, and reward states.
View pattern definition →Core Home
Home, study/workout/work, mini-games and photo features maintain non-combat retention between major banners.
- Evidence
- Source Described
- Outcome basis
- Design Evidence
Core Low-toxicity Challenge Loop
Hunter Contest and Trials keep mastery pressure asynchronous and subordinate to relationship immersion.
- Evidence
- Source Described
- Outcome basis
- Design Evidence
Return Core Relationship Growth Loop
Story/battle/farming feed Memory growth; Memory and Affinity unlock dates, voice, Myths, home/photo interaction; events and Wish Pools restart the loop.
- Evidence
- Source Described
- Outcome basis
- Design Evidence
Supply Combat Growth Farm Loop
Bounty Hunt and Core Hunt supply materials and Protocores; Deepspace Trials and Hunter Contest validate the resulting builds.
- Evidence
- Source Described
- Outcome basis
- Design Evidence
Return Limited Event Monetization Loop
Version/event trigger creates desire for limited Memory/outfit/home/photo value; Wish and shop conversion then feed relationship assets.
- Evidence
- Source Described
- Outcome basis
- Design Evidence
Cooperation Partner Cooperation Loop
Player-partner pair combat and daily shared activities substitute for guild-style social cooperation.
- Evidence
- Source Described
- Outcome basis
- Design Evidence
Core classification and definition · Decision and Planning Calculability Breakdown
Decision and Planning Calculability Breakdown
The limiting point sits in the growth collection planning handoff.
Multiple goals, resources, states, rules, and paths cannot be compared on one decision surface, forcing repeated reprioritization.
View pattern definition →Core Decision and Planning Calculability Breakdown · Growth Collection
The limiting point sits in the growth collection planning handoff.
- Evidence
- Classification Confirmed
- Outcome basis
- Design Evidence
Supporting Rights and Lifecycle Discontinuity · Commerce
The limiting point sits in the commerce result handoff.
- Evidence
- Classification Confirmed
- Outcome basis
- Design Evidence
Supporting Temporal and Operational Synchronization Break · Liveops Event
The limiting point sits in the liveops event return handoff.
- Evidence
- Classification Confirmed
- Outcome basis
- Design Evidence
Supporting Pressure and Concentration Bottleneck · Roster Growth
The affected flow runs through requirement → allocation → retry; its limiting point is the roster growth planning handoff.
- Evidence
- Classification Confirmed
- Outcome basis
- Design Evidence
Supporting Action Feedback and Failure Attribution Break · Combat Mastery
The limiting point sits in the combat mastery result handoff.
- Evidence
- Classification Confirmed
- Outcome basis
- Design Evidence
Contradictions
Contradiction Patterns
What must improve, and what must remain protected?
5 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 Home → Event, 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 Home → Event, improve Complexity Vs Convenience while preserving Freedom Vs Control.
- Evidence
- Classification Confirmed
- Outcome basis
- Design Evidence
Supporting Limited Wish Decision Contract
Across Limited/Precise Wish, improve Revenue Vs Trust while preserving Freedom Vs Control.
- Evidence
- Classification Confirmed
- Outcome basis
- Design Evidence
Supporting Event Concurrency and Post-Event Residence
Across event core, improve Stability Vs Volatility while preserving Performance Vs Load.
- Evidence
- Classification Confirmed
- Outcome basis
- Design Evidence
Supporting Late Multi-Formation
Across setup → roster/resource → retry, improve Complexity Vs Convenience while preserving Freedom Vs Control.
- Evidence
- Classification Confirmed
- Outcome basis
- Design Evidence
Supporting Combat Result–Rule–Correction–Retry Continuity
Improve Complexity Vs Convenience while preserving None.
- Evidence
- Classification Confirmed
- Outcome basis
- Design Evidence
Solution Mechanisms
Solution Mechanisms
Which intervention mechanism changes the condition?
5 analysis items · Read the method
Core classification and definition · Layered and Progressive Disclosure
Layered and Progressive Disclosure
Apply Layered and Progressive Disclosure across Home → Event 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 Home → Event while preserving the protected value.
- Evidence
- Solution Link Confirmed
- Outcome basis
- Design Evidence
Supporting State and Rule Visibility Encoding · Attachment
Apply State and Rule Visibility Encoding across Wish while preserving the protected value.
- Evidence
- Solution Link Confirmed
- Outcome basis
- Design Evidence
Supporting State and Rule Visibility Encoding · Attachment
Apply State and Rule Visibility Encoding across Event while preserving the protected value.
- Evidence
- Solution Link Confirmed
- Outcome basis
- Design Evidence
Supporting State and Rule Visibility Encoding · Attachment
Apply State and Rule Visibility Encoding across setup → roster/resource → retry while preserving the protected value.
- Evidence
- Solution Link Confirmed
- Outcome basis
- Design Evidence
Supporting State and Rule Visibility Encoding · Attachment
Apply State and Rule Visibility Encoding to the source-declared attachment track while preserving its protected value.
- Evidence
- Solution Link Confirmed
- Outcome basis
- Design Evidence
Solution Compositions
Solution Compositions
How should interventions be combined and sequenced?
7 analysis items · Read the method
Core classification and definition · Single-Track Localized Bundle
Single-Track Localized Bundle
Connect 1 source-declared mechanism across Home → Event 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 Home → Event as Single-Track Localized Bundle.
- Evidence
- Solution Link Confirmed
- Outcome basis
- Design Evidence
Supporting State and Rule Visibility Encoding · Attachment Composition
Connect 1 source-declared mechanism across Wish as Single-Track Localized Bundle.
- Evidence
- Solution Link Confirmed
- Outcome basis
- Design Evidence
Supporting State and Rule Visibility Encoding · Attachment Composition
Connect 1 source-declared mechanism across Event as Single-Track Localized Bundle.
- Evidence
- Solution Link Confirmed
- Outcome basis
- Design Evidence
Supporting State and Rule Visibility Encoding · Attachment Composition
Connect 1 source-declared mechanism across setup → roster/resource → retry as Single-Track Localized Bundle.
- Evidence
- Solution Link Confirmed
- Outcome basis
- Design Evidence
Supporting State and Rule Visibility Encoding · Attachment Composition
Connect 1 source-declared mechanism as Single-Track Localized Bundle.
- Evidence
- Solution Link Confirmed
- Outcome basis
- Design Evidence
Supporting Parallel Solution-Mechanism Composition
Connect 5 source-declared mechanisms across Home → Event as Core-First Branch-Sequential Portfolio.
- Evidence
- Solution Link Confirmed
- Outcome basis
- Design Evidence
Supporting Parallel Solution-Mechanism Composition
Connect 5 source-declared mechanisms across Home → Event as Parallel Local Contracts with Independent Rollback.
- Evidence
- Solution Link Confirmed
- Outcome basis
- Design Evidence