Problem definition
A reading gap between combat causes, growth contribution, product value and next actions.
View all bottlenecksGAME DECISION MAP
Kingshot
Design direction
Layer causes, contribution and choices, evidence, and detailed traces across combat reports, formation, growth and shop touchpoints, preserving the combat engine, prices, growth and rewards.
View all mechanismsRead the recurring-flow summary
Rebuild and upgrade the Town under a Governor identity → recruit and grow Heroes, Troops, Gear, Pets, Master, and account multipliers → clear Conquest or Arena Hero Combat and Expedition, Rally, or Garrison Troop Combat → collect resources, Speedups, currencies, rank, status, and event outcomes → coordinate Help, Tech, Territory, roster, and warfare through an Alliance → compare free, focused-acquisition, shop, calendar, and settlement paths → return to the next Town, combat, Alliance, Kingdom, or Zone objective.
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 Evidence Trace
Contextual Status Provenance Trace
Voluntary Cadence Contract
Governor Promise Thread
Legacy Value Continuity Contract
Contextual Settlement Grammar Contract
Goals and residual processing
Initial IFR · goal direction
Realign exposure, sequence and rules at the shared cause-and-value interpretation junction to recover trust, value and volition.
Recurring Structures
Detailed Repeating Structures
What repeats and keeps the system moving?
1 analysis items · Read the method
Core classification and definition · Compounding Growth
Compounding Growth
Rebuild and upgrade the Town under a Governor identity → recruit and grow Heroes, Troops, Gear, Pets, Master, and account multipliers → clear Conquest or Arena Hero Combat and Expedition, Rally, or Garrison Troop Combat → collect resources, Speedups, currencies, rank, status, and event outcomes → coordinate Help, Tech, Territory, roster, and warfare through an Alliance → compare free, focused-acquisition, shop, calendar, and settlement paths → return to the next Town, combat, Alliance, Kingdom, or Zone objective.
Outputs strengthen assets, capabilities, or access and open a stronger next cycle.
View pattern definition →Core Core Loop: Growth → Cooperation → Competition → Reward → Regrowth
Town/hero/troop growth feeds alliance capability and kingdom/zone competition; competition rewards and status feed back into growth and war readiness.
- Evidence
- Source Described
- Outcome basis
- Design Evidence
Core classification and definition · Action Feedback and Failure Attribution Break
Action Feedback and Failure Attribution Break
The limiting point sits in the combat feedback result handoff.
Outcomes, causes, rules, rewards, and retry information do not close the feedback loop needed for correction.
View pattern definition →Core Action Feedback and Failure Attribution Break · Combat Feedback
The limiting point sits in the combat feedback result handoff.
- Evidence
- Classification Confirmed
- Outcome basis
- Design Evidence
Supporting Transition and Handoff Break ·
The limiting point sits in the transition handoff.
- Evidence
- Classification Confirmed
- Outcome basis
- Design Evidence
Supporting Pressure and Concentration Bottleneck · Operations
The limiting point sits in the operations pressure 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 Fairness and Legitimacy Erosion · Competition
The limiting point sits in the competition result handoff.
- Evidence
- Classification Confirmed
- Outcome basis
- Design Evidence
Supporting Obligation and Volition Erosion · Routine Liveops
The limiting point sits in the routine liveops return handoff.
- Evidence
- Classification Confirmed
- Outcome basis
- Design Evidence
Supporting Resource and Value Conversion Failure · Economy Commerce
The limiting point sits in the economy commerce settlement 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 trace, improve Complexity Vs Convenience while preserving Revenue Vs Trust.
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 trace, improve Complexity Vs Convenience while preserving Revenue Vs Trust.
- Evidence
- Classification Confirmed
- Outcome basis
- Design Evidence
Supporting Complexity Vs Convenience / Freedom Vs Control
Across Rank → Buff, improve Complexity Vs Convenience while preserving Freedom Vs Control.
- Evidence
- Classification Confirmed
- Outcome basis
- Design Evidence
Supporting Performance Vs Load / Stability Vs Volatility
Across deadline, improve Performance Vs Load while preserving Stability Vs Volatility.
- Evidence
- Classification Confirmed
- Outcome basis
- Design Evidence
Supporting Complexity Vs Convenience / Stability Vs Volatility
Across Town → Hero → Alliance War, improve Complexity Vs Convenience while preserving Stability Vs Volatility.
- Evidence
- Classification Confirmed
- Outcome basis
- Design Evidence
Supporting Stability Vs Volatility / Revenue Vs Trust
Improve Stability Vs Volatility while preserving Revenue Vs Trust.
- Evidence
- Classification Confirmed
- Outcome basis
- Design Evidence
Supporting Complexity Vs Convenience / Revenue Vs Trust
Across Source/Sink/Cost/Carry/Recovery, improve Complexity Vs Convenience while preserving Revenue Vs Trust.
- 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 Evidence Trace 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 Evidence Trace
Apply Layered and Progressive Disclosure across Layered Evidence Trace while preserving the protected value.
- Evidence
- Solution Link Confirmed
- Outcome basis
- Design Evidence
Supporting Governor Promise Thread
Apply State and Rule Visibility Encoding across Governor Promise Thread while preserving the protected value.
- Evidence
- Solution Link Confirmed
- Outcome basis
- Design Evidence
Supporting Legacy Value Continuity Contract
Apply Route and Return Handoff across Legacy Value Continuity Contract while preserving the protected value.
- Evidence
- Solution Link Confirmed
- Outcome basis
- Design Evidence
Supporting Contextual Status Provenance Trace
Apply State and Rule Visibility Encoding across Contextual Status Provenance Trace while preserving the protected value.
- Evidence
- Solution Link Confirmed
- Outcome basis
- Design Evidence
Supporting Voluntary Cadence Contract
Apply State and Rule Visibility Encoding across Voluntary Cadence Contract while preserving the protected value.
- Evidence
- Solution Link Confirmed
- Outcome basis
- Design Evidence
Supporting Contextual Settlement Grammar Contract
Apply Context Asset and Authority Isolation across Contextual Settlement Grammar 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 Evidence Trace 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 Evidence Trace Composition
Connect 1 source-declared mechanism across Layered Evidence Trace as Single-Track Localized Bundle.
- Evidence
- Solution Link Confirmed
- Outcome basis
- Design Evidence
Supporting Governor Promise Thread Composition
Connect 1 source-declared mechanism across Governor Promise Thread as Single-Track Localized Bundle.
- Evidence
- Solution Link Confirmed
- Outcome basis
- Design Evidence
Supporting Legacy Value Continuity Contract Composition
Connect 1 source-declared mechanism across Legacy Value Continuity Contract as Single-Track Localized Bundle.
- Evidence
- Solution Link Confirmed
- Outcome basis
- Design Evidence
Supporting Contextual Status Provenance Trace Composition
Connect 1 source-declared mechanism across Contextual Status Provenance Trace as Single-Track Localized Bundle.
- Evidence
- Solution Link Confirmed
- Outcome basis
- Design Evidence
Supporting Voluntary Cadence Contract Composition
Connect 1 source-declared mechanism across Voluntary Cadence Contract as Single-Track Localized Bundle.
- Evidence
- Solution Link Confirmed
- Outcome basis
- Design Evidence
Supporting Contextual Settlement Grammar Contract Composition
Connect 1 source-declared mechanism across Contextual Settlement Grammar 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 Evidence Trace 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 Evidence Trace as Parallel Local Contracts with Independent Rollback.
- Evidence
- Solution Link Confirmed
- Outcome basis
- Design Evidence