Problem definition
Accumulated rules, currencies and dependencies contribute to return and operating costs.
View all bottlenecksGAME DECISION MAP
Capybara Go!
Design direction
Build a layered continuity map while safeguarding growth depth, the economy, ownership, safety nets and free access.
View all mechanismsRead the recurring-flow summary
Advance Story Adventure with low-input Auto Turn Combat → resolve battle feedback and collect stage, AFK, Energy, sweep, event, Arena, Guild, and rewarded-access outcomes → acquire equipment, talents, inheritance materials, currencies, and collection assets → enhance, merge, inherit, and compose a build → validate progress in Adventure, competition, cooperation, and rotating events → compare free, saved, exchange, and optional paid routes → return to the next chapter, growth target, or activity.
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 Continuity Map
Attribution-to-Edit Ladder
Acquisition-to-Readiness Contract Ladder
Completion-to-Choice Relay
Free-Path Readiness Relay
Voluntary Contribution Lane & Async Mediation Contract
Goals and residual processing
Final IFR · design goal
Expose current state, dependencies, provenance and one next action at optional depth while retaining the underlying systems.
Recurring Structures
Detailed Repeating Structures
What repeats and keeps the system moving?
6 analysis items · Read the method
Core classification and definition · External Calendar
External Calendar
Advance Story Adventure with low-input Auto Turn Combat → resolve battle feedback and collect stage, AFK, Energy, sweep, event, Arena, Guild, and rewarded-access outcomes → acquire equipment, talents, inheritance materials, currencies, and collection assets → enhance, merge, inherit, and compose a build → validate progress in Adventure, competition, cooperation, and rotating events → compare free, saved, exchange, and optional paid routes → return to the next chapter, growth target, or activity.
Events, operating schedules, and live operations reactivate participation, exchange, and reward states.
View pattern definition →Supply Story Progression Loop
Energy → Story/Travel → basic rewards/equipment → Equipment/Talent growth → upper chapter unlock.
- Evidence
- Source Described
- Outcome basis
- Design Evidence
Supply Specialized Growth Loop
Ticket/Voucher/Key → Challenge/Dungeon → dedicated materials → Pet/Mount/Artifact/Adventurer/Specialization/Gem growth → higher difficulty.
- Evidence
- Source Described
- Outcome basis
- Design Evidence
Competition Competition Validation Loop
Growth build → Arena/Seal/Tournament → rank/division/reward → growth reinvestment → next season competition.
- Evidence
- Source Described
- Outcome basis
- Design Evidence
Cooperation Cooperation Reinforcement Loop
Guild/partner content → shared progress, Guild Coin, Aid Token and rewards → shop/growth → stronger future contribution.
- Evidence
- Source Described
- Outcome basis
- Design Evidence
Return LiveOps Acceleration Loop
Daily/limited missions specify growth actions and resource use, then return event currencies, gacha tokens and growth materials.
- Evidence
- Source Described
- Outcome basis
- Design Evidence
Return Return Loop
Offline time → AFK rewards → immediate reinforcement → frontier retry → daily/weekly routine re-entry.
- Evidence
- Source Described
- Outcome basis
- Design Evidence
Core classification and definition · Pressure and Concentration Bottleneck
Pressure and Concentration Bottleneck
The limiting point sits in 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 accretion→legacy
The limiting point sits in the operations pressure handoff.
- Evidence
- Classification Confirmed
- Outcome basis
- Design Evidence
Supporting schedule→fragmentation
The limiting point sits in the liveops operations synchronization handoff.
- Evidence
- Classification Confirmed
- Outcome basis
- Design Evidence
Supporting attribution→learning
The limiting point sits in the combat feedback result handoff.
- Evidence
- Classification Confirmed
- Outcome basis
- Design Evidence
Supporting free opportunity→re-entry
The limiting point sits in the entry handoff.
- Evidence
- Classification Confirmed
- Outcome basis
- Design Evidence
Supporting acquisition→usable completion
The limiting point sits in the asset lifecycle handoff.
- Evidence
- Classification Confirmed
- Outcome basis
- Design Evidence
Supporting paid velocity→performance
The limiting point sits in the competition result handoff.
- Evidence
- Classification Confirmed
- Outcome basis
- Design Evidence
Supporting reward→next advantage
The limiting point sits in the transition handoff.
- Evidence
- Classification Confirmed
- Outcome basis
- Design Evidence
Supporting participation→completion
The limiting point sits in the transition handoff.
- Evidence
- Classification Confirmed
- Outcome basis
- Design Evidence
Supporting partner
The limiting point sits in the social operations coordination 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 Layer → Currency → SKU → Event → legacy → QA/CS/ TAT, improve Complexity Vs Convenience while preserving None.
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 Layer → Currency → SKU → Event → legacy → QA/CS/ TAT, improve Complexity Vs Convenience while preserving None.
- Evidence
- Classification Confirmed
- Outcome basis
- Design Evidence
Supporting Complexity Vs Convenience / Speed Vs Integrity
Across CP → RNG → skill → choice feedback → build edit → retry, improve Complexity Vs Convenience while preserving Speed Vs Integrity.
- Evidence
- Classification Confirmed
- Outcome basis
- Design Evidence
Supporting Revenue Vs Trust / Complexity Vs Convenience
Across target → rotation → completion cost/time → acquisition usable build completion, improve Revenue Vs Trust while preserving Complexity Vs Convenience.
- Evidence
- Classification Confirmed
- Outcome basis
- Design Evidence
Supporting Performance Vs Load / Freedom Vs Control
Across participation → completion → reward use → next action ordered closure, improve Performance Vs Load while preserving Freedom Vs Control.
- Evidence
- Classification Confirmed
- Outcome basis
- Design Evidence
Supporting Performance Vs Load / Freedom Vs Control
Across free supply/opportunity → upgrade → re-entry continuity progression step predictability, improve Performance Vs Load while preserving Freedom Vs Control.
- Evidence
- Classification Confirmed
- Outcome basis
- Design Evidence
Supporting Freedom Vs Control / Performance Vs Load
Across Co-op access, helper supply, contribution → settlement legibility and sustainable operator value, improve Freedom Vs Control 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 Continuity Map 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 Continuity Map
Apply Layered and Progressive Disclosure across Layered Continuity Map while preserving the protected value.
- Evidence
- Solution Link Confirmed
- Outcome basis
- Design Evidence
Supporting Attribution-to-Edit Ladder
Apply State and Rule Visibility Encoding across Attribution-to-Edit Ladder while preserving the protected value.
- Evidence
- Solution Link Confirmed
- Outcome basis
- Design Evidence
Supporting Free-Path Readiness Relay
Apply Route and Return Handoff across Free-Path Readiness Relay while preserving the protected value.
- Evidence
- Solution Link Confirmed
- Outcome basis
- Design Evidence
Supporting Acquisition-to-Readiness Contract Ladder
Apply State and Rule Visibility Encoding across Acquisition-to-Readiness Contract Ladder while preserving the protected value.
- Evidence
- Solution Link Confirmed
- Outcome basis
- Design Evidence
Supporting Completion-to-Choice Relay
Apply State and Rule Visibility Encoding across Completion-to-Choice Relay while preserving the protected value.
- Evidence
- Solution Link Confirmed
- Outcome basis
- Design Evidence
Supporting Voluntary Contribution Lane & Async Mediation Contract
Apply Context Asset and Authority Isolation across Voluntary Contribution Lane & Async Mediation 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 Continuity Map 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 Continuity Map Composition
Connect 1 source-declared mechanism across Layered Continuity Map as Single-Track Localized Bundle.
- Evidence
- Solution Link Confirmed
- Outcome basis
- Design Evidence
Supporting Attribution-to-Edit Ladder Composition
Connect 1 source-declared mechanism across Attribution-to-Edit Ladder as Single-Track Localized Bundle.
- Evidence
- Solution Link Confirmed
- Outcome basis
- Design Evidence
Supporting Free-Path Readiness Relay Composition
Connect 1 source-declared mechanism across Free-Path Readiness Relay as Single-Track Localized Bundle.
- Evidence
- Solution Link Confirmed
- Outcome basis
- Design Evidence
Supporting Acquisition-to-Readiness Contract Ladder Composition
Connect 1 source-declared mechanism across Acquisition-to-Readiness Contract Ladder as Single-Track Localized Bundle.
- Evidence
- Solution Link Confirmed
- Outcome basis
- Design Evidence
Supporting Completion-to-Choice Relay Composition
Connect 1 source-declared mechanism across Completion-to-Choice Relay as Single-Track Localized Bundle.
- Evidence
- Solution Link Confirmed
- Outcome basis
- Design Evidence
Supporting Voluntary Contribution Lane & Async Mediation Contract Composition
Connect 1 source-declared mechanism across Voluntary Contribution Lane & Async Mediation 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 Continuity Map 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 Continuity Map as Parallel Local Contracts with Independent Rollback.
- Evidence
- Solution Link Confirmed
- Outcome basis
- Design Evidence