Problem definition
Difficulty calculating the full route from hero assets to completed growth, eligible teams and content outcomes.
View all bottlenecksGAME DECISION MAP
Seven Knights Re:BIRTH
Design direction
Layer growth, team eligibility, content entry, results and next actions in hero details, preserving existing values, probabilities and combat rules.
View all mechanismsRead the recurring-flow summary
Summon and collect heroes and pets → level, enhance, and awaken the roster → assemble eligible teams → play turn-based PvE, Arena, raids, and guild content → receive battle and activity rewards → reinvest Ruby and materials into heroes and the next formation.
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.
Hero transition-state contract
Growth-stop and next-route queue
Hero completion-state contract
Mode-specific defeat-cause contract
Optional-participation and return-right contract
Entitlement lifecycle-state contract
Goals and residual processing
Initial IFR · goal direction
Realign rules, sequence, exposure and attribution across existing growth, formation and result surfaces at state-and-result attribution junctions.
Final IFR · design goal
Arrange state, conditions and next actions in layers across existing hero, formation, entry and result surfaces while retaining growth and combat rules.
Recurring Structures
Detailed Repeating Structures
What repeats and keeps the system moving?
5 analysis items · Read the method
Core classification and definition · External Calendar
External Calendar
Summon and collect heroes and pets → level, enhance, and awaken the roster → assemble eligible teams → play turn-based PvE, Arena, raids, and guild content → receive battle and activity rewards → reinvest Ruby and materials into heroes and the next formation.
Events, operating schedules, and live operations reactivate participation, exchange, and reward states.
View pattern definition →Core Primary Growth Loop
Hero acquisition → adventure/repeat battle → level/ruby → dungeon/raid → growth/equipment → higher content → reinvestment.
- Evidence
- Source Described
- Outcome basis
- Design Evidence
Core Convenience Loop
First clear or setup → team copy/preset/booster/sweep/repeat battle → routine time reduction → more processing or background progress.
- Evidence
- Source Described
- Outcome basis
- Design Evidence
Competition Competition Return Loop
Growth assets → PvP modes → score/rank/currency/status → shop/growth/summon reinvestment → renewed competitiveness.
- Evidence
- Source Described
- Outcome basis
- Design Evidence
Cooperation Cooperation Return Loop
Guild joining → attendance/requests/siege/guild war/expedition → guild and personal rewards → personal/guild growth reinvestment.
- Evidence
- Source Described
- Outcome basis
- Design Evidence
Return LiveOps Acceleration Loop
Events layer missions, drops, points, pass, and special summon on top of existing content to drive focused re-entry.
- Evidence
- Source Described
- Outcome basis
- Design Evidence
Core classification and definition · Resource and Value Conversion Failure
Resource and Value Conversion Failure
The affected flow runs through state-result attribution; its limiting point is the economy commerce settlement handoff.
Currencies, assets, products, or inputs do not convert reliably into utility or residual value.
View pattern definition →Core asset→usable state→result
The affected flow runs through state-result attribution; its limiting point is the economy commerce settlement handoff.
- Evidence
- Classification Confirmed
- Outcome basis
- Design Evidence
Supporting source
The affected flow runs through source/sink → growth stop; its limiting point is the economy commerce settlement handoff.
- Evidence
- Classification Confirmed
- Outcome basis
- Design Evidence
Supporting overlap→deadline choice
The affected flow runs through overlap → deadline choice; its limiting point is the routine liveops return handoff.
- Evidence
- Classification Confirmed
- Outcome basis
- Design Evidence
Supporting right→use
The affected flow runs through right → use/expiry/CS; its limiting point is the asset lifecycle handoff.
- Evidence
- Classification Confirmed
- Outcome basis
- Design Evidence
Supporting detail→formation
The affected flow runs through detail → formation/Codex; its limiting point is the information interpretation handoff.
- Evidence
- Classification Confirmed
- Outcome basis
- Design Evidence
Supporting result→replay
The affected flow runs through result → replay/retry; its limiting point is the combat feedback result 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 · Input and Reward Value Closure vs Diversity and Invested-Asset Preservation
Input and Reward Value Closure vs Diversity and Invested-Asset Preservation
Across F/C/M, improve Complexity Vs Convenience while preserving Freedom Vs Control.
Time, currency, purchases, rewards, and held assets must close into trustworthy value while route diversity, scarcity, and invested assets remain protected.
View pattern definition →Core Core Contradiction
Across F/C/M, improve Complexity Vs Convenience while preserving Freedom Vs Control.
- Evidence
- Classification Confirmed
- Outcome basis
- Design Evidence
Supporting Freedom Vs Control / Revenue Vs Trust
Across source → gain → stock → spend → growth-stop → next-play, improve Freedom Vs Control while preserving Revenue Vs Trust.
- Evidence
- Classification Confirmed
- Outcome basis
- Design Evidence
Supporting Performance Vs Load / Stability Vs Volatility
Across voluntary/deadline → skip → unused right → post-return, improve Performance Vs Load while preserving Stability Vs Volatility.
- Evidence
- Classification Confirmed
- Outcome basis
- Design Evidence
Supporting ← - — entitlement lifecycle
Across offer/right/grant/use/expiry/reset/CS lifecycle → source integrity, improve Revenue Vs Trust while preserving Speed Vs Integrity.
- Evidence
- Classification Confirmed
- Outcome basis
- Design Evidence
Supporting Complexity Vs Convenience / Popularity Vs Scarcity
Across taxonomy/duplicate → formation/Codex → adoption terminal feedback, improve Complexity Vs Convenience while preserving Popularity Vs Scarcity.
- Evidence
- Classification Confirmed
- Outcome basis
- Design Evidence
Supporting Speed Vs Integrity / Complexity Vs Convenience
Across result → cause → learning/retry, improve Speed Vs Integrity 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 · State and Rule Visibility Encoding
State and Rule Visibility Encoding
Apply State and Rule Visibility Encoding across F/C/M while preserving the protected value.
Expose states, rules, and outcomes through readable signals and a consistent grammar to reduce decision loss.
View pattern definition →Core State and Rule Visibility Encoding · Core
Apply State and Rule Visibility Encoding across F/C/M while preserving the protected value.
- Evidence
- Solution Link Confirmed
- Outcome basis
- Design Evidence
Supporting Route and Return Handoff · Attachment
Apply Route and Return Handoff across source → gain → stock → spend → growth-stop → next-play while preserving the protected value.
- Evidence
- Solution Link Confirmed
- Outcome basis
- Design Evidence
Supporting Route and Return Handoff · Attachment
Apply Route and Return Handoff across voluntary/deadline → skip → unused right → post-return while preserving the protected value.
- Evidence
- Solution Link Confirmed
- Outcome basis
- Design Evidence
Supporting Loss Trust and Entitlement Buffer · Attachment
Apply Loss Trust and Entitlement Buffer across offer/right/grant/use/expiry/reset/CS lifecycle → source integrity while preserving the protected value.
- Evidence
- Solution Link Confirmed
- Outcome basis
- Design Evidence
Supporting State and Rule Visibility Encoding · Attachment
Apply State and Rule Visibility Encoding across taxonomy/duplicate → formation/Codex → adoption terminal feedback while preserving the protected value.
- Evidence
- Solution Link Confirmed
- Outcome basis
- Design Evidence
Supporting State and Rule Visibility Encoding · Attachment
Apply State and Rule Visibility Encoding across result → cause → learning/retry 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 F/C/M 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 State and Rule Visibility Encoding · Core Composition
Connect 1 source-declared mechanism across F/C/M as Single-Track Localized Bundle.
- Evidence
- Solution Link Confirmed
- Outcome basis
- Design Evidence
Supporting Route and Return Handoff · Attachment Composition
Connect 1 source-declared mechanism across source → gain → stock → spend → growth-stop → next-play as Single-Track Localized Bundle.
- Evidence
- Solution Link Confirmed
- Outcome basis
- Design Evidence
Supporting Route and Return Handoff · Attachment Composition
Connect 1 source-declared mechanism across voluntary/deadline → skip → unused right → post-return as Single-Track Localized Bundle.
- Evidence
- Solution Link Confirmed
- Outcome basis
- Design Evidence
Supporting Loss Trust and Entitlement Buffer · Attachment Composition
Connect 1 source-declared mechanism across offer/right/grant/use/expiry/reset/CS lifecycle → source integrity as Single-Track Localized Bundle.
- Evidence
- Solution Link Confirmed
- Outcome basis
- Design Evidence
Supporting State and Rule Visibility Encoding · Attachment Composition
Connect 1 source-declared mechanism across taxonomy/duplicate → formation/Codex → adoption terminal feedback as Single-Track Localized Bundle.
- Evidence
- Solution Link Confirmed
- Outcome basis
- Design Evidence
Supporting State and Rule Visibility Encoding · Attachment Composition
Connect 1 source-declared mechanism across result → cause → learning/retry as Single-Track Localized Bundle.
- Evidence
- Solution Link Confirmed
- Outcome basis
- Design Evidence
Supporting Parallel Solution-Mechanism Composition
Connect 6 source-declared mechanisms across F/C/M 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 F/C/M as Parallel Local Contracts with Independent Rollback.
- Evidence
- Solution Link Confirmed
- Outcome basis
- Design Evidence