Problem definition
A bottleneck in converting attack rewards into builder growth.
View all bottlenecksGAME DECISION MAP
Clash of Clans
Design direction
Show a primary choice, alternative and reason at the reward state, then recalculate after selection, deferral or return from attack, preserving rewards, costs, time, capacity and rules.
View all mechanismsRead the recurring-flow summary
Build and upgrade the Home Village → train troops and configure an army → raid players or AI for Gold, Elixir, and Dark Elixir → reinvest resources into Town Hall, buildings, research, Heroes, and Equipment → join Clan Wars, CWL, Clan Capital, and Clan Games → return to the Home Village and attack again.
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.
Reward-to-Next-Action Router
Currency Role & Policy Contract Card
Contribution-to-Completion Closure Card
Rule–Result–Replay Closure
Purpose–Window–Choice Closure Card
One-Contract Compare–Commit–Receipt Closure
Goals and residual processing
Initial IFR · goal direction
Realign routing, sequence and exposure from reward inflow through capacity, valid completion or alternatives to the next session.
Final IFR · design goal
Read supported resource, Ore and Builder states in existing reward, completion and next-session contexts, then provide one primary action, one alternative and a reason for choosing, deferring or returning to attack.
Recurring Structures
Detailed Repeating Structures
What repeats and keeps the system moving?
9 analysis items · Read the method
Core classification and definition · Compounding Growth
Compounding Growth
Build and upgrade the Home Village → train troops and configure an army → raid players or AI for Gold, Elixir, and Dark Elixir → reinvest resources into Town Hall, buildings, research, Heroes, and Equipment → join Clan Wars, CWL, Clan Capital, and Clan Games → return to the Home Village and attack again.
Outputs strengthen assets, capabilities, or access and open a stronger next cycle.
View pattern definition →Core Home Village Core Loop
Base design → army composition → attack → defense outcome → reinvestment remains the hub that all spokelike modes feed.
- Evidence
- Source Described
- Outcome basis
- Design Evidence
Economy Growth-to-Economy Loop
growth contents supply Gold/Elixir/Dark Elixir/Ore/Medals, which consumes through upgrades and controls through sinks.
- Evidence
- Source Described
- Outcome basis
- Design Evidence
Competition Competition Validation Loop
turns account power into trophies, stars, destruction, medals, rank and clan status.
- Evidence
- Source Described
- Outcome basis
- Design Evidence
Cooperation Clan
ties donations, Clan Games, Clan Capital, Raid Weekend and chat/recruitment to the same core account progress.
- Evidence
- Source Described
- Outcome basis
- Design Evidence
Return Event Recontextualization Loop
events do not replace the core loop; they reinterpret attacks, clan tasks and season goals with new rewards.
- Evidence
- Source Described
- Outcome basis
- Design Evidence
Return Hero Journey Catch-up Loop
Permanent Hero Hall track converts accumulated Hero Levels into equipment, Ore, skin and catch-up value.
- Evidence
- Source Described
- Outcome basis
- Design Evidence
Supply Gold Pass
Monthly Daily Tasks, Stamp Cards, Choice Nodes and season rewards thicken the reward layer over the core loop.
- Evidence
- Source Described
- Outcome basis
- Design Evidence
Economy Event Shop
Limited event currencies route event actions to Epic Equipment, Ore, Magic Items and cosmetics via Trader/Event tab.
- Evidence
- Source Described
- Outcome basis
- Design Evidence
Cooperation Global Chat Recruitment Loop
Groups, Communities and Town Square reconnect public discovery, recruitment and clan settlement to the core loop.
- Evidence
- Source Described
- Outcome basis
- Design Evidence
Core classification and definition · Resource and Value Conversion Failure
Resource and Value Conversion Failure
The affected flow runs through Ore → Builder; its limiting point is the combat growth reinvestment handoff.
Currencies, assets, products, or inputs do not convert reliably into utility or residual value.
View pattern definition →Core Resource and Value Conversion Failure · Combat Growth
The affected flow runs through Ore → Builder; its limiting point is the combat growth reinvestment handoff.
- Evidence
- Classification Confirmed
- Outcome basis
- Design Evidence
Supporting Outcome and Contribution Attribution Failure · Cooperation
The limiting point sits in the cooperation result handoff.
- Evidence
- Classification Confirmed
- Outcome basis
- Design Evidence
Supporting Fairness and Legitimacy Erosion · Competition
The affected flow runs through Ranked/War → replay → loadout; its limiting point is the competition result handoff.
- Evidence
- Classification Confirmed
- Outcome basis
- Design Evidence
Supporting Decision and Planning Calculability Breakdown · Economy Growth
The affected flow runs through Hero Equipment; its limiting point is the economy growth planning handoff.
- Evidence
- Classification Confirmed
- Outcome basis
- Design Evidence
Supporting Obligation and Volition Erosion · Liveops Event
The limiting point sits in the liveops event return handoff.
- Evidence
- Classification Confirmed
- Outcome basis
- Design Evidence
Supporting Rights and Lifecycle Discontinuity · Commerce Entitlement
The affected flow runs through transaction → entitlement → post-use; its limiting point is the commerce entitlement settlement 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 Independent Social Propagation
Improve Complexity Vs Convenience while preserving Performance Vs Load.
- Evidence
- Classification Confirmed
- Outcome basis
- Design Evidence
Supporting Independent Competition Contract
Improve Freedom Vs Control while preserving None.
- Evidence
- Classification Confirmed
- Outcome basis
- Design Evidence
Supporting Core Economic Transfer Face
Across source/sink, improve Freedom Vs Control while preserving Revenue Vs Trust.
- Evidence
- Classification Confirmed
- Outcome basis
- Design Evidence
Supporting Independent Temporal
Improve Complexity Vs Convenience while preserving Stability Vs Volatility.
- Evidence
- Classification Confirmed
- Outcome basis
- Design Evidence
Supporting Independent Commerce
Across entitlement, improve Complexity Vs Convenience while preserving Revenue Vs Trust.
- 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 Reward-to-Next-Action Router 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 Reward-to-Next-Action Router
Apply Route and Return Handoff across Reward-to-Next-Action Router while preserving the protected value.
- Evidence
- Solution Link Confirmed
- Outcome basis
- Design Evidence
Supporting Contribution-to-Completion Closure Card
Apply State and Rule Visibility Encoding across Contribution-to-Completion Closure Card while preserving the protected value.
- Evidence
- Solution Link Confirmed
- Outcome basis
- Design Evidence
Supporting Rule–Result–Replay Closure
Apply State and Rule Visibility Encoding across Rule Result Replay Closure while preserving the protected value.
- Evidence
- Solution Link Confirmed
- Outcome basis
- Design Evidence
Supporting Currency Role & Policy Contract Card
Apply State and Rule Visibility Encoding across Currency Role & Policy Contract Card while preserving the protected value.
- Evidence
- Solution Link Confirmed
- Outcome basis
- Design Evidence
Supporting Purpose–Window–Choice Closure Card
Apply State and Rule Visibility Encoding across Purpose Window Choice Closure Card while preserving the protected value.
- Evidence
- Solution Link Confirmed
- Outcome basis
- Design Evidence
Supporting One-Contract Compare–Commit–Receipt Closure
Apply Loss Trust and Entitlement Buffer across One-Contract Compare Commit Receipt Closure 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 Reward-to-Next-Action Router 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 Reward-to-Next-Action Router Composition
Connect 1 source-declared mechanism across Reward-to-Next-Action Router as Single-Track Localized Bundle.
- Evidence
- Solution Link Confirmed
- Outcome basis
- Design Evidence
Supporting Contribution-to-Completion Closure Card Composition
Connect 1 source-declared mechanism across Contribution-to-Completion Closure Card as Single-Track Localized Bundle.
- Evidence
- Solution Link Confirmed
- Outcome basis
- Design Evidence
Supporting Rule–Result–Replay Closure Composition
Connect 1 source-declared mechanism across Rule Result Replay Closure as Single-Track Localized Bundle.
- Evidence
- Solution Link Confirmed
- Outcome basis
- Design Evidence
Supporting Currency Role & Policy Contract Card Composition
Connect 1 source-declared mechanism across Currency Role & Policy Contract Card as Single-Track Localized Bundle.
- Evidence
- Solution Link Confirmed
- Outcome basis
- Design Evidence
Supporting Purpose–Window–Choice Closure Card Composition
Connect 1 source-declared mechanism across Purpose Window Choice Closure Card as Single-Track Localized Bundle.
- Evidence
- Solution Link Confirmed
- Outcome basis
- Design Evidence
Supporting One-Contract Compare–Commit–Receipt Closure Composition
Connect 1 source-declared mechanism across One-Contract Compare Commit Receipt Closure as Single-Track Localized Bundle.
- Evidence
- Solution Link Confirmed
- Outcome basis
- Design Evidence
Supporting Parallel Solution-Mechanism Composition
Connect 6 source-declared mechanisms across Reward-to-Next-Action Router 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 Reward-to-Next-Action Router as Parallel Local Contracts with Independent Rollback.
- Evidence
- Solution Link Confirmed
- Outcome basis
- Design Evidence