Problem definition
A continuity problem between dice resources, recovery and next actions.
View all bottlenecksGAME DECISION MAP
MONOPOLY GO!
Design direction
Explain current states and valid existing actions at the roll, recovery-timer and milestone junction, without adding forced actions, automatic execution or payment.
View all mechanismsRead the recurring-flow summary
Spend Dice to roll around the Monopoly board → resolve tile rewards, Railroad attacks, and event points → use Cash to upgrade Landmarks and complete the board → raise Net Worth and collect or trade Stickers → claim event and Album rewards that refill Dice → roll again.
REASONING IN THIS GAME
Selected designs and judgment conditions
Goals and residual processing
Initial IFR · goal direction
Realign rules, sequence and exposure from recovery through milestone distance to the next action, recovering trust, volition and value.
Recurring Structures
Detailed Repeating Structures
What repeats and keeps the system moving?
3 analysis items · Read the method
Core classification and definition · External Calendar
External Calendar
Spend Dice to roll around the Monopoly board → resolve tile rewards, Railroad attacks, and event points → use Cash to upgrade Landmarks and complete the board → raise Net Worth and collect or trade Stickers → claim event and Album rewards that refill Dice → roll again.
Events, operating schedules, and live operations reactivate participation, exchange, and reward states.
View pattern definition →Core Core Loop
Dice → board movement → cash → landmark construction → Net Worth → next board; stickers/events reactivate loop.
- Evidence
- Source Described
- Outcome basis
- Design Evidence
Return Cash-to-Landmark Loop
Cash acquired from rolls/events is sunk into landmarks/Houses/Hotels and produces Net Worth progression.
- Evidence
- Source Described
- Outcome basis
- Design Evidence
Return Sticker Album Loop
Sticker packs and album completion create long-horizon rewards that refill dice/cash and seasonal value.
- Evidence
- Source Described
- Outcome basis
- Design Evidence
Core classification and definition · Transition and Handoff Break
Transition and Handoff Break
The limiting point sits in the economy return 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 · Economy
The limiting point sits in the economy return handoff.
- Evidence
- Classification Confirmed
- Outcome basis
- Design Evidence
Supporting Temporal and Operational Synchronization Break · Liveops
The affected flow runs through calendar → spend/miss/abandon → gap return; its limiting point is the liveops return handoff.
- Evidence
- Classification Confirmed
- Outcome basis
- Design Evidence
Supporting Allocation and Coordination Failure · Collection
The affected flow runs through pack/duplicate → route → gap → complete/abandon; its limiting point is the collection settlement handoff.
- Evidence
- Classification Confirmed
- Outcome basis
- Design Evidence
Supporting Resource and Value Conversion Failure · Commerce
The affected flow runs through impression → choice → free action → return/refund; its limiting point is the commerce entry handoff.
- Evidence
- Classification Confirmed
- Outcome basis
- Design Evidence
Supporting Action Feedback and Failure Attribution Break · Competition
The affected flow runs through result → points → rank → participation with controls; its limiting point is the competition result handoff.
- Evidence
- Classification Confirmed
- Outcome basis
- Design Evidence
Supporting Action Feedback and Failure Attribution Break · Mastery
The affected flow runs through multiplier → dispersion → feedback → reuse; E confirm; its limiting point is the mastery 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
Across resource/recovery state next meaningful action continuity → legibility, 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
Across resource/recovery state next meaningful action continuity → legibility, improve Performance Vs Load while preserving Freedom Vs Control.
- Evidence
- Classification Confirmed
- Outcome basis
- Design Evidence
Supporting - — LiveOps calendar residual
Across calendar-level time/scarcity separation → schedule/deadline legibility, improve Stability Vs Volatility while preserving Performance Vs Load.
- Evidence
- Classification Confirmed
- Outcome basis
- Design Evidence
Supporting - — Sticker last-mile residual
Across final-gap correction-route controllability → route efficacy legibility, improve Popularity Vs Scarcity while preserving Freedom Vs Control.
- Evidence
- Classification Confirmed
- Outcome basis
- Design Evidence
Supporting - — Offer exposure residual
Across composition → price → odds comparability close-after free continuation legibility, improve Revenue Vs Trust while preserving Complexity Vs Convenience.
- Evidence
- Classification Confirmed
- Outcome basis
- Design Evidence
Supporting - — Competition attribution residual
Across action/result → points → bracket/rank attribution legibility, improve Complexity Vs Convenience while preserving Speed Vs Integrity.
- Evidence
- Classification Confirmed
- Outcome basis
- Design Evidence
Supporting - — Multiplier mastery residual
Across multiplier choice → outcome/mastery feedback legibility, 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?
6 analysis items · Read the method
Core classification and definition · Route and Return Handoff
Route and Return Handoff
Apply Route and Return Handoff across resource/recovery state next meaningful action continuity → legibility 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 Route and Return Handoff · Core
Apply Route and Return Handoff across resource/recovery state next meaningful action continuity → legibility while preserving the protected value.
- Evidence
- Solution Link Confirmed
- Outcome basis
- Design Evidence
Supporting Cadence and Rhythm Coordination · Attachment
Apply Cadence and Rhythm Coordination across calendar-level time/scarcity separation → schedule/deadline legibility while preserving the protected value.
- Evidence
- Solution Link Confirmed
- Outcome basis
- Design Evidence
Supporting Route and Return Handoff · Attachment
Apply Route and Return Handoff across final-gap correction-route controllability → route efficacy legibility 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 composition → price → odds comparability close-after free continuation legibility 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 action/result → points → bracket/rank attribution legibility 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 multiplier choice → outcome/mastery feedback legibility 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 resource/recovery state next meaningful action continuity → legibility 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 across resource/recovery state next meaningful action continuity → legibility 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 calendar-level time/scarcity separation → schedule/deadline legibility as Single-Track Localized Bundle.
- Evidence
- Solution Link Confirmed
- Outcome basis
- Design Evidence
Supporting Route and Return Handoff · Attachment Composition
Connect 1 source-declared mechanism across final-gap correction-route controllability → route efficacy legibility 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 composition → price → odds comparability close-after free continuation legibility 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 action/result → points → bracket/rank attribution legibility 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 multiplier choice → outcome/mastery feedback legibility as Single-Track Localized Bundle.
- Evidence
- Solution Link Confirmed
- Outcome basis
- Design Evidence
Supporting Parallel Solution-Mechanism Composition
Connect 6 source-declared mechanisms across resource/recovery state next meaningful action continuity → legibility as Core-First Branch-Sequential Portfolio.
- Evidence
- Classification Confirmed
- Outcome basis
- Design Evidence
Supporting Parallel Solution-Mechanism Composition
Connect 6 source-declared mechanisms across resource/recovery state next meaningful action continuity → legibility as Parallel Local Contracts with Independent Rollback.
- Evidence
- Classification Confirmed
- Outcome basis
- Design Evidence