Recurring Structures
Detailed Repeating Structures
What repeats and keeps the system moving?
Compounding Growth
Auto-clear main stages → claim idle rewards → summon, upgrade, and form heroes → run dungeons, arenas, or guild activities → return to main stages.
Outputs strengthen assets, capabilities, or access and open a stronger next cycle.
View pattern definition →Core Idle Growth Loop
Offline rewards → resource collection → hero growth → stage push → higher production loop.
Ruby
Competition/event rewards and shop offers feed ruby/ticket assets into / and back into growth.
Bottlenecks
Bottleneck Patterns
Where do decisions and flow break?
Pressure and Concentration Bottleneck
The affected flow runs through claim → spend; its limiting point is the operations pressure handoff.
Difficulty, randomness, growth, or completion pressure accumulates at one decision point and concentrates the burden of retrying or reinvesting.
View pattern definition →Pressure and Concentration Bottleneck · Operations
The affected flow runs through claim → spend; its limiting point is the operations pressure handoff.
Decision and Planning Calculability Breakdown · Growth Economy
The affected flow runs through claim → spend → stage_return; its limiting point is the growth economy planning handoff.
Action Feedback and Failure Attribution Break · Combat Feedback
The affected flow runs through Result explanation node / match-log-retry validation; its limiting point is the combat feedback result handoff.
Rights and Lifecycle Discontinuity · Asset
The affected flow runs through Target/recovery-state node / draw-pity-wait validation; its limiting point is the asset lifecycle handoff.
Legibility and Interpretation Break · Information
The affected flow runs through Roster taxonomy node / dwell-error-retry validation; its limiting point is the information interpretation handoff.
Rights and Lifecycle Discontinuity · Asset
The affected flow runs through Entitlement/renewal node / commerce validation; its limiting point is the asset lifecycle handoff.
Contradictions
Contradiction Patterns
What must improve, and what must remain protected?
Action and Return Continuity vs System Depth and Throughput
Across Main Stage, 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 Contradiction
Across Main Stage, improve Performance Vs Load while preserving Complexity Vs Convenience.
Complexity Vs Convenience / Freedom Vs Control
Across source/sink, improve Complexity Vs Convenience while preserving Freedom Vs Control.
Complexity Vs Convenience / Freedom Vs Control
Across roster taxonomy → preset, improve Complexity Vs Convenience while preserving Freedom Vs Control.
Speed Vs Integrity / Complexity Vs Convenience
Improve Speed Vs Integrity while preserving Complexity Vs Convenience.
Popularity Vs Scarcity / Revenue Vs Trust
Improve Popularity Vs Scarcity while preserving Revenue Vs Trust.
Revenue Vs Trust / Complexity Vs Convenience
Across entitlement → duration → renewal SKU, improve Revenue Vs Trust while preserving Complexity Vs Convenience.
Solution Mechanisms
Solution Mechanisms
Which intervention mechanism changes the condition?
Route and Return Handoff
Apply Route and Return Handoff across Return- Friction Extraction 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 →Return- Friction Extraction
Apply Route and Return Handoff across Return- Friction Extraction while preserving the protected value.
Cohort-Aware Growth Allocation Lens
Apply Route and Return Handoff across Cohort-Aware Growth Allocation Lens while preserving the protected value.
Layered Result Receipt & Retry Map
Apply Layered and Progressive Disclosure across Layered Result Receipt & Retry Map while preserving the protected value.
Target-Recovery Receipt & Capped Link
Apply Loss Trust and Entitlement Buffer across Target-Recovery Receipt & Capped Link while preserving the protected value.
Context-Keyed Taxonomy & Preset Overlay
Apply State and Rule Visibility Encoding across Context-Keyed Taxonomy & Preset Overlay while preserving the protected value.
Layered Entitlement Lifecycle Receipt
Apply Loss Trust and Entitlement Buffer across Layered Entitlement Lifecycle Receipt while preserving the protected value.
Return- Friction Extraction Composition
Connect 1 source-declared mechanism across Return- Friction Extraction as Single-Track Localized Bundle.
Cohort-Aware Growth Allocation Lens Composition
Connect 1 source-declared mechanism across Cohort-Aware Growth Allocation Lens as Single-Track Localized Bundle.
Layered Result Receipt & Retry Map Composition
Connect 1 source-declared mechanism across Layered Result Receipt & Retry Map as Single-Track Localized Bundle.
Target-Recovery Receipt & Capped Link Composition
Connect 1 source-declared mechanism across Target-Recovery Receipt & Capped Link as Single-Track Localized Bundle.
Context-Keyed Taxonomy & Preset Overlay Composition
Connect 1 source-declared mechanism across Context-Keyed Taxonomy & Preset Overlay as Single-Track Localized Bundle.
Layered Entitlement Lifecycle Receipt Composition
Connect 1 source-declared mechanism across Layered Entitlement Lifecycle Receipt as Single-Track Localized Bundle.
Parallel Solution-Mechanism Composition
Connect 6 source-declared mechanisms across Return- Friction Extraction as Core-First Branch-Sequential Portfolio.
Parallel Solution-Mechanism Composition
Connect 6 source-declared mechanisms across Return- Friction Extraction as Parallel Local Contracts with Independent Rollback.