Problem definition
A break in the growth cycle linking campaign progress, outpost production, Core Dust and shared levels.
View all bottlenecksGAME DECISION MAP
Goddess of Victory: NIKKE
Design direction
Layer campaign progress, production state, resource needs, shared levels and the next battle, preserving combat, production, growth and recruitment values.
View all mechanismsRead the recurring-flow summary
Build a five-Nikke squad → aim, cover, reload, and trigger Burst chains in Campaign and combat modes → gain rewards and raise Outpost Defense → accumulate idle growth resources → level, skill, equip, and synchronize Nikkes → recruit or refine the roster and enter the next battle.
REASONING IN THIS GAME
Selected designs and judgment conditions
Selected principles and the game-local design5 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.
Growth-cycle continuity layer
Combat-readiness connection card
Optional event-joining board
Banner-specific recruitment-choice ledger
Multiple-squad allocation and performance-attribution ledger
Goals and residual processing
Initial IFR · goal direction
Realign state, sequence, exposure, reward and operating conditions to recover trust, volition and value.
Final IFR · design goal
Connect existing Outpost, Core Dust, shared-level and retry or return states and routes through a continuity layer after Campaign failure.
Recurring Structures
Detailed Repeating Structures
What repeats and keeps the system moving?
4 analysis items · Read the method
Core classification and definition · External Calendar
External Calendar
Build a five-Nikke squad → aim, cover, reload, and trigger Burst chains in Campaign and combat modes → gain rewards and raise Outpost Defense → accumulate idle growth resources → level, skill, equip, and synchronize Nikkes → recruit or refine the roster and enter the next battle.
Events, operating schedules, and live operations reactivate participation, exchange, and reward states.
View pattern definition →Supply Campaign–Idle Loop
Campaign clear increases Outpost productivity; Outpost resources fuel level growth; level growth enables next campaign clear.
- Evidence
- Source Described
- Outcome basis
- Design Evidence
Supply Daily Specialized Farming Loop
Outpost, Dispatch, Simulation Room, Interception and daily missions route recurring resources into growth.
- Evidence
- Source Described
- Outcome basis
- Design Evidence
Supply Vertical Challenge Loop
Tribe Tower, Lost Sector, Overclock and Solo Raid Museum validate power and supply specialized growth resources.
- Evidence
- Source Described
- Outcome basis
- Design Evidence
Return Seasonal Acceleration Loop
Events, mini-games, login, FULL BURST DAY and raids create short-term resource acceleration and return reasons.
- Evidence
- Source Described
- Outcome basis
- Design Evidence
Core classification and definition · Transition and Handoff Break
Transition and Handoff Break
The affected flow runs through Mileage → CS; its limiting point is the transition handoff.
The result of one step does not connect to the next action, return, or reinvestment decision.
View pattern definition →Core Transition and Handoff Break ·
The affected flow runs through Mileage → CS; its limiting point is the transition handoff.
- Evidence
- Classification Confirmed
- Outcome basis
- Design Evidence
Supporting Rights and Lifecycle Discontinuity · Asset
The limiting point sits in the asset lifecycle handoff.
- Evidence
- Classification Confirmed
- Outcome basis
- Design Evidence
Supporting Obligation and Volition Erosion · Routine Liveops
The affected flow runs through Event/Core faucet; its limiting point is the routine liveops return handoff.
- Evidence
- Classification Confirmed
- Outcome basis
- Design Evidence
Supporting Rights and Lifecycle Discontinuity · Asset
The affected flow runs through Mileage → CS; its limiting point is the asset lifecycle handoff.
- Evidence
- Classification Confirmed
- Outcome basis
- Design Evidence
Supporting Allocation and Coordination Failure · Social Operations
The affected flow runs through Arena 2 +Solo Raid 1; its limiting point is the social operations coordination handoff.
- Evidence
- Classification Confirmed
- Outcome basis
- Design Evidence
Contradictions
Contradiction Patterns
What must improve, and what must remain protected?
5 analysis items · Read the method
Core classification and definition · State and Timing Integrity vs Operational Volatility
State and Timing Integrity vs Operational Volatility
Improve Stability Vs Volatility while preserving Complexity Vs Convenience.
State, deadline, channel, and charge consistency must improve while legitimate operating rhythm, variation, and speed remain protected.
View pattern definition →Core Core Contradiction
Improve Stability Vs Volatility while preserving Complexity Vs Convenience.
- Evidence
- Classification Confirmed
- Outcome basis
- Design Evidence
Supporting Complexity Vs Convenience / Performance Vs Load
Improve Complexity Vs Convenience while preserving Performance Vs Load.
- Evidence
- Classification Confirmed
- Outcome basis
- Design Evidence
Supporting Stability Vs Volatility / Complexity Vs Convenience
Improve Stability Vs Volatility while preserving Complexity Vs Convenience.
- Evidence
- Classification Confirmed
- Outcome basis
- Design Evidence
Supporting Revenue Vs Trust / Popularity Vs Scarcity
Improve Revenue Vs Trust while preserving Popularity Vs Scarcity.
- Evidence
- Classification Confirmed
- Outcome basis
- Design Evidence
Supporting Complexity Vs Convenience / Freedom Vs Control
Improve Complexity Vs Convenience while preserving Freedom Vs Control.
- Evidence
- Classification Confirmed
- Outcome basis
- Design Evidence
Solution Mechanisms
Solution Mechanisms
Which intervention mechanism changes the condition?
5 analysis items · Read the method
Core classification and definition · Route and Return Handoff
Route and Return Handoff
Apply Route and Return Handoff to the source-declared core track while preserving its protected value.
Connect the current state to valid next actions, routes, retries, and returns while preserving choice and existing paths.
View pattern definition →Core Route and Return Handoff · Core
Apply Route and Return Handoff to the source-declared core track while preserving its protected value.
- Evidence
- Solution Link Confirmed
- Outcome basis
- Design Evidence
Supporting State and Rule Visibility Encoding · Attachment
Apply State and Rule Visibility Encoding to the source-declared attachment track while preserving its protected value.
- Evidence
- Solution Link Confirmed
- Outcome basis
- Design Evidence
Supporting State and Rule Visibility Encoding · Attachment
Apply State and Rule Visibility Encoding to the source-declared attachment track while preserving its protected value.
- Evidence
- Solution Link Confirmed
- Outcome basis
- Design Evidence
Supporting State and Rule Visibility Encoding · Attachment
Apply State and Rule Visibility Encoding to the source-declared attachment track while preserving its protected value.
- Evidence
- Solution Link Confirmed
- Outcome basis
- Design Evidence
Supporting State and Rule Visibility Encoding · Attachment
Apply State and Rule Visibility Encoding to the source-declared attachment track while preserving its protected value.
- Evidence
- Solution Link Confirmed
- Outcome basis
- Design Evidence
Solution Compositions
Solution Compositions
How should interventions be combined and sequenced?
7 analysis items · Read the method
Core classification and definition · Single-Track Localized Bundle
Single-Track Localized Bundle
Connect 1 source-declared mechanism 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 Route and Return Handoff · Core Composition
Connect 1 source-declared mechanism 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 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 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 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 as Single-Track Localized Bundle.
- Evidence
- Solution Link Confirmed
- Outcome basis
- Design Evidence
Supporting Parallel Solution-Mechanism Composition
Connect 5 source-declared mechanisms as Core-First Branch-Sequential Portfolio.
- Evidence
- Solution Link Confirmed
- Outcome basis
- Design Evidence
Supporting Parallel Solution-Mechanism Composition
Connect 5 source-declared mechanisms as Parallel Local Contracts with Independent Rollback.
- Evidence
- Solution Link Confirmed
- Outcome basis
- Design Evidence