GAME DECISION MAP
Discover or join an experience → play, create, or socialize → earn or spend experience-specific progress and items → switch or return to experiences.
Recurring Structures
What repeats and keeps the system moving?
Discover or join an experience → play, create, or socialize → earn or spend experience-specific progress and items → switch or return to experiences.
Outputs strengthen assets, capabilities, or access and open a stronger next cycle.
View pattern definition →Home/RFY/chart/curation → Experience play → co-play/revisit/spend → signal accumulation → additional discovery.
Bottlenecks
Where do decisions and flow break?
The limiting point sits in the platform portfolio social reinvestment handoff.
Acquisition, ownership, guarantees, resets, expiry, refunds, editing, and reuse do not form one continuous lifecycle.
View pattern definition →The limiting point sits in the platform portfolio social reinvestment handoff.
The affected flow runs through cohort impression → launch → state restore/first action → next action → return lineage residual; its limiting point is the discovery portfolio entry handoff.
The affected flow runs through ordered path creator cohort; its limiting point is the discovery entry handoff.
The affected flow runs through gate completion communication/co-play/return residual safety outcome; its limiting point is the safety social entry handoff.
The affected flow runs through canonical transaction → Robux conversion → local source/sink → product use → repeat/refund lineage Experience → region; its limiting point is the economy commerce platform entry handoff.
The affected flow runs through device tier asset fidelity join/load/frame/input/crash → session/result → return residual; its limiting point is the runtime device handoff.
Contradictions
What must improve, and what must remain protected?
Across cross-Experience accumulated value/status/org/utility recognition and use continuity, improve Stability Vs Volatility while preserving Complexity Vs Convenience.
Time, currency, purchases, rewards, and held assets must close into trustworthy value while route diversity, scarcity, and invested assets remain protected.
View pattern definition →Across cross-Experience accumulated value/status/org/utility recognition and use continuity, improve Stability Vs Volatility while preserving Complexity Vs Convenience.
Across restored state, first value and next-action legibility, improve Complexity Vs Convenience while preserving Freedom Vs Control.
Across allocation → performance/payout → reinvestment traceability, improve Freedom Vs Control while preserving Speed Vs Integrity.
Across protected access/co-play route legibility, improve Freedom Vs Control while preserving Speed Vs Integrity.
Across common-to-local value-contract legibility, improve Freedom Vs Control while preserving Revenue Vs Trust.
Across device/fidelity state predictability and quality floor, improve Performance Vs Load while preserving Complexity Vs Convenience.
Solution Mechanisms
Which intervention mechanism changes the condition?
Apply Loss Trust and Entitlement Buffer across Continuity Recovery Overlay while preserving the protected value.
Buffer loss, regret, probability, completion, and purchase-right risk while preserving existing value and voluntary choice.
View pattern definition →Apply Loss Trust and Entitlement Buffer across Continuity Recovery Overlay while preserving the protected value.
Apply Route and Return Handoff across Destination Resume Compass while preserving the protected value.
Apply Context Asset and Authority Isolation across Common-to-Local Value Contract Compass while preserving the protected value.
Apply Context Asset and Authority Isolation across Protected Co-Play Access Compass while preserving the protected value.
Apply Context Asset and Authority Isolation across Discovery-to-Supply Counterfactual Compass while preserving the protected value.
Apply Context Asset and Authority Isolation across Device-Fidelity Preflight Compass while preserving the protected value.
Solution Compositions
How should interventions be combined and sequenced?
Connect 1 source-declared mechanism across Continuity Recovery Overlay 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 →Connect 1 source-declared mechanism across Continuity Recovery Overlay as Single-Track Localized Bundle.
Connect 1 source-declared mechanism across Destination Resume Compass as Single-Track Localized Bundle.
Connect 1 source-declared mechanism across Common-to-Local Value Contract Compass as Single-Track Localized Bundle.
Connect 1 source-declared mechanism across Protected Co-Play Access Compass as Single-Track Localized Bundle.
Connect 1 source-declared mechanism across Discovery-to-Supply Counterfactual Compass as Single-Track Localized Bundle.
Connect 1 source-declared mechanism across Device-Fidelity Preflight Compass as Single-Track Localized Bundle.
Connect 6 source-declared mechanisms across Continuity Recovery Overlay as Core-First Branch-Sequential Portfolio.
Connect 6 source-declared mechanisms across Continuity Recovery Overlay as Parallel Local Contracts with Independent Rollback.