Problem definition
Failure to separate controllable causes from external power, guild and spending dependencies weakens retry and fairness judgments.
View all bottlenecksGAME DECISION MAP
Top Heroes
Design direction
Connect actionable causes, optional external-dependency context and existing details to formation changes and retry, keeping evidence for other domains separate.
View all mechanismsRead the recurring-flow summary
Explore and fight → recruit and level heroes → build the kingdom → join guild and competitive battles → expand territory.
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 Attribution & Correction
Layered Growth Path & Protection Board
Role-Cell Succession Buffer
Bounded Recovery-to-Completion Route
Choice-Preserving Cadence Contract
Selective Realized-Convenience Contract
Goals and residual processing
Initial IFR · goal direction
Realign exposure, sequence and rules in result and dependency contexts to recover trust and volition.
Final IFR · design goal
Align existing result detail around actionable attribution, optional detail depth, formation editing and retry using consistent criteria.
Recurring Structures
Detailed Repeating Structures
What repeats and keeps the system moving?
1 analysis items · Read the method
Core classification and definition · Compounding Growth
Compounding Growth
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 →Core Loop Risk
Loop overload can make gameplay feel like stockpiling and checklist management rather than distinct content experiences.
- Evidence
- Source Described
- Outcome basis
- Design Evidence
Core classification and definition · Action Feedback and Failure Attribution Break
Action Feedback and Failure Attribution 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 →Core result attribution
The affected flow runs through attribution node; its limiting point is the combat feedback result handoff.
- Evidence
- Classification Confirmed
- Outcome basis
- Design Evidence
Supporting next-growth continuity and investment protection break across parallel axes
The affected flow runs through allocation/protection rule; its limiting point is the asset lifecycle handoff.
- Evidence
- Classification Confirmed
- Outcome basis
- Design Evidence
Supporting routines, Point-Race and concurrent schedules transfer to hoarding
The affected flow runs through schedule node; its limiting point is the routine liveops return handoff.
- Evidence
- Classification Confirmed
- Outcome basis
- Design Evidence
Supporting failure
The affected flow runs through safety/exchange rule; its limiting point is the asset lifecycle handoff.
- Evidence
- Classification Confirmed
- Outcome basis
- Design Evidence
Supporting leader workload, time sync and top-power concentration transfer to organization fragility
The limiting point sits in the social operations coordination handoff.
- Evidence
- Classification Confirmed
- Outcome basis
- Design Evidence
Supporting queue
The limiting point sits in the operations pressure 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
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 →Core Core Contradiction
Across dependency context, improve Complexity Vs Convenience while preserving Freedom Vs Control.
- Evidence
- Classification Confirmed
- Outcome basis
- Design Evidence
Supporting — Growth Route Continuity
Improve Complexity Vs Convenience while preserving Freedom Vs Control.
- Evidence
- Classification Confirmed
- Outcome basis
- Design Evidence
Supporting — Calendar
Improve Performance Vs Load while preserving Stability Vs Volatility.
- Evidence
- Classification Confirmed
- Outcome basis
- Design Evidence
Supporting — Collection Recovery
Across recovery-to-completion, improve Popularity Vs Scarcity while preserving Revenue Vs Trust.
- Evidence
- Classification Confirmed
- Outcome basis
- Design Evidence
Supporting — Guild Key-Node Concentration
Across key-node, improve Performance Vs Load while preserving Freedom Vs Control.
- Evidence
- Classification Confirmed
- Outcome basis
- Design Evidence
Supporting — Promised-vs-Realized Convenience
Across entitlement, improve Revenue Vs Trust while preserving Performance Vs Load.
- 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 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 →Core Layered Attribution & Correction
Apply Layered and Progressive Disclosure across Layered Attribution & Correction while preserving the protected value.
- Evidence
- Solution Link Confirmed
- Outcome basis
- Design Evidence
Supporting Layered and Progressive Disclosure · Attachment
Apply Layered and Progressive Disclosure across Layered Growth Path & Protection Board while preserving the protected value.
- Evidence
- Solution Link Confirmed
- Outcome basis
- Design Evidence
Supporting Choice-Preserving Cadence Contract
Apply Cadence and Rhythm Coordination across Choice-Preserving Cadence Contract while preserving the protected value.
- Evidence
- Solution Link Confirmed
- Outcome basis
- Design Evidence
Supporting Bounded Recovery-to-Completion Route
Apply Loss Trust and Entitlement Buffer across Bounded Recovery-to-Completion Route while preserving the protected value.
- Evidence
- Solution Link Confirmed
- Outcome basis
- Design Evidence
Supporting Role-Cell Succession Buffer
Apply Context Asset and Authority Isolation across Role-Cell Succession Buffer while preserving the protected value.
- Evidence
- Solution Link Confirmed
- Outcome basis
- Design Evidence
Supporting Selective Realized-Convenience Contract
Apply State and Rule Visibility Encoding across Selective Realized-Convenience 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 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 →Core Layered Attribution & Correction Composition
Connect 1 source-declared mechanism across Layered Attribution & Correction as Single-Track Localized Bundle.
- Evidence
- Solution Link Confirmed
- Outcome basis
- Design Evidence
Supporting Layered and Progressive Disclosure · Attachment Composition
Connect 1 source-declared mechanism across Layered Growth Path & Protection Board as Single-Track Localized Bundle.
- Evidence
- Solution Link Confirmed
- Outcome basis
- Design Evidence
Supporting Choice-Preserving Cadence Contract Composition
Connect 1 source-declared mechanism across Choice-Preserving Cadence Contract as Single-Track Localized Bundle.
- Evidence
- Solution Link Confirmed
- Outcome basis
- Design Evidence
Supporting Bounded Recovery-to-Completion Route Composition
Connect 1 source-declared mechanism across Bounded Recovery-to-Completion Route as Single-Track Localized Bundle.
- Evidence
- Solution Link Confirmed
- Outcome basis
- Design Evidence
Supporting Role-Cell Succession Buffer Composition
Connect 1 source-declared mechanism across Role-Cell Succession Buffer as Single-Track Localized Bundle.
- Evidence
- Solution Link Confirmed
- Outcome basis
- Design Evidence
Supporting Selective Realized-Convenience Contract Composition
Connect 1 source-declared mechanism across Selective Realized-Convenience 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 Layered Attribution & Correction 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 Attribution & Correction as Parallel Local Contracts with Independent Rollback.
- Evidence
- Solution Link Confirmed
- Outcome basis
- Design Evidence