Problem definition
A bottleneck coupling recovery, resource continuity, sales exposure and reentry decisions after repeated failures.
View all bottlenecksGAME DECISION MAP
Gardenscapes
Design direction
Compare owned, free and paid recovery routes, costs, continuing states, reentry and exit within the same failure context, preserving the puzzle, currencies, free routes and player choice.
View all mechanismsRead the recurring-flow summary
Spend a Life to play a limited-move match-3 level → create power-ups and clear objectives → earn Stars and Coins → spend Stars on garden restoration tasks and story progression → use Coins, boosters, Lives, and team or event rewards to recover or continue → enter the next level.
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.
Recovery-decision hub
Predictable LiveOps rhythm map
Three-layer Offer Value Card
Duplicate Assurance & Completion Path
Team Contribution Ledger & Role Bridge
Competition History & Status Ledger
Goals and residual processing
Initial IFR · goal direction
Realign rules, sequence, exposure and economic conditions at the decision junction to recover trust, volition and value.
Final IFR · design goal
Align existing post-failure assets in one comparison context showing source, cost, consequence and next action while separately preserving free, owned, team and paid routes and the economy and puzzle core.
Recurring Structures
Detailed Repeating Structures
What repeats and keeps the system moving?
2 analysis items · Read the method
Core classification and definition · Compounding Growth
Compounding Growth
Spend a Life to play a limited-move match-3 level → create power-ups and clear objectives → earn Stars and Coins → spend Stars on garden restoration tasks and story progression → use Coins, boosters, Lives, and team or event rewards to recover or continue → enter the next level.
Outputs strengthen assets, capabilities, or access and open a stronger next cycle.
View pattern definition →Core Collection Completion Loop
Main Collection → Legendary Collection → Supreme Collection; Supreme repeatable with boosters/coins and no token.
- Evidence
- Source Described
- Outcome basis
- Design Evidence
Return Expedition Loop
Separate map event with Energy, quests, Grand Prize; Energy does not carry to next Expedition.
- Evidence
- Source Described
- Outcome basis
- Design Evidence
Core classification and definition · Transition and Handoff Break
Transition and Handoff Break
The affected flow runs through level_fail → recovery choice → resource/offer → reentry; its limiting point is the transition handoff.
The result of one step does not connect to the next action, return, or reinvestment decision.
View pattern definition →Core Transition and Handoff Break ·
The affected flow runs through level_fail → recovery choice → resource/offer → reentry; its limiting point is the transition handoff.
- Evidence
- Classification Confirmed
- Outcome basis
- Design Evidence
Supporting Pressure and Concentration Bottleneck · Operations
The affected flow runs through concurrent active demand → content switch → complete/abandon; its limiting point is the operations pressure handoff.
- Evidence
- Classification Confirmed
- Outcome basis
- Design Evidence
Supporting Resource and Value Conversion Failure · Economy Commerce
The affected flow runs through offer context → value reading → accept/dismiss; its limiting point is the economy commerce settlement handoff.
- Evidence
- Classification Confirmed
- Outcome basis
- Design Evidence
Supporting Rights and Lifecycle Discontinuity · Asset
The affected flow runs through pack open → duplicate/Gold gap → trade cap → deadline → completion; its limiting point is the asset lifecycle handoff.
- Evidence
- Classification Confirmed
- Outcome basis
- Design Evidence
Supporting Outcome and Contribution Attribution Failure · Social
The affected flow runs through help/life/card contribution → visibility → team status/retention; its limiting point is the social result handoff.
- Evidence
- Classification Confirmed
- Outcome basis
- Design Evidence
Supporting Fairness and Legitimacy Erosion · Competition
The affected flow runs through score rule → rank/reward → persistent status → reentry; its limiting point is the competition result 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
Improve Performance Vs Load 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
Improve Performance Vs Load while preserving Freedom Vs Control.
- Evidence
- Classification Confirmed
- Outcome basis
- Design Evidence
Supporting Performance Vs Load / Stability Vs Volatility
Improve Performance Vs Load while preserving Stability Vs Volatility.
- Evidence
- Classification Confirmed
- Outcome basis
- Design Evidence
Supporting Revenue Vs Trust / Freedom Vs Control
Across entitlement, improve Revenue Vs Trust while preserving Freedom Vs Control.
- Evidence
- Classification Confirmed
- Outcome basis
- Design Evidence
Supporting Popularity Vs Scarcity / Speed Vs Integrity
Improve Popularity Vs Scarcity while preserving Speed Vs Integrity.
- Evidence
- Classification Confirmed
- Outcome basis
- Design Evidence
Supporting Complexity Vs Convenience / Freedom Vs Control
Improve Complexity Vs Convenience while preserving Freedom Vs Control.
- Evidence
- Classification Confirmed
- Outcome basis
- Design Evidence
Supporting Complexity Vs Convenience / Speed Vs Integrity
Improve Complexity Vs Convenience while preserving Speed Vs Integrity.
- 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 · Route and Return Handoff
Route and Return Handoff
Apply Route and Return Handoff to the source-declared core track while preserving its protected value.
Connect the current state to valid next actions, routes, retries, and returns while preserving choice and existing paths.
View pattern definition →Core Route and Return Handoff · Core
Apply Route and Return Handoff to the source-declared core track while preserving its protected value.
- Evidence
- Solution Link Confirmed
- Outcome basis
- Design Evidence
Supporting Cadence and Rhythm Coordination · Attachment
Apply Cadence and Rhythm Coordination across LiveOps while preserving the protected value.
- Evidence
- Solution Link Confirmed
- Outcome basis
- Design Evidence
Supporting Layered and Progressive Disclosure · Attachment
Apply Layered and Progressive Disclosure across 3 Offer Value Card while preserving the protected value.
- Evidence
- Solution Link Confirmed
- Outcome basis
- Design Evidence
Supporting Duplicate Assurance & Completion Path
Apply State and Rule Visibility Encoding across Duplicate Assurance & Completion Path while preserving the protected value.
- Evidence
- Solution Link Confirmed
- Outcome basis
- Design Evidence
Supporting Team Contribution Ledger & Role Bridge
Apply State and Rule Visibility Encoding across Team Contribution Ledger & Role Bridge while preserving the protected value.
- Evidence
- Solution Link Confirmed
- Outcome basis
- Design Evidence
Supporting Competition History & Status Ledger
Apply State and Rule Visibility Encoding across Competition History & Status Ledger 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 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 Route and Return Handoff · Core Composition
Connect 1 source-declared mechanism as Single-Track Localized Bundle.
- Evidence
- Solution Link Confirmed
- Outcome basis
- Design Evidence
Supporting Cadence and Rhythm Coordination · Attachment Composition
Connect 1 source-declared mechanism across LiveOps as Single-Track Localized Bundle.
- Evidence
- Solution Link Confirmed
- Outcome basis
- Design Evidence
Supporting Layered and Progressive Disclosure · Attachment Composition
Connect 1 source-declared mechanism across 3 Offer Value Card as Single-Track Localized Bundle.
- Evidence
- Solution Link Confirmed
- Outcome basis
- Design Evidence
Supporting Duplicate Assurance & Completion Path Composition
Connect 1 source-declared mechanism across Duplicate Assurance & Completion Path as Single-Track Localized Bundle.
- Evidence
- Solution Link Confirmed
- Outcome basis
- Design Evidence
Supporting Team Contribution Ledger & Role Bridge Composition
Connect 1 source-declared mechanism across Team Contribution Ledger & Role Bridge as Single-Track Localized Bundle.
- Evidence
- Solution Link Confirmed
- Outcome basis
- Design Evidence
Supporting Competition History & Status Ledger Composition
Connect 1 source-declared mechanism across Competition History & Status Ledger as Single-Track Localized Bundle.
- Evidence
- Solution Link Confirmed
- Outcome basis
- Design Evidence
Supporting Parallel Solution-Mechanism Composition
Connect 6 source-declared mechanisms across LiveOps as Core-First Branch-Sequential Portfolio.
- Evidence
- Solution Link Confirmed
- Outcome basis
- Design Evidence
Supporting Parallel Solution-Mechanism Composition
Connect 6 source-declared mechanisms across LiveOps as Parallel Local Contracts with Independent Rollback.
- Evidence
- Solution Link Confirmed
- Outcome basis
- Design Evidence