Architecture & Design Decisions Log

ADR Registry

Date: 2026-10-10
Status: Accepted
Context: Driving feels sluggish and unnatural on Roblox if vehicle physics run server-side due to 50–150ms round-trip ping.
Decision: When a player sits in a vehicle seat, the server grants network ownership of the vehicle assembly to that client. The client computes all physics locally and streams transform updates to other players.
Consequences: Flawless, responsive 60 FPS steering feel. Requires server-side telemetry validation for delivery job completion to prevent teleportation exploits.

Date: 2026-10-10
Status: Accepted
Context: Games with only one currency suffer from inflation or allow wealthy players to bypass all progression hurdles by power-farming a single high-yield exploit.
Decision: Separate liquid money (Cash) from status (Reputation). Cash buys items; Rep unlocks access. Rep is non-transferable and earned purely through driving mastery and job completions.
Consequences: Preserves long-term engagement curves and gives clear aspirational milestones to early-game players.

Date: 2026-10-10
Status: Accepted
Context: The game is being solo-designed via Telegram brain dumps in Thai and English. A single, standardized documentation language is required to avoid drift.
Decision: GDD website is strictly English-only, generated via Astro Starlight with client-side Mermaid rendering, validated prior to every push by a headless parser. Raw Telegram messages remain in inbox/ for auditability.
Consequences: Standardized terminology, zero translation fragmentation across documentation pages, fast static builds.