Problem definition
Difficulty reading input priorities and result attribution across growth layers.
View all bottlenecksGAME DECISION MAP
State of Survival
Design direction
Align decisions, context and detailed traces around expected and actual changes, reasons and next actions, preserving growth depth, existing investment and choice diversity.
View all mechanismsRead the recurring-flow summary
Build and upgrade the Settlement → collect resources and manage construction, research, and training queues → grow Heroes, troops, Chief gear, and Battle Power → clear Explorer Trail, world zombies, gathering, and rallies → join Alliance help, research, events, and State warfare → reinvest rewards into the next upgrade and war preparation.
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.
Three-Layer Growth Result Contract
Hero Next-State Grammar
Eligibility-to-Next-State Grammar
Offer-to-Use Value Lineage Contract
Alliance Contribution Contract Hub
Role & Result Legitimacy Receipt
Goals and residual processing
Final IFR · design goal
Present established goals, cost sources, expected direction, actual results or reasons and next actions in optional three-layer information on existing growth surfaces.
Recurring Structures
Detailed Repeating Structures
What repeats and keeps the system moving?
1 analysis items · Read the method
Core classification and definition · External Calendar
External Calendar
Build and upgrade the Settlement → collect resources and manage construction, research, and training queues → grow Heroes, troops, Chief gear, and Battle Power → clear Explorer Trail, world zombies, gathering, and rallies → join Alliance help, research, events, and State warfare → reinvest rewards into the next upgrade and war preparation.
Events, operating schedules, and live operations reactivate participation, exchange, and reward states.
View pattern definition →Return Core Daily → War Conversion Loop
The actual loop runs through Help → Explorer Trail → BP → Chief → SvS/Capital Clash.
- Evidence
- Source Described
- Outcome basis
- Design Evidence
Core classification and definition · Decision and Planning Calculability Breakdown
Decision and Planning Calculability Breakdown
The affected flow runs through DR; its limiting point is 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 affected flow runs through DR; its limiting point is the growth economy planning handoff.
- Evidence
- Classification Confirmed
- Outcome basis
- Design Evidence
Supporting Outcome and Contribution Attribution Failure · Alliance Cooperation
The limiting point sits in the alliance cooperation result handoff.
- Evidence
- Classification Confirmed
- Outcome basis
- Design Evidence
Supporting Temporal and Operational Synchronization Break · Liveops Event
The limiting point sits in the liveops event return handoff.
- Evidence
- Classification Confirmed
- Outcome basis
- Design Evidence
Supporting Rights and Lifecycle Discontinuity · Hero
The limiting point sits in the hero handoff.
- Evidence
- Classification Confirmed
- Outcome basis
- Design Evidence
Supporting Fairness and Legitimacy Erosion · Competition Alliance
The limiting point sits in the competition alliance result handoff.
- Evidence
- Classification Confirmed
- Outcome basis
- Design Evidence
Supporting Resource and Value Conversion Failure · Commerce Economy
The affected flow runs through offer lineage reconciliation; its limiting point is the commerce economy 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 · Outcome and Failure Attribution vs System Depth and Rule Integrity
Outcome and Failure Attribution vs System Depth and Rule Integrity
Improve Complexity Vs Convenience while preserving Freedom Vs Control.
Causes and retry conditions for outcomes, failures, and fairness must become attributable while strategic, combat, and competitive depth and rule integrity remain protected.
View pattern definition →Core Core Contradiction
Improve Complexity Vs Convenience while preserving Freedom Vs Control.
- Evidence
- Classification Confirmed
- Outcome basis
- Design Evidence
Supporting Complexity Vs Convenience / Freedom Vs Control
Across Alliance, improve Complexity Vs Convenience while preserving Freedom Vs Control.
- Evidence
- Classification Confirmed
- Outcome basis
- Design Evidence
Supporting Performance Vs Load / Stability Vs Volatility
Across entry/task/claim/skip → return, improve Performance Vs Load while preserving Stability Vs Volatility.
- Evidence
- Classification Confirmed
- Outcome basis
- Design Evidence
Supporting Popularity Vs Scarcity / Complexity Vs Convenience
Across Hero → rank/build/use/display → completion/revisit lineage, improve Popularity Vs Scarcity while preserving Complexity Vs Convenience.
- Evidence
- Classification Confirmed
- Outcome basis
- Design Evidence
Supporting Freedom Vs Control / Stability Vs Volatility
Improve Freedom Vs Control while preserving Stability Vs Volatility.
- Evidence
- Classification Confirmed
- Outcome basis
- Design Evidence
Supporting Revenue Vs Trust / Complexity Vs Convenience
Across SKU view → compare/action → use → next-action, improve Revenue Vs Trust while preserving Complexity Vs Convenience.
- 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 Three-Layer Growth Result Contract 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 Three-Layer Growth Result Contract
Apply Layered and Progressive Disclosure across Three-Layer Growth Result Contract while preserving the protected value.
- Evidence
- Solution Link Confirmed
- Outcome basis
- Design Evidence
Supporting DO- Alliance Contribution Contract Hub
Apply State and Rule Visibility Encoding across Alliance Contribution Contract Hub while preserving the protected value.
- Evidence
- Solution Link Confirmed
- Outcome basis
- Design Evidence
Supporting Eligibility-to-Next-State Grammar
Apply State and Rule Visibility Encoding across Eligibility-to-Next-State Grammar while preserving the protected value.
- Evidence
- Solution Link Confirmed
- Outcome basis
- Design Evidence
Supporting Hero Next-State Grammar
Apply State and Rule Visibility Encoding across Hero Next-State Grammar while preserving the protected value.
- Evidence
- Solution Link Confirmed
- Outcome basis
- Design Evidence
Supporting Role & Result Legitimacy Receipt
Apply State and Rule Visibility Encoding across Role & Result Legitimacy Receipt while preserving the protected value.
- Evidence
- Solution Link Confirmed
- Outcome basis
- Design Evidence
Supporting Offer-to-Use Value Lineage Contract
Apply State and Rule Visibility Encoding across Offer-to-Use Value Lineage Contract 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 Three-Layer Growth Result Contract 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 Three-Layer Growth Result Contract Composition
Connect 1 source-declared mechanism across Three-Layer Growth Result Contract as Single-Track Localized Bundle.
- Evidence
- Solution Link Confirmed
- Outcome basis
- Design Evidence
Supporting DO- Alliance Contribution Contract Hub Composition
Connect 1 source-declared mechanism across Alliance Contribution Contract Hub as Single-Track Localized Bundle.
- Evidence
- Solution Link Confirmed
- Outcome basis
- Design Evidence
Supporting Eligibility-to-Next-State Grammar Composition
Connect 1 source-declared mechanism across Eligibility-to-Next-State Grammar as Single-Track Localized Bundle.
- Evidence
- Solution Link Confirmed
- Outcome basis
- Design Evidence
Supporting Hero Next-State Grammar Composition
Connect 1 source-declared mechanism across Hero Next-State Grammar as Single-Track Localized Bundle.
- Evidence
- Solution Link Confirmed
- Outcome basis
- Design Evidence
Supporting Role & Result Legitimacy Receipt Composition
Connect 1 source-declared mechanism across Role & Result Legitimacy Receipt as Single-Track Localized Bundle.
- Evidence
- Solution Link Confirmed
- Outcome basis
- Design Evidence
Supporting Offer-to-Use Value Lineage Contract Composition
Connect 1 source-declared mechanism across Offer-to-Use Value Lineage Contract as Single-Track Localized Bundle.
- Evidence
- Solution Link Confirmed
- Outcome basis
- Design Evidence
Supporting Parallel Solution-Mechanism Composition
Connect 6 source-declared mechanisms across Three-Layer Growth Result Contract 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 Three-Layer Growth Result Contract as Parallel Local Contracts with Independent Rollback.
- Evidence
- Solution Link Confirmed
- Outcome basis
- Design Evidence