Problem definition
Tasks, rewards, claims, exchanges and returns are fragmented across passes and events.
View all bottlenecksGAME DECISION MAP
Call of Duty: Mobile
Design direction
Layer current state and next actions, effort, claims and returns, and rules, completion and prestige, keeping each mode’s evidence separate.
View all mechanismsRead the recurring-flow summary
Choose a mode and loadout → fight and complete objectives → earn XP and rewards → unlock or equip gear → re-enter matches.
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.
Layered Contract Status Spine
Persistence-Locked Milestone Spine
Evidence-Locked Collection Contract Spine
Integrity-Locked Ranked Decision Spine
Mode-Locked Reward-to-Asset Spine
Layered Voluntary Contribution-to-Recognition Spine
Goals and residual processing
Initial IFR · goal direction
Realign rules, sequence, exposure and governance conditions at the decision junction to recover trust, volition and value.
Final IFR · design goal
Connect state, the next action, claim or exchange and return through information layers and consistent state grammar within existing surfaces, supporting explainable conditions, chosen participation and effort–value–return continuity.
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
Choose a mode and loadout → fight and complete objectives → earn XP and rewards → unlock or equip gear → re-enter matches.
Outputs strengthen assets, capabilities, or access and open a stronger next cycle.
View pattern definition →Core Shared Combat Hub Loop
Core structure: common input/weapon/operator pipeline supports Multiplayer, Battle Royale and DMZ: Recon as parallel pillars.
- Evidence
- Source Described
- Outcome basis
- Design Evidence
Competition Multiplayer Pillar Loop
MP match → Battle Pass/Challenge progress → ranked/league/WCPS status → seasonal rewards and store/draw exposure.
- Evidence
- Source Described
- Outcome basis
- Design Evidence
Competition Battle Royale Pillar Loop
BR session → ranked/event progress → BR class/LTM engagement → season rewards and themed event/store hooks.
- Evidence
- Source Described
- Outcome basis
- Design Evidence
Economy DMZ Risk Pillar Loop
Pre-battle loadout → contracts/loot/bosses → exfil/loss → Black Market/talents/reactive camos → account-season value.
- Evidence
- Source Described
- Outcome basis
- Design Evidence
Acquisition Season Package Loop
Season launch bundles mode update, event list, Battle Pass, Challenge Pass and Store/Draw update into one operating package.
- Evidence
- Source Described
- Outcome basis
- Design Evidence
Acquisition Event-to-Store
Collaboration/event novelty routes attention into Draw, Armory, Web Store and Battle Pass monetization surfaces.
- Evidence
- Source Described
- Outcome basis
- Design Evidence
Core classification and definition · Rule and State Fragmentation
Rule and State Fragmentation
The affected flow runs through chain by persona/window; its limiting point is the liveops event entry handoff.
Rules and states vary across channels, platforms, resets, or probabilities and fail to form a consistent action grammar.
View pattern definition →Core Rule and State Fragmentation · Liveops Event
The affected flow runs through chain by persona/window; its limiting point is the liveops event entry handoff.
- Evidence
- Classification Confirmed
- Outcome basis
- Design Evidence
Supporting Transition and Handoff Break · Growth
The affected flow runs through Credits/XP/unlock/goal; its limiting point is the growth return handoff.
- Evidence
- Classification Confirmed
- Outcome basis
- Design Evidence
Supporting Rights and Lifecycle Discontinuity · Armory Collection
The affected flow runs through rule/draw/duplicate/completion; its limiting point is the armory collection handoff.
- Evidence
- Classification Confirmed
- Outcome basis
- Design Evidence
Supporting Fairness and Legitimacy Erosion · Ranked Competition
The affected flow runs through result/review/edit/retry; its limiting point is the ranked competition result handoff.
- Evidence
- Classification Confirmed
- Outcome basis
- Design Evidence
Supporting Resource and Value Conversion Failure · Dmz Growth
The affected flow runs through reward/market/Camo/return; its limiting point is the dmz growth reinvestment handoff.
- Evidence
- Classification Confirmed
- Outcome basis
- Design Evidence
Supporting Outcome and Contribution Attribution Failure · Social
The affected flow runs through graph/social return; its limiting point is the social 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 Pass → Challenge → Event effort → reward → claim/exchange → return, improve Complexity Vs Convenience while preserving Stability Vs Volatility.
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 Pass → Challenge → Event effort → reward → claim/exchange → return, improve Complexity Vs Convenience while preserving Stability Vs Volatility.
- Evidence
- Classification Confirmed
- Outcome basis
- Design Evidence
Supporting Stability Vs Volatility / Complexity Vs Convenience
Across evergreen claim → Credits/Weapon XP → unlock → next-goal → return, improve Stability Vs Volatility while preserving Complexity Vs Convenience.
- Evidence
- Classification Confirmed
- Outcome basis
- Design Evidence
Supporting Complexity Vs Convenience / Revenue Vs Trust
Across rule/probability → draw → duplicate → completion → equip/display governance, improve Complexity Vs Convenience while preserving Revenue Vs Trust.
- Evidence
- Classification Confirmed
- Outcome basis
- Design Evidence
Supporting Speed Vs Integrity / Complexity Vs Convenience
Across result comprehension → review/edit → retry/exit, improve Speed Vs Integrity while preserving Complexity Vs Convenience.
- Evidence
- Classification Confirmed
- Outcome basis
- Design Evidence
Supporting Popularity Vs Scarcity / Freedom Vs Control
Across DMZ reward → voucher/market → asset completion → return, improve Popularity Vs Scarcity while preserving Freedom Vs Control.
- Evidence
- Classification Confirmed
- Outcome basis
- Design Evidence
Supporting Complexity Vs Convenience / Freedom Vs Control
Across contribution → recognition/practice → persistent relation capital → return, 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 · Layered and Progressive Disclosure
Layered and Progressive Disclosure
Apply Layered and Progressive Disclosure across Layered Contract Status Spine while preserving the protected value.
Separate complex meaning, rules, and strategy into layers and reveal only the depth needed at each moment.
View pattern definition →Core Layered Contract Status Spine
Apply Layered and Progressive Disclosure across Layered Contract Status Spine while preserving the protected value.
- Evidence
- Solution Link Confirmed
- Outcome basis
- Design Evidence
Supporting Persistence- Milestone Spine
Apply Route and Return Handoff across Persistence- Milestone Spine while preserving the protected value.
- Evidence
- Solution Link Confirmed
- Outcome basis
- Design Evidence
Supporting Source- Collection Contract Spine
Apply State and Rule Visibility Encoding across Source- Collection Contract Spine while preserving the protected value.
- Evidence
- Solution Link Confirmed
- Outcome basis
- Design Evidence
Supporting Integrity- Ranked Decision Spine
Apply State and Rule Visibility Encoding across Integrity- Ranked Decision Spine while preserving the protected value.
- Evidence
- Solution Link Confirmed
- Outcome basis
- Design Evidence
Supporting Mode- Reward-to-Asset Spine
Apply State and Rule Visibility Encoding across Mode- Reward-to-Asset Spine while preserving the protected value.
- Evidence
- Solution Link Confirmed
- Outcome basis
- Design Evidence
Supporting Layered Voluntary Contribution-to-Recognition Spine
Apply Layered and Progressive Disclosure across Layered Voluntary Contribution-to-Recognition Spine 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 Layered Contract Status Spine 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 Layered Contract Status Spine Composition
Connect 1 source-declared mechanism across Layered Contract Status Spine as Single-Track Localized Bundle.
- Evidence
- Solution Link Confirmed
- Outcome basis
- Design Evidence
Supporting Persistence- Milestone Spine Composition
Connect 1 source-declared mechanism across Persistence- Milestone Spine as Single-Track Localized Bundle.
- Evidence
- Solution Link Confirmed
- Outcome basis
- Design Evidence
Supporting Source- Collection Contract Spine Composition
Connect 1 source-declared mechanism across Source- Collection Contract Spine as Single-Track Localized Bundle.
- Evidence
- Solution Link Confirmed
- Outcome basis
- Design Evidence
Supporting Integrity- Ranked Decision Spine Composition
Connect 1 source-declared mechanism across Integrity- Ranked Decision Spine as Single-Track Localized Bundle.
- Evidence
- Solution Link Confirmed
- Outcome basis
- Design Evidence
Supporting Mode- Reward-to-Asset Spine Composition
Connect 1 source-declared mechanism across Mode- Reward-to-Asset Spine as Single-Track Localized Bundle.
- Evidence
- Solution Link Confirmed
- Outcome basis
- Design Evidence
Supporting Layered Voluntary Contribution-to-Recognition Spine Composition
Connect 1 source-declared mechanism across Layered Voluntary Contribution-to-Recognition Spine as Single-Track Localized Bundle.
- Evidence
- Solution Link Confirmed
- Outcome basis
- Design Evidence
Supporting Parallel Solution-Mechanism Composition
Connect 6 source-declared mechanisms across Layered Contract Status Spine 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 Layered Contract Status Spine as Parallel Local Contracts with Independent Rollback.
- Evidence
- Solution Link Confirmed
- Outcome basis
- Design Evidence