Problem definition
As lamp output grows, equipment processing and enhancement-priority decisions obstruct the next growth action.
View all bottlenecksGAME DECISION MAP
Legend of Mushroom
Design direction
Connect equipment, auto-sell state and growth information on the lamp-results surface into one primary action flow, supporting the next growth decision while protecting immediacy and manual choice.
View all mechanismsRead the recurring-flow summary
Open Lamps and receive equipment → keep, equip, or sell results → recover Gold and EXP → raise Lamp Level and layered character growth → clear automatic stages, daily dungeons, Garden, competition, Family, and events → collect rewards and return to the next Lamp and growth decision.
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.
Lamp growth decision hub
Alignment of routine states and deadline signals
Economy route map organized by growth goals
Alignment of an offer’s core value disclosure
Layered collection completion and safety-net card
Family participation readiness and contribution-state card
Conditional composition candidates4 candidate records
These conditional candidates require a separate decision. They do not establish a selected game-local composition or approval for actual application.
Class-linked auto-sell learning bridge
Guaranteed-value exchange lane
Duplicate-to-build completion tracking path
Asynchronous contribution network
Goals and residual processing
Initial IFR · goal direction
Aim for a state in which the connection from output through processing to growth actions is compatible with low-friction growth value.
Final IFR · design goal
Connect candidate equipment, auto-sell state, Gold/EXP, Lamp Level and the next growth action into one primary action flow on the existing lamp-results surface.
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
Open Lamps and receive equipment → keep, equip, or sell results → recover Gold and EXP → raise Lamp Level and layered character growth → clear automatic stages, daily dungeons, Garden, competition, Family, and events → collect rewards and return to the next Lamp and growth decision.
Outputs strengthen assets, capabilities, or access and open a stronger next cycle.
View pattern definition →Core Core Lamp-Gear Loop
The actual loop runs through Core.
- 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 economy 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 Economy
The limiting point sits in the growth economy planning handoff.
- Evidence
- Classification Confirmed
- Outcome basis
- Design Evidence
Supporting Pressure and Concentration Bottleneck · Operations Liveops
The limiting point sits in the operations liveops return handoff.
- Evidence
- Classification Confirmed
- Outcome basis
- Design Evidence
Supporting Decision and Planning Calculability Breakdown · Economy Growth
The limiting point sits in the economy growth planning handoff.
- Evidence
- Classification Confirmed
- Outcome basis
- Design Evidence
Supporting Resource and Value Conversion Failure · Commerce Growth
The limiting point sits in the commerce growth entry handoff.
- Evidence
- Classification Confirmed
- Outcome basis
- Design Evidence
Supporting Rights and Lifecycle Discontinuity ·
The limiting point sits in the result handoff.
- Evidence
- Classification Confirmed
- Outcome basis
- Design Evidence
Supporting Pressure and Concentration Bottleneck · Cooperation Liveops
The limiting point sits in the cooperation liveops 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
Improve Performance Vs Load while preserving Complexity Vs Convenience.
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 Complexity Vs Convenience.
- 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 Freedom Vs Control / Revenue Vs Trust
Across source/sink, improve Freedom Vs Control while preserving Revenue Vs Trust.
- Evidence
- Classification Confirmed
- Outcome basis
- Design Evidence
Supporting Revenue Vs Trust / Complexity Vs Convenience
Across entitlement, improve Revenue Vs Trust while preserving Complexity Vs Convenience.
- Evidence
- Classification Confirmed
- Outcome basis
- Design Evidence
Supporting Complexity Vs Convenience / Revenue Vs Trust
Improve Complexity Vs Convenience while preserving Revenue Vs Trust.
- Evidence
- Classification Confirmed
- Outcome basis
- Design Evidence
Supporting Performance Vs Load / Freedom Vs Control
Improve Performance Vs Load while preserving Freedom Vs Control.
- 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 · Multifunction and Multitrack Coordination
Multifunction and Multitrack Coordination
Apply Multifunction and Multitrack Coordination to the source-declared core track while preserving its protected value.
Coordinate two or more functions or problem tracks in one structure while preserving each track's evidence and protection boundary.
View pattern definition →Core Multifunction and Multitrack Coordination · Core
Apply Multifunction and Multitrack Coordination 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 to the source-declared attachment track while preserving its protected value.
- Evidence
- Solution Link Confirmed
- Outcome basis
- Design Evidence
Supporting Baseline and Resource Stabilization · Attachment
Apply Baseline and Resource Stabilization across source/sink 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 entitlement while preserving the protected value.
- Evidence
- Solution Link Confirmed
- Outcome basis
- Design Evidence
Supporting Loss Trust and Entitlement Buffer · Attachment
Apply Loss Trust and Entitlement Buffer to the source-declared attachment track while preserving its protected value.
- Evidence
- Solution Link Confirmed
- Outcome basis
- Design Evidence
Supporting Multifunction and Multitrack Coordination · Attachment
Apply Multifunction and Multitrack Coordination 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?
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 Multifunction and Multitrack Coordination · 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 as Single-Track Localized Bundle.
- Evidence
- Solution Link Confirmed
- Outcome basis
- Design Evidence
Supporting Baseline and Resource Stabilization · Attachment Composition
Connect 1 source-declared mechanism across source/sink 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 entitlement as Single-Track Localized Bundle.
- Evidence
- Solution Link Confirmed
- Outcome basis
- Design Evidence
Supporting Loss Trust and Entitlement Buffer · Attachment Composition
Connect 1 source-declared mechanism as Single-Track Localized Bundle.
- Evidence
- Solution Link Confirmed
- Outcome basis
- Design Evidence
Supporting Multifunction and Multitrack Coordination · 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 6 source-declared mechanisms across source/sink as Core-First Branch-Sequential Portfolio.
- Evidence
- Classification Confirmed
- Outcome basis
- Design Evidence
Supporting Parallel Solution-Mechanism Composition
Connect 6 source-declared mechanisms across source/sink as Parallel Local Contracts with Independent Rollback.
- Evidence
- Classification Confirmed
- Outcome basis
- Design Evidence