Problem definition
Valid non-purchase actions are exhausted under combined stopping constraints.
View all bottlenecksGAME DECISION MAP
Merge Mansion
Design direction
Build a bridge to the next action by separating constraints, safeguarding pacing.
View all mechanismsRead the recurring-flow summary
Read the current Task and persistent 7×9 Main Board → tap Producers using Yellow Energy → merge two matching items into the next chain state → manage Board space, Regular Inventory, Producer cooldown, and alternate routes → submit required items to restore the mansion and reveal story → receive Coins, Gems, XP, parts, chests, Pass or event progress → return to the next Task, Producer decision, Daily, Pass, collection, or optional competition cycle.
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.
Constraint-Sliced Next-Action Bridge
State-Verified Relief-to-Completion Bridge
State-Verified Item–Task Fit & Use Bridge
Canonical Routine Schedule & Skip Disclosure
Canonical Pass End-State Disclosure & Value Lock
Goals and residual processing
Initial IFR · goal direction
Realign routing, sequence and availability at the established transition rule.
Final IFR · design goal
Separate Energy, Board, Producer and compound-stop conditions, preserving and revalidating one already executable non-purchase route while it remains valid.
Recurring Structures
Detailed Repeating Structures
What repeats and keeps the system moving?
6 analysis items · Read the method
Core classification and definition · Compounding Growth
Compounding Growth
Read the current Task and persistent 7×9 Main Board → tap Producers using Yellow Energy → merge two matching items into the next chain state → manage Board space, Regular Inventory, Producer cooldown, and alternate routes → submit required items to restore the mansion and reveal story → receive Coins, Gems, XP, parts, chests, Pass or event progress → return to the next Task, Producer decision, Daily, Pass, collection, or optional competition cycle.
Outputs strengthen assets, capabilities, or access and open a stronger next cycle.
View pattern definition →Core Mainline Restoration Loop
The actual loop runs through Energy → Producer → Item Chain → Task → Story Beat → Task/Area.
- Evidence
- Source Described
- Outcome basis
- Design Evidence
Acquisition Daily Support Loop
The actual loop runs through Mainline /Trade → Key → Point → Chest.
- Evidence
- Source Described
- Outcome basis
- Design Evidence
Supply Season Pass Loop
The actual loop runs through Pass Item → Milestone.
- Evidence
- Source Described
- Outcome basis
- Design Evidence
Return Separate Board Event Loop
The actual loop runs through Board/Energy/Producer → Chain → Point/Milestone/Rank → Pouch → Mainline.
- Evidence
- Source Described
- Outcome basis
- Design Evidence
Return Core-Integrated Event Loop
The actual loop runs through Task → Trade → Bubble → Merge → Event Point → Race/League/Milestone.
- Evidence
- Source Described
- Outcome basis
- Design Evidence
Acquisition Collection Loop
The actual loop runs through Event/Offer Collection Unit → Set → Collection.
- Evidence
- Source Described
- Outcome basis
- Design Evidence
Core classification and definition · Access and Qualification Friction
Access and Qualification Friction
The affected flow runs through state → action → return/transaction; its limiting point is the resource progression handoff.
Players cannot reliably identify, meet, or sustain the opportunity, qualification, capability, role, or viable path needed to enter.
View pattern definition →Core Access and Qualification Friction · Resource Progression
The affected flow runs through state → action → return/transaction; its limiting point is the resource progression handoff.
- Evidence
- Classification Confirmed
- Outcome basis
- Design Evidence
Supporting Transition and Handoff Break · Progression Commerce
The affected flow runs through post-use completion/regret/repeat; its limiting point is the progression commerce return handoff.
- Evidence
- Classification Confirmed
- Outcome basis
- Design Evidence
Supporting Temporal and Operational Synchronization Break · Operations
The affected flow runs through cycle burden → return; its limiting point is the operations return handoff.
- Evidence
- Classification Confirmed
- Outcome basis
- Design Evidence
Supporting Temporal and Operational Synchronization Break · Liveops Commerce
The affected flow runs through three cycles; its limiting point is the liveops commerce settlement handoff.
- Evidence
- Classification Confirmed
- Outcome basis
- Design Evidence
Supporting Resource and Value Conversion Failure · Progression Economy
The affected flow runs through item use → next delta; its limiting point is the progression economy 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
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 Performance Vs Load / Freedom Vs Control
Improve Performance Vs Load while preserving Freedom Vs Control.
- Evidence
- Classification Confirmed
- Outcome basis
- Design Evidence
Supporting Revenue Vs Trust / Freedom Vs Control
Improve Revenue Vs Trust 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 / Speed Vs Integrity
Improve Revenue Vs Trust 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
Solution Mechanisms
Solution Mechanisms
Which intervention mechanism changes the condition?
5 analysis items · Read the method
Core classification and definition · Route and Return Handoff
Route and Return Handoff
Apply Route and Return Handoff across Constraint-Sliced Next-Action Bridge while preserving the protected value.
Connect the current state to valid next actions, routes, retries, and returns while preserving choice and existing paths.
View pattern definition →Core Constraint-Sliced Next-Action Bridge
Apply Route and Return Handoff across Constraint-Sliced Next-Action Bridge while preserving the protected value.
- Evidence
- Solution Link Confirmed
- Outcome basis
- Design Evidence
Supporting State-Verified Relief-to-Completion Bridge
Apply Route and Return Handoff across State-Verified Relief-to-Completion Bridge while preserving the protected value.
- Evidence
- Solution Link Confirmed
- Outcome basis
- Design Evidence
Supporting State-Verified Item–Task Fit & Use Bridge
Apply Context Asset and Authority Isolation across State-Verified Item Task Fit & Use Bridge while preserving the protected value.
- Evidence
- Solution Link Confirmed
- Outcome basis
- Design Evidence
Supporting Canonical Routine Schedule & Skip Disclosure
Apply Cadence and Rhythm Coordination across Canonical Routine Schedule & Skip Disclosure while preserving the protected value.
- Evidence
- Solution Link Confirmed
- Outcome basis
- Design Evidence
Supporting Canonical Pass End-State Disclosure & Value Lock
Apply Loss Trust and Entitlement Buffer across Canonical Pass End-State Disclosure & Value Lock while preserving the 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 Constraint-Sliced Next-Action Bridge 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 Constraint-Sliced Next-Action Bridge Composition
Connect 1 source-declared mechanism across Constraint-Sliced Next-Action Bridge as Single-Track Localized Bundle.
- Evidence
- Solution Link Confirmed
- Outcome basis
- Design Evidence
Supporting State-Verified Relief-to-Completion Bridge Composition
Connect 1 source-declared mechanism across State-Verified Relief-to-Completion Bridge as Single-Track Localized Bundle.
- Evidence
- Solution Link Confirmed
- Outcome basis
- Design Evidence
Supporting State-Verified Item–Task Fit & Use Bridge Composition
Connect 1 source-declared mechanism across State-Verified Item Task Fit & Use Bridge as Single-Track Localized Bundle.
- Evidence
- Solution Link Confirmed
- Outcome basis
- Design Evidence
Supporting Canonical Routine Schedule & Skip Disclosure Composition
Connect 1 source-declared mechanism across Canonical Routine Schedule & Skip Disclosure as Single-Track Localized Bundle.
- Evidence
- Solution Link Confirmed
- Outcome basis
- Design Evidence
Supporting Canonical Pass End-State Disclosure & Value Lock Composition
Connect 1 source-declared mechanism across Canonical Pass End-State Disclosure & Value Lock as Single-Track Localized Bundle.
- Evidence
- Solution Link Confirmed
- Outcome basis
- Design Evidence
Supporting Parallel Solution-Mechanism Composition
Connect 5 source-declared mechanisms across Constraint-Sliced Next-Action Bridge as Parallel Local Contracts with Independent Rollback.
- Evidence
- Classification Confirmed
- Outcome basis
- Design Evidence
Supporting Parallel Solution-Mechanism Composition
Connect 2 source-declared mechanisms across Canonical Routine Schedule & Skip Disclosure as Core-First Branch-Sequential Portfolio.
- Evidence
- Classification Confirmed
- Outcome basis
- Design Evidence