GAME DECISION MAP
Explore and fight → recruit and level heroes → build the kingdom → join guild and competitive battles → expand territory.
Recurring Structures
What repeats and keeps the system moving?
Explore and fight → recruit and level heroes → build the kingdom → join guild and competitive battles → expand territory.
Outputs strengthen assets, capabilities, or access and open a stronger next cycle.
View pattern definition →Loop overload can make gameplay feel like stockpiling and checklist management rather than distinct content experiences.
Bottlenecks
Where do decisions and flow break?
The affected flow runs through attribution node; its limiting point is the combat feedback result handoff.
Outcomes, causes, rules, rewards, and retry information do not close the feedback loop needed for correction.
View pattern definition →The affected flow runs through attribution node; its limiting point is the combat feedback result handoff.
The affected flow runs through allocation/protection rule; its limiting point is the asset lifecycle handoff.
The affected flow runs through schedule node; its limiting point is the routine liveops return handoff.
The affected flow runs through safety/exchange rule; its limiting point is the asset lifecycle handoff.
The limiting point sits in the social operations coordination handoff.
The limiting point sits in the operations pressure handoff.
Contradictions
What must improve, and what must remain protected?
Across dependency context, 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 →Across dependency context, improve Complexity Vs Convenience while preserving Freedom Vs Control.
Improve Complexity Vs Convenience while preserving Freedom Vs Control.
Improve Performance Vs Load while preserving Stability Vs Volatility.
Across recovery-to-completion, improve Popularity Vs Scarcity while preserving Revenue Vs Trust.
Across key-node, improve Performance Vs Load while preserving Freedom Vs Control.
Across entitlement, improve Revenue Vs Trust while preserving Performance Vs Load.
Solution Mechanisms
Which intervention mechanism changes the condition?
Apply Layered and Progressive Disclosure across Layered Attribution & Correction 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 →Apply Layered and Progressive Disclosure across Layered Attribution & Correction while preserving the protected value.
Apply Layered and Progressive Disclosure across Layered Growth Path & Protection Board while preserving the protected value.
Apply Cadence and Rhythm Coordination across Choice-Preserving Cadence Contract while preserving the protected value.
Apply Loss Trust and Entitlement Buffer across Bounded Recovery-to-Completion Route while preserving the protected value.
Apply Context Asset and Authority Isolation across Role-Cell Succession Buffer while preserving the protected value.
Apply State and Rule Visibility Encoding across Selective Realized-Convenience Contract while preserving the protected value.
Solution Compositions
How should interventions be combined and sequenced?
Connect 1 source-declared mechanism across Layered Attribution & Correction 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 Layered Attribution & Correction as Single-Track Localized Bundle.
Connect 1 source-declared mechanism across Layered Growth Path & Protection Board as Single-Track Localized Bundle.
Connect 1 source-declared mechanism across Choice-Preserving Cadence Contract as Single-Track Localized Bundle.
Connect 1 source-declared mechanism across Bounded Recovery-to-Completion Route as Single-Track Localized Bundle.
Connect 1 source-declared mechanism across Role-Cell Succession Buffer as Single-Track Localized Bundle.
Connect 1 source-declared mechanism across Selective Realized-Convenience Contract as Single-Track Localized Bundle.
Connect 6 source-declared mechanisms across Layered Attribution & Correction as Core-First Branch-Sequential Portfolio.
Connect 6 source-declared mechanisms across Layered Attribution & Correction as Parallel Local Contracts with Independent Rollback.