NOVASMC

GAME DECISION MAP

Asphalt Legends Unite

Arcade Racing · Cross-platform · 2024

Current analysisBaseline 2026-06-04Open Decision Analysis →

Choose a licensed target vehicle and route → race with TouchDrive or Manual using drift, Nitro, stunts, and route choice → earn Blueprints, Credits, Parts, Keys, event currency, Rating, and RP → unlock, Star Up, upgrade, and present the Garage portfolio → enter Career, Showroom, Hunts, seasonal events, competition, Clubs, and commerce paths → use the resulting state to select the next vehicle journey and race.

Recurring Structures

Detailed Repeating Structures

What repeats and keeps the system moving?

CORE CLASSIFICATION

External Calendar

Choose a licensed target vehicle and route → race with TouchDrive or Manual using drift, Nitro, stunts, and route choice → earn Blueprints, Credits, Parts, Keys, event currency, Rating, and RP → unlock, Star Up, upgrade, and present the Garage portfolio → enter Career, Showroom, Hunts, seasonal events, competition, Clubs, and commerce paths → use the resulting state to select the next vehicle journey and race.

Events, operating schedules, and live operations reactivate participation, exchange, and reward states.

View pattern definition →
  1. Supply

    Race → Reward → Garage Update loop

    Mechanical core: race execution produces rewards that change Garage state and unlock/performance eligibility.

Bottlenecks

Bottleneck Patterns

Where do decisions and flow break?

CORE CLASSIFICATION

Decision and Planning Calculability Breakdown

The affected flow runs through joined route outcomes by persona window; its limiting point is the growth economy planning handoff.

Multiple goals, resources, states, rules, and paths cannot be compared on one decision surface, forcing repeated reprioritization.

View pattern definition →
  1. Core

    route-state next-action and completion calculability

    The affected flow runs through joined route outcomes by persona window; its limiting point is the growth economy planning handoff.

  2. Supporting

    gate vector→forecast→completion

    The affected flow runs through gate vector → forecast → completion; its limiting point is the rules handoff.

  3. Supporting

    precondition→result→retry

    The affected flow runs through precondition → result → retry; its limiting point is the combat feedback result handoff.

  4. Supporting

    calendar workload and displacement remain

    The affected flow runs through increment/displacement/value-cost; its limiting point is the routine liveops return handoff.

  5. Supporting

    utility, status and ownership meaning remain

    The affected flow runs through 90/180-day linkage; its limiting point is the asset lifecycle handoff.

  6. Supporting

    random tail, duplicate progression and terminal safety remain

    The affected flow runs through distribution/duration/support linkage; its limiting point is the asset lifecycle handoff.

Contradictions

Contradiction Patterns

What must improve, and what must remain protected?

CORE CLASSIFICATION

Action and Return Continuity vs System Depth and Throughput

Improve Complexity Vs Convenience while preserving Freedom Vs Control.

Continuity to the next action, return, or reinvestment must improve while route diversity, strategic depth, and throughput remain protected.

View pattern definition →
  1. Core

    Core Contradiction

    Improve Complexity Vs Convenience while preserving Freedom Vs Control.

  2. Supporting

    Gate-stack Completion Forecast

    Improve Performance Vs Load while preserving Complexity Vs Convenience.

  3. Supporting

    Competition Outcome Attribution

    Across result attribution and retry meaning under controlled match conditions, improve Complexity Vs Convenience while preserving None.

  4. Supporting

    LiveOps Workload & Displacement

    Across event increment, calendar workload and displaced-behavior legibility, improve Stability Vs Volatility while preserving Performance Vs Load.

  5. Supporting

    Vehicle Investment Half-life

    Across acquired-vehicle utility, status and ownership continuity over cohort windows, improve Stability Vs Volatility while preserving Popularity Vs Scarcity.

  6. Supporting

    Acquisition Tail-cost Safety

    Across acquisition tail, duration, duplicate progression and terminal-safety legibility, improve Popularity Vs Scarcity while preserving Revenue Vs Trust.

Solution Mechanisms

Solution Mechanisms

Which intervention mechanism changes the condition?

CORE CLASSIFICATION

Layered and Progressive Disclosure

Apply Layered and Progressive Disclosure across Layered Target Journey Contract 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 →
  1. Core

    Layered Target Journey Contract

    Apply Layered and Progressive Disclosure across Layered Target Journey Contract while preserving the protected value.

  2. Supporting

    Gate-State Preflight Forecast Contract

    Apply State and Rule Visibility Encoding across Gate-State Preflight Forecast Contract while preserving the protected value.

  3. Supporting

    Layered Result Attribution & Retry Contract

    Apply Layered and Progressive Disclosure across Layered Result Attribution & Retry Contract while preserving the protected value.

  4. Supporting

    Capacity-Bounded LiveOps Rhythm Contract

    Apply Cadence and Rhythm Coordination across Capacity-Bounded LiveOps Rhythm Contract while preserving the protected value.

  5. Supporting

    Dual-Value Vehicle Lifecycle Continuity Contract

    Apply Context Asset and Authority Isolation across Dual-Value Vehicle Lifecycle Continuity Contract while preserving the protected value.

  6. Supporting

    Bounded Tail-to-Completion Safety Contract

    Apply Loss Trust and Entitlement Buffer across Bounded Tail-to-Completion Safety Contract while preserving the protected value.

Solution Compositions

Solution Compositions

How should interventions be combined and sequenced?

CORE CLASSIFICATION

Single-Track Localized Bundle

Connect 1 source-declared mechanism across Layered Target Journey Contract 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 →
  1. Core

    Layered Target Journey Contract Composition

    Connect 1 source-declared mechanism across Layered Target Journey Contract as Single-Track Localized Bundle.

  2. Supporting

    Gate-State Preflight Forecast Contract Composition

    Connect 1 source-declared mechanism across Gate-State Preflight Forecast Contract as Single-Track Localized Bundle.

  3. Supporting

    Layered Result Attribution & Retry Contract Composition

    Connect 1 source-declared mechanism across Layered Result Attribution & Retry Contract as Single-Track Localized Bundle.

  4. Supporting

    Capacity-Bounded LiveOps Rhythm Contract Composition

    Connect 1 source-declared mechanism across Capacity-Bounded LiveOps Rhythm Contract as Single-Track Localized Bundle.

  5. Supporting

    Dual-Value Vehicle Lifecycle Continuity Contract Composition

    Connect 1 source-declared mechanism across Dual-Value Vehicle Lifecycle Continuity Contract as Single-Track Localized Bundle.

  6. Supporting

    Bounded Tail-to-Completion Safety Contract Composition

    Connect 1 source-declared mechanism across Bounded Tail-to-Completion Safety Contract as Single-Track Localized Bundle.

  7. Supporting

    Parallel Solution-Mechanism Composition

    Connect 6 source-declared mechanisms across Layered Target Journey Contract as Core-First Branch-Sequential Portfolio.

  8. Supporting

    Parallel Solution-Mechanism Composition

    Connect 6 source-declared mechanisms across Layered Target Journey Contract as Parallel Local Contracts with Independent Rollback.