Problem definition
Concurrent growth, mission, ad, event and guild tasks delay return to the main stage.
View all bottlenecksGAME DECISION MAP
Seven Knights Idle Adventure
Design direction
Reduce duplicate trips and checks along existing task-claim, reinvestment and main-stage return routes, connecting return readiness and actions.
View all mechanismsRead the recurring-flow summary
Auto-clear main stages → claim idle rewards → summon, upgrade, and form heroes → run dungeons, arenas, or guild activities → return to main stages.
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.
Return-Ready Friction Extraction
Cohort-Aware Growth Allocation Lens
Context-Keyed Taxonomy & Preset Overlay
Layered Result Receipt & Retry Map
Target-Recovery Receipt & Capped Link
Layered Entitlement Lifecycle Receipt
Goals and residual processing
Initial IFR · goal direction
Realign sequence, routing and exposure to recover volition and value.
Final IFR · design goal
Reduce duplicate round trips and repeated checks, bringing return readiness and the Main Stage return action forward.
Recurring Structures
Detailed Repeating Structures
What repeats and keeps the system moving?
2 analysis items · Read the method
Core classification and definition · Compounding Growth
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 →Supply Core Idle Growth Loop
Offline rewards → resource collection → hero growth → stage push → higher production loop.
- Evidence
- Source Described
- Outcome basis
- Design Evidence
Acquisition Ruby
Competition/event rewards and shop offers feed ruby/ticket assets into / and back into growth.
- Evidence
- Source Described
- Outcome basis
- Design Evidence
Core classification and definition · Pressure and Concentration Bottleneck
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 →Core Pressure and Concentration Bottleneck · Operations
The affected flow runs through claim → spend; its limiting point is the operations pressure handoff.
- Evidence
- Classification Confirmed
- Outcome basis
- Design Evidence
Supporting 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.
- Evidence
- Classification Confirmed
- Outcome basis
- Design Evidence
Supporting 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.
- Evidence
- Classification Confirmed
- Outcome basis
- Design Evidence
Supporting 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.
- Evidence
- Classification Confirmed
- Outcome basis
- Design Evidence
Supporting 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.
- Evidence
- Classification Confirmed
- Outcome basis
- Design Evidence
Supporting Rights and Lifecycle Discontinuity · Asset
The affected flow runs through Entitlement/renewal node / commerce validation; its limiting point is the asset lifecycle 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
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 Core Contradiction
Across Main Stage, improve Performance Vs Load while preserving Complexity Vs Convenience.
- Evidence
- Classification Confirmed
- Outcome basis
- Design Evidence
Supporting Complexity Vs Convenience / Freedom Vs Control
Across source/sink, improve Complexity Vs Convenience while preserving Freedom Vs Control.
- Evidence
- Classification Confirmed
- Outcome basis
- Design Evidence
Supporting Complexity Vs Convenience / Freedom Vs Control
Across roster taxonomy → preset, improve Complexity Vs Convenience while preserving Freedom Vs Control.
- Evidence
- Classification Confirmed
- Outcome basis
- Design Evidence
Supporting Speed Vs Integrity / Complexity Vs Convenience
Improve Speed Vs Integrity while preserving Complexity Vs Convenience.
- Evidence
- Classification Confirmed
- Outcome basis
- Design Evidence
Supporting Popularity Vs Scarcity / Revenue Vs Trust
Improve Popularity Vs Scarcity while preserving Revenue Vs Trust.
- Evidence
- Classification Confirmed
- Outcome basis
- Design Evidence
Supporting Revenue Vs Trust / Complexity Vs Convenience
Across entitlement → duration → renewal SKU, 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 · Route and Return Handoff
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 →Core Return- Friction Extraction
Apply Route and Return Handoff across Return- Friction Extraction while preserving the protected value.
- Evidence
- Solution Link Confirmed
- Outcome basis
- Design Evidence
Supporting Cohort-Aware Growth Allocation Lens
Apply Route and Return Handoff across Cohort-Aware Growth Allocation Lens while preserving the protected value.
- Evidence
- Solution Link Confirmed
- Outcome basis
- Design Evidence
Supporting Layered Result Receipt & Retry Map
Apply Layered and Progressive Disclosure across Layered Result Receipt & Retry Map while preserving the protected value.
- Evidence
- Solution Link Confirmed
- Outcome basis
- Design Evidence
Supporting Target-Recovery Receipt & Capped Link
Apply Loss Trust and Entitlement Buffer across Target-Recovery Receipt & Capped Link while preserving the protected value.
- Evidence
- Solution Link Confirmed
- Outcome basis
- Design Evidence
Supporting Context-Keyed Taxonomy & Preset Overlay
Apply State and Rule Visibility Encoding across Context-Keyed Taxonomy & Preset Overlay while preserving the protected value.
- Evidence
- Solution Link Confirmed
- Outcome basis
- Design Evidence
Supporting Layered Entitlement Lifecycle Receipt
Apply Loss Trust and Entitlement Buffer across Layered Entitlement Lifecycle Receipt 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 Return- Friction Extraction 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 Return- Friction Extraction Composition
Connect 1 source-declared mechanism across Return- Friction Extraction as Single-Track Localized Bundle.
- Evidence
- Solution Link Confirmed
- Outcome basis
- Design Evidence
Supporting Cohort-Aware Growth Allocation Lens Composition
Connect 1 source-declared mechanism across Cohort-Aware Growth Allocation Lens as Single-Track Localized Bundle.
- Evidence
- Solution Link Confirmed
- Outcome basis
- Design Evidence
Supporting Layered Result Receipt & Retry Map Composition
Connect 1 source-declared mechanism across Layered Result Receipt & Retry Map as Single-Track Localized Bundle.
- Evidence
- Solution Link Confirmed
- Outcome basis
- Design Evidence
Supporting Target-Recovery Receipt & Capped Link Composition
Connect 1 source-declared mechanism across Target-Recovery Receipt & Capped Link as Single-Track Localized Bundle.
- Evidence
- Solution Link Confirmed
- Outcome basis
- Design Evidence
Supporting Context-Keyed Taxonomy & Preset Overlay Composition
Connect 1 source-declared mechanism across Context-Keyed Taxonomy & Preset Overlay as Single-Track Localized Bundle.
- Evidence
- Solution Link Confirmed
- Outcome basis
- Design Evidence
Supporting Layered Entitlement Lifecycle Receipt Composition
Connect 1 source-declared mechanism across Layered Entitlement Lifecycle Receipt as Single-Track Localized Bundle.
- Evidence
- Solution Link Confirmed
- Outcome basis
- Design Evidence
Supporting Parallel Solution-Mechanism Composition
Connect 6 source-declared mechanisms across Return- Friction Extraction 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 Return- Friction Extraction as Parallel Local Contracts with Independent Rollback.
- Evidence
- Solution Link Confirmed
- Outcome basis
- Design Evidence