The development workspace for WorldStead Roleplay. Explore the platforms, geography and evidence behind the fictional United States of Ingrossia.
OFFICIAL WORLDSTEAD IDENTITYWorldStead is a civilian-first FiveM roleplay and systems-simulation project set in the original United States of Ingrossia. The program is pushing GTA V/FiveM toward its practical limits with deeper vehicle behavior, persistent world consequences, responsive NPCs, believable public safety, and a long-term path toward a standalone game. The entries below describe current engineering work and approved goals—not a list of live, completed features.
BMW 330i (G20) engineering blockout: 117 named parts and 189 one-inch reference stations; intermediate 3D output is not a finished GTA vehicle. ws_crash impact telemetry has passed local calculations. Vehicle-registration and in-game crash-physics acceptance tests remain outstanding.
The United States of Ingrossia has a 12-state planning atlas; the V0.16 map is a conceptual reference, not surveyed game terrain. Terrain, realistic cities, road networks, state climates, streaming/LOD and civilian highway/county/city traffic remain active development targets. Brinlow is at survey/staging rather than verified map construction.
ws_interaction is being moved toward free-mouse Third Eye targeting, with integration and visibility defects still requiring live tests. Character persistence, main-menu sizing, PvP configuration and day-to-day civilian activities are tracked work; ws_phone, ws_camera and deeper jobs are design/build priorities.
The aim is a WorldStead-owned dispatch and law model instead of GTA's native wanted behavior. Native wanted suppression in ws_dispatch has been tested in gameplay, including multiplayer. PASS (user-confirmed October 26): GTA's native wanted system does not trigger. This confirms wanted-level suppression, not completion of the separate custom dispatch and responder lifecycle. Computer Aided Dispatch and Mobile Data Terminal are separate professional workflows; radio operation stays inside ws_radio. Server-authoritative sirens and ELS controller/park-mode concepts remain in development.
ws_radio targets the sound characteristics of AMBE+2 digital equipment, without using the licensed codec, with nearby people able to hear a speaker radio. NPC voice/world-knowledge integration, advanced driving/flight/damage mechanics, and ws_tank are staged or planned; the tank Lua damage-model checks were offline only.
ws_database is a prototype independent C++17 storage engine with nine isolated tests passed, not a production MariaDB replacement. Existing persistence must stay safe until migrations and FiveM integration are demonstrated. SHIN Link, staged packages, resource manifests, server configuration, and EDP's actual in-game test gates remain central to delivery.
This is the official Ingrossia map from worldsteadrp.com, not a generated replacement.
States are defined by landscapes, cities, seasonal patterns and transportation links—not generic biome labels.
The Atlas is a historical reference. Proposed systems are not automatically considered operational, and implementation status requires direct server verification.
DEVELOPMENT SYSTEMSEDITION 05 CONCEPT · ACTUAL MAP ASSET · NO SERVER CHANGESA full architectural reference for WorldStead Roleplay—from character identity and vehicle physics to national geography, jobs, climate, public safety and operational controls.
Every capability gets one authority, explicit dependencies, persisted state, meaningful failure behavior, telemetry and a rollback path. Existing progress is preserved until replacement parity is demonstrated.
The anatomy of an interconnected nation—eight engineering domains and their documented authority contracts.
Navigate the eight major domains and their constituent resources. This is a working index, not a decorative diagram.
Trace every documented resource, owner, dependency and evidence gap. Interactive links visualize the recorded design—not live execution.
This resource registry is the historical October 20 architecture inventory. Recent work includes ws_database, ws_crash, ws_interaction, ws_tank, ws_world, and BMW G20 vehicle engineering. A resource name or an offline package does not establish a live installation.
Use this table to navigate system ownership and dependencies; confirm manifests, startup order, resource exports, multiplayer behavior and rollback evidence before marking any change production-ready.
Every tracked component retains its Oct 20 evidence level, owner domain, integration gaps and next verification task.
Explore documented provider → consumer relationships. This diagram is an editorial visualization of the Architecture Atlas dataset, not an active FiveM linker or a live dependency scan.
| Resource | Ownership | Evidence | Priority |
|---|
One geographic identity, twelve states, nine planned highways and an illustrated world still subject to engine feasibility.
A closer look at the approved twelve-state United States of Ingrossia, its planned cities, landscapes, communities and interstate corridors.
Concept geography · Not surveyed. The map and highlighted routes represent proposed national infrastructure, not verified FiveM terrain, collision geometry or measured highway distances. State-specific details below are sourced from the WorldStead public /world page.
Six primary interstates and three metropolitan auxiliary routes, reproduced from the public WorldStead plan. Select a highway to inspect its named destinations and illustrated corridor.
The 45–60 minute representative state-crossing goal and earlier Southport → Northgate 235-mile concept are unverified design targets, not measured routing or real driving ETAs.
ws_world owns geographic identity; ws_coordinates spatial topology; ws_navigations routes; streamed map assets handle terrain; FGVO handles graphics. A web map is not proof of a complete playable FiveM nation.
Source snapshot: WorldStead Roleplay /world, map asset ingrossia-map-routes-v16.webp. Architecture Atlas's complete WSRP-ARCH 1.0 technical blueprint remains separately preserved.
Acceptance gates, historical hazards and verification criteria belong in a dedicated quality workspace.
Acceptance gates and historical risks. Nothing is green until evidence establishes that it works.
The complete milestone and architectural decision ledgers, grouped by evidence and priority—not by assumed deployment.
ws_crash telemetry checks passed offline. ws_vehicle registry/manifest integration still needs live resource acceptance.ws_dispatch was tested with another player. The user confirmed on October 26 that native wanted levels no longer trigger: PASS. This does not imply that the separate managed-officer and incident-response workflows are fully accepted. ws_law and ws_dispatch remain distinct. CAD and MDT stay separate from ws_radio; sirens and ELS remain specialized subsystems.ws_database C++17 prototype passed 9/9 isolated tests, but compatibility, transactions, migration safety and live FiveM use are unproven. Keep legacy storage intact.ws_tank Lua damage checks passed in isolation; server manifest, activation and in-game tests still need confirmation. Use EDP and SHIN Link snapshots for traceable staged changes.Acceptance rule: source or offline test success is not equivalent to a live WorldStead deployment. txAdmin remains in current use while ws_staff is developed as a future replacement.
Twenty documented milestone gates carried forward from the project control workbook. No in-game rollout is inferred from this page.
An indexed, unabridged technical specification for the WorldStead platform, its operating standards and its migration plan.
Unabridged architecture specification, preserved from V1.0 and indexed for reading.
Architecture: WSRP-ARCH 1.0 (design baseline)
Date: 2026-10-23
Scope: Entire WorldStead FiveM Legacy platform, Ingrossia national simulation, existing resources and planned systems
Status: Design deliverable; no live server changes, migrations, installation, or restarts executed
Source evidence: WorldStead Project Control — 2026-10-20 (60 tracked systems, 18 decisions, 29 dependencies, 26 QA gates); WorldStead Original World Foundation V0.1; October 21–23 owner-reported changes and approved Ingrossia atlas.
Evidence discipline: Historic status is not contemporary production certification. Keep user-observed progress separate from verified deployed hashes and two-client gameplay tests.
This is a whole-platform architecture refactor. The prior employment-only response was incomplete and is superseded. WorldStead becomes a modular, server-authoritative, persistent simulation platform. Existing functioning resources are retained until an explicitly tested successor achieves parity. We will not delete/rewrite servers, discard MariaDB data, remove txAdmin/baseevents/chat/pma-voice/oxmysql prematurely, or declare unfinished domains operational.
ws_core contains contracts and shared validation, not gameplay state. ws_world owns geographic identity, not terrain rendering, routing, weather or economy.server.cfg, grants, installed manifests, exports, data schemas, hashes and dependencies are audited before changes.flowchart TB
U[Players / Input / NUI / Gamepad / PXN Wheel] --> C[Presentation and Client Adapters]
C --> G[Server Authorization / Contract Validation]
G --> F[Foundation: ws_core + ws_events + ws_identity + ws_database adapter]
G --> D[Domain Authorities]
D --> W[Geography + Simulation]
D --> P[Population + Safety]
D --> V[Vehicles + Transport]
D --> E[Economy + Civilian Life]
D --> X[Communication + UI]
W --> DB[(MariaDB: durable state / transactions)]
P --> DB
V --> DB
E --> DB
D --> O[Read-only Diagnostics + Staff Auditing]
D --> R[Client Replication + LOD + Visual/Audio Effects]
R --> C
O --> S[ws_staff + Status/Discord/SHIN collector]
Service model: Native FiveM resources with strict Lua/JS exports/events and bounded state bags, not a separate microservice per gameplay function. Cross-resource calls occur through versioned contracts; periodic telemetry and cosmetic updates are bounded, sampled and proximity scoped. Databases and outside services are not reachable directly from untrusted clients. External bots and SHIN may observe configured feeds but do not gain unrestricted desktop/server authority.
| Plane | Goal | Components |
|---|---|---|
| Platform and lifecycle | Stable sessions, input authentication, durable persistence | ws_core, ws_events, ws_database candidate, ws_identity, ws_state, ws_spawn, ws_security |
| Territorial world | Nation, state/county/municipal registries, road/parcel identities | ws_world proposed, ws_coordinates, ws_navigations, map-stream resources |
| Environmental simulation | Time, climates, weather, exposure, fire, surface friction | ws_weather, ws_environment, ws_wind, ws_fire, ws_smoke, ws_explosions candidate |
| Mobility and vehicles | Physical vehicle authority, passengers, transport | ws_vehicle / ws_vehicle_ignition reconciliation, ws_vehicles, ws_commercial, ws_wheel, ws_physics, ws_trailers, ws_fuel, aviation and marine |
| Society and public safety | NPC population, commerce, incidents, laws, responder coordination | ws_npc, ws_traffic, ws_gameplay, ws_law, ws_dispatch, ws_cad candidate |
| Civilian economy | Currency ledger, employers, businesses, work, property, items | ws_economy, ws_store, proposed employment/business/work/property/inventory subsystems |
| Experience | Interaction, visible maps, HUDs, audio, phone, chat, voice and visuals | ws_interaction, ws_map, ws_minimap, ws_dashboard, ws_mainmenu, ws_chat, ws_voice, radio, phone, fgvo, fcgvo, ws_audio |
| Operations | Staff platform, permissions, quality gates, telemetry, recovery | ws_staff, ws_security, ws_status, ws_presence, bot, proposed shared diagnostics reader |
request_id, schema version, actor and character IDs, target IDs, creation times, authorization context and source evidence; do not trust client-provided monetary amounts or job completion.ws_core — only shared type validation, contracts/version checking, service discovery, error/result conventions, correlation IDs, transition guards and lifecycle helpers. No all-powerful core manager, no central item/job/money/vehicle state.
ws_database (planned) — compatibility access layer for MariaDB; oxmysql remains present until functional parity, load tests, transaction rollback, code search and recovery succeed. Parameterized statements, migrations with checksums, unique IDs, transaction retries only for retry-safe operations, schema versioning and tested backups. High-rate transient positions do not write per tick to MariaDB.
ws_events — stable lifecycle provider for joined, authenticated, selected character, ped spawned, death, disconnect and resource recovery. Preserve stock baseevents during parity; the event bridge must avoid double emission and late-join state races.
ws_security — server authorization, anti-cheat signals, incident attribution, rate limits, replay protection and defensive policy. Cannot directly manufacture staff rank. Separate detection from sanction, support appeal/evidence and controlled false-positive testing.
Character sequence: ws_loading → ws_identity → ws_character → ws_spawn; ws_state checkpoints only authorized committed per-character state; clothing preview is never a durable appearance commit; reconnect restores valid saved coordinates, clothing, fuel references and accepted state. ws_clothes, ws_vest, ws_armor build on character canonical appearance/accessories, not parallel character databases.
| Data category | Durable authority | Replication / failure |
|---|---|---|
| Accounts and characters | ws_identity and ws_character coordinated with DB |
Hard identity check on every privileged event; stale session rejected |
| Spawn, last position, equipment snapshot | ws_state + domain-specific item owners |
Checkpoint transaction with revision / safe fallback spawn |
| World names, boundaries, road and address IDs | ws_world registry |
Immutable IDs; versioned read-only client subsets |
| Spatial road graph | ws_coordinates / asset registry |
Versioned tile graph; topology check on loaded sector |
| Money, debt, company receivables | ws_economy |
Double-entry journal, idempotent payment settlement |
| NPC incident and managed patrols | ws_npc, ws_dispatch respectively |
OneSync owner migration + restart recovery, no duplicate units |
| Vehicle condition, ownership, fuel | Appropriate vehicle/fuel owners | Versioned entity state with persistence; stale/fault differentiated |
| Weather, fire, surface exposure | Domain environmental owners | Region-scoped authoritative snapshots; client visuals derived |
The 12-state layout supersedes earlier seven-state schemes. Approved geographic labels: Glacemere, Northreach, Highplain, Eastmark, Merrow Coast, Crownheart, Riverland, Sunridge, Stoneway, Tidehold, Southwatch, Seabreak Isles. Individual borders, county names, exact municipal boundaries, state capitals and highway alignments are still survey/modeling tasks, rather than image-certified geometries. The atlas is a design reference, not a georeferenced raster, a collision mesh or GTA-compatible navigable level.
ws_world data: nation_id, state_id, county_id, municipality_id, settlement_id, address_id, road_id, district_id, climate_zone_id, service_area_id, stable geometry refs, adjacent borders, effective-date schema versions and approved aliases. Store physical geography in separate terrain/mesh/vector databases, never all inside ws_world Lua code.
ws_world: names, codes, jurisdiction identities and place metadata.ws_coordinates: coordinates, elevation sampling, containment and road/lane topology. Define transform precision; never assume GTA native road graph extends automatically to brand-new terrain.ws_navigations: routing, driving directions, truck clearance/weight constraints, public-sector vehicle routing and ETA using road graph/time costs rather than straight lines.ws_map / ws_minimap: separate photorealistic satellite base layers from political, traffic and weather overlays; accurate player marker, tile/zoom calibration, route display; no duplicate minimap.| Layer | Data | Streaming principle |
|---|---|---|
| Sector HD | Nearby streets, signs, structures, intersections, building interiors | Standard native scoped detail/collision, subject to profiled caps |
| District mid | Neighborhood silhouettes, grouped vegetation, industrial blocks | Reduced meshes/materials and time-of-day-aware swaps |
| Regional far | Broad skylines, mountains, horizon features | Proxy meshes, SLOD and constrained materials |
| National view | Multi-zoom map atlas tiles and vector overlays | Not live 3D terrain displayed at full detail |
| Remote/offline | Cities and states outside relevance | No detailed client entities; persistence via durable records/aggregate simulation |
Feasibility warning: The ~235-mile Southport-to-Northgate corridor and 45–60-minute per-state crossing are not verified engine capabilities. No LOD design alone proves floating-point precision, AI path graphs, map extents, collision streaming, water behavior or physics synchronization on a national-size continuous terrain. EDP must validate increasing corridor lengths and coordinate-extreme road traversal before constructing all states. Benchmark on the target QsTower hardware as well as an additional typical client; avoid designing only for high-end GPUs.
Road hierarchy: national interstates, state highways, regionally divided roads, metropolitan ring roads, suburban arterials, industrial truck routes, local streets, rural roads, service alleys, signed passes and ferry links. Each metropolitan region has practical urban density (blocks, neighborhoods, service access), not a symbolic dot. Create a major-city classification with two-city or multi-core metropolitan areas, multi-county conurbations, realistic suburban gradients and industrial buffers.
Preserved user reference route: Southport → Red Willow → Greenfield → Coldwater. Northgate is a farther northern destination in Glacemere, reached by an explicitly surveyed continuation; do not silently place Coldwater and Northgate at the same location. Road ETA is computed from measured road distance, speed profiles, grades, turns, congestion and seasonal conditions only after route graph acceptance. Cross-state pursuits must preserve callouts, dispatch handoff and vehicle networking, not force arbitrary jurisdiction resets.
ws_weather is forecast and precipitation authority; ws_environment is road/surface wetness, accumulated snow, shade/cover, ambient exposure and hydrological state; ws_wind owns vectors and gusts; ws_fire owns ignition, fuel, spread and suppression; ws_smoke owns smoke transport/decay; ws_explosions is a candidate coordinating bounded effects. FGVO is visual only. Avoid graphics resources inventing rain/fuel or fire facts.
Geography-driven regional climate uses latitude analog, elevation, coastline, ocean influence, terrain shelter, season, fronts and local rain shadows. North can experience long snowy winters, south hotter seasonal climate; never force a sharp weather seam along political boundaries. Roof cover is a geometry/occlusion exposure input—pumps under shelter must not simply render vehicle wetness/surface rain as if uncovered. Regional time/weather data replicated by bounded areas and smoothed at transitions.
Fire/smoke uses server incident cells + client visual emitters with safety caps, tested windward propagation and recovery. Client LOD only affects visuals; it must not delete the authoritative fire state. Seasonal traction inputs influence ws_physics without double-applying GTA traction modifiers.
ws_vehicle design had cross-category profile exports, but recent user input reports transition to ws_vehicle_ignition; the installed resource's actual role/exports must be inspected before making a final rename. Do not pretend exports.ws_vehicle:RegisterProfile exists: ws_vehicles/server/main.lua:12 previously failed on that missing export. Provide a transition shim only after verified source audits.ws_vehicles / ws_motorcycle candidate / ws_commercial: category-specific behavior and vehicle-class profiles.ws_physics: authoritative custom traction/engine/brake response layer where technically proven; v7 read-only/shadow logic is not an active physics override. Inputs include mass, occupants, cargo, environment, tires, gearbox, brakes, damage and engine family.ws_wheel: existing PXN V9 Gen2 device mapping/input remains until audited; wheel contact/traction duties from older records require explicit disambiguation before splitting. All wheel/control profiles preserved; ws_input is a candidate for generalized device/control routing, not asserted installed.ws_trailers: trailer identities, attach/detach, landing gear, fifth wheel, collisions, tow mass, replicated ownership and safety limits. Experimental ws_trailer_trial retires only after parity.ws_fuel: quantity, type, flow, delivery, burn, pump targeting, authorization, transactions; fixed real stations, pump Third Eye targeting, engine off/vehicle exited, no false refuel. Missing fuel data = fault, not empty. Catalog must fail explicitly if undefined.ws_dashboard: display-only vehicle cluster determined by real make/model/generation/trim, functional turbo indicator only if actual profile includes one; special reference-accurate marine/aero/commercial dashboards.ws_plane, ws_helicopter, ws_boats candidate: specialized controls and vehicle categories; flight/marine mechanics and UI do not fork universal fuel/vehicle identity.ws_emergency candidate: lights, sirens and specialized equipment role; no duplicate full vehicle mechanics.Input hardware → normalized throttle/brake/clutch/steering and shift intents → vehicle permission/ignition → chosen vehicle/engine/transmission authority → physics actuation (when tested) → authoritative telemetry → dashboards/audio/third-eye. A controller mismatch cannot grant physics authority. Shift constraints support clutch, 6-/12-/18-speed selectable gearing and real drivetrain differences, with credible braking and trailer weight transfer. Controller interfaces must include keyboard/gamepad fallback.
Physical tests require instrumented road/tire/temperature/load conditions: stopping distance, truck acceleration, hill climb, air-brake delay, clutch slipping, engine governor, trailer jackknife, ownership migration and two-player perception. Shadow telemetry and fake projected acceleration cannot substitute for measured movement.
ws_npc: managed actor lifecycle and NPC behavior policy, with native GTA fallback when enhancement cannot safely control actors. ws_npc_guard: independent watchdog/status agent; either kept independently or merged only after failure-detection parity. ws_traffic: traffic generation/behavior, lane choice, intersections, parking and congestion using verified ws_coordinates road graph and ws_navigations route plans. Read-only v0.1.0 observer is not proof of AI control. Fix parking-lot wandering with road-access classification, appropriate nav task endpoints and fallback handling—don't just increase scan rates.
ws_law: in-universe laws, codes, offense catalog, jurisdiction rules and policy effective dates. It is not a synonym for NPC officers. ws_dispatch: incidents, calls, responders, assignments, triage, escalation, handoffs and unit status. ws_gameplay: shared scene/interactions policy only, not a catch-all replacing NPC/law/dispatch. ws_cad/MDT candidate: presentation + authenticated records and queries. Officer/EMS/fire agency authorities remain policy-configurable; do not invent constitutional institutions before USI government decisions.
Incident lifecycle: citizen call/sensor → ws_dispatch incident ID → jurisdiction via ws_world → routing via ws_navigations → closest capable unit (player or managed NPC) → scene reservation → actions and law entries → close/cancel → immutable audit. Test cross-state pursuit/handoff, civilian vs NPC incidents, absence of real players, repeat calls, unit death/disconnect and restart recovery.
Civilian-first systems remain a core architectural requirement. ws_economy owns fixed-rate policy, currency, account balances, double-entry ledger, taxes/fees policy and transactions. ws_store owns point-of-sale stock/carts/supply chain; no resource may addMoney or deduct cash without a transaction receipt from economy.
Proposal modules/resources, created only after live-inventory/name collision review:
ws_employment): agreements, qualifications, licenses, rosters, clock-in, historical positions.ws_business): company entity, establishments, ownership, access control, employees and finances as a projection (actual cash under economy).ws_work): verified work orders, delivery legs, service calls, repair/construction/agricultural jobs and industry task adapters.ws_properties candidate): housing, tenancies, warehouses, commercial facilities, addresses and access, without copying world parcels.ws_inventory candidate): custodial items/transfer receipts/durability; police evidence, commerce and vehicle storage consume a single item service.ws_logistics candidate): freight manifests, custody, depot stock, shipment routing, insurance claims. Truck physics and trailer coupling stay in transport owners.ws_utilities candidate): water, power, sewer, heating, telecom and billing states where simulation is justified; do not spawn mandatory background ticks for empty distant regions.Population and business activity should be distributed across all 12 states; geography provides location and regional conditions, economy provides prices, industries provide work. Independent contracts, part-time and multiple-job employment allowed within explicit conflict/policy rules. Real elapsed time is the pay basis; contract verification prevents repeat payouts. The earlier employment-only platform spec becomes a subsystem design under this complete architecture, not the umbrella architecture itself.
An empty server still supports limited NPC or system-operated businesses; player employers can recruit, operate and respond to supply/demand in-world. Simulated economic statistics for unloaded regions run coarse-grained, deterministic aggregate updates instead of spawning thousands of persistent NPCs.
ws_interaction: primary physical context/action surface. Registered actions require range, line-of-sight, entity role, network owner and server authorization. Raycast and NUI readiness exposed to diagnostics.ws_chat: RP character display names, proximity and channel rules, suggestions, NUI cursor support, filtering of console-only F8 output, staff/txAdmin passthrough. Legacy chat remains until migration parity.ws_voice: speech transport abstraction and health; actual pma-voice remains the installed provider until verified replacement. ws_radio and ws_phone are distinct voice/session/routing domains; phone calls never automatically join radio channels.ws_map: separate satellite imagery, vector navigation, addresses, overlay layers and city detail. ws_minimap: exactly one anchored minimap; calibrated geo transform, no unnecessary player-arrow circle, appropriate collision with dashboard safe area.ws_mainmenu, ws_loading, ws_character, ws_clothes: cohesive first-party design language with independent workflow ownership, protected NUI focus, configurable input and no black-screen overlays on startup/failure.ws_audio: canonical acoustic system for engine, firearm, collisions, sirens, occlusion and region soundscapes. Retire the older ws_weapon_audio only after verifying wavepack registration, multiplayer hearing, sustain fire, pistol mapping and fallback audio.UI should use read models and clearly show stale/unknown data (e.g., fuel health unavailable, connection provider_disconnected), rather than silently asserting real state.
fgvo is a single resource with internal performance, materials, lighting, atmospheric, vegetation, postprocessing, maps and diagnostics modules. FGVO:Performance is a module—not an invented second server resource. fcgvo remains separately evaluated client-only capability, taking account of FiveM Legacy plugin/graphics restrictions. GVOFU (when used) is the updater/delivery mechanism, never an authoritative weather/physics simulation.
Visual hierarchy: asset-level LOD + GPU-conscious materials/shaders + FGVO effects budgeting + weather-driven appearance + distance-scaled audio + optional client-side effects. Server authoritative facts are passed via contracts; no client shader decides road friction, fuel delivery or fire damage. Implement A/B benchmarks for rain, snow, wet vehicles (including covered pumps), photorealistic map, road textures, lens flare, reflective surfaces and NPC density. On low-end systems, dynamically degrade nonessential effects rather than terrain collision or authoritative simulations.
No claim that this can surpass GTA VI rendering or that a 235-mile region is playable has been proven. Visual acceptance must be judged through in-game screenshots, performance logs and realistic road/city reference fixtures.
ws_staff is the single first-party authority for staff operations and the planned txAdmin parity target. Existing ws_admin, ws_access, ws_moderation, ws_monitor are proposed internal modules under ws_staff unless a proven operational requirement warrants separate independent resources; avoid duplicate permission authority. Staff access uses ACE + explicitly verified account/license/Discord bindings, least privilege, dual confirmation for high-impact actions, tamper-evident audit, command provenance and emergency recovery. An ACL status showing member should point to specific failed grants without leaking secrets.
Do not disable txAdmin until a full replacement is operational and proven, including server start/stop/restart, safe console, scheduled maintenance, player moderation, logging, crashes, permissions, audit, rollback and out-of-band recovery. Maintain a documented break-glass management route not dependent on a broken in-game UI.
ws_status publishes sanitized server health; ws_presence reports player presence/Discord rich presence; WorldStead bot handles status cards and community commands under explicit token scoping. External collectors and SHIN read-only outbound link can ingest signed sanitized diagnostics, but source modifications require separate authorized deployment channel. Distinguish “job receipt HTTP 202” from proof that UI/collector stored and displayed the event.
Diagnostics: a lightweight ws_diagnostics reader/aggregator candidate may publish standardized status/error codes and health probes without taking ownership of gameplay or duplicating ws_staff monitoring. Domain modules self-report faults; diagnostics merely aggregates and exports. Error classification: AUTH, DB, IDENTITY, WORLD, SPATIAL, AI, VEH, FUEL, UI, NUI, NET, AUDIO, VIS, OPS with source resource, severity, timestamp, trace ID, latest good sample and remediation hint. Never stream authentication tokens, private Discord credentials or full player secrets to telemetry.
{
"schema": "ws.contract.v1",
"event_id": "unique-event-or-request-id",
"correlation_id": "end-to-end-trace-id",
"producer": "ws_fuel",
"event_type": "fuel.tank.updated",
"occurred_at_unix_ms": 0,
"subject": {"vehicle_id": "stable-id", "character_id": "optional-id"},
"subject_revision": 17,
"payload": {"liters": 45.2, "fuel_type": "diesel", "quality": "fresh"}
}
Contract rules: exported names are versioned and real (validated at boot), all mutating events are authenticated, all requests are deduplicated, client-originated prices/coordinates/ranks are treated as claims to validate, event cadence is bounded and back-pressure has a policy. fxmanifest.lua declares actual dependencies and supported asset metadata; avoid circular dependency rings by using deferred readiness and clearly published provider APIs.
Example payment flow: verified delivery ws_work → signed completion receipt → ws_economy atomic transaction + idempotency key → ledger record → notification. On failure, mark work settlement_pending; do not silently regenerate money. Example refuel flow: third-eye pump intent → validated pump/site/station/ignition state → fuel reservation + economy hold → metered fuel transfer → invoice settlement and durable tank update; compensate or cancel on partial failure.
Every public API must define: allowed caller context, server/client authority, request schema, result schema, missing dependency behavior, timeouts, retryability, idempotency, restart replay and metrics. Consumers that lose a provider display degraded/unavailable state; they must not silently use zero fuel, zero balance, no laws or default owner authorization.
WorldsteadCore.base/
server.cfg # existing authoritative config; patch incrementally only
resources/
[worldstead]/
[00_foundation]/ # ws_core, ws_events, ws_security, ws_database adapter
[01_lifecycle]/ # ws_loading, ws_identity, ws_character, ws_spawn, ws_state, ws_clothes
[02_geography]/ # ws_world, ws_coordinates, ws_navigations, ws_map, ws_minimap
[03_environment]/ # ws_weather, ws_environment, ws_wind, ws_fire, ws_smoke
[04_simulation]/ # ws_npc, ws_npc_guard, ws_traffic, ws_gameplay
[05_vehicles]/ # current audited ws_vehicle/ignition mapping, ws_vehicles,
# ws_commercial, ws_physics, ws_wheel, ws_trailers,
# ws_fuel, ws_dashboard, ws_plane, ws_helicopter
[06_society]/ # ws_law, ws_dispatch, ws_cad candidate, civic/economy/work
[07_communications]/ # ws_voice, ws_radio, ws_phone, ws_chat, ws_audio
[08_ui]/ # ws_interaction, ws_mainmenu
[09_operations]/ # ws_staff, ws_status, ws_presence, diagnostic observer
[10_visuals]/ # fgvo (single modular resource)
[11_content]/ # geography sector streaming: terrain, roads, props, LOD
[legacy_compat]/ # controlled tested provider adapters until full cutover
[third_party]/ # pma-voice, oxmysql, txAdmin etc. as deployed
worldstead-source/ # offline authoring, tests, migration scripts, manifests
contracts/
geo/ # state/county/road/route datasets
schemas/
tests/
deployments/
evidence/
rollback/
Important: This is a target repository layout, not the current folder tree and not instruction to move live FiveM resource directories. Bracket-group behavior and ensure globs need testing; deployment may preserve present resource paths while introducing equivalent source organization via build/install scripts.
Suggested order, subject to real manifests: database provider → foundation/contracts → identity/security/lifecycle → geography/spatial services → environment owners → vehicle/physics/fuel → NPC/traffic/public safety → economy/business/work → interactive UI/audio/communications → visuals and status/operations projections.
Not all resources should hard-depend on all preceding phases: define hard dependencies narrowly, use optional capabilities for marine/aviation and future employers, and ensure a provider outage exposes degraded read mode rather than cascading resource stop. Avoid starting client NUI before identity handoff grants required data.
Provision health at three levels: resource_started, domain_ready, gameplay_verified. A successfully started resource with a missing export or a dead server callback is not domain-ready. Long-lived telemetry uses service IDs and source hashes so cached diagnostics cannot masquerade as a current deployment.
| Stage | Goal | Technical exit gate | Rollback |
|---|---|---|---|
| 0. Immutable baseline | Capture ZAP server resources, CFG, database schema, manifests, permissions, versions, asset hashes and dependencies | Complete source/DB backups and hash report | Do not modify live |
| 1. Reconciliation | Compare 60-track Oct20 inventory with actual Oct23 resources, fixes and archives | Each installed package mapped to a named authority and current export list | No live changes |
| 2. Contracts | Introduce versioned, read-only shared schemas and health probes | No missing exports, duplicate domain writers or event collision | Remove adapters only |
| 3. Safety and persistence | Character reconnect, ACE staff, transaction semantics, event guards | Two-client and restart tests passed | Restore known configs and backed-up schema |
| 4. Spatial and world dataset | 12-state registry, road graph prototypes, coordinate proof | Same route ETA reproducible; collision/coordinate limits proven | Disable new sectors |
| 5. Vehicle and environment integration | Confirm ignition naming, physics authority, fuel, weather, wind and dashboard | Live driving matrix + fault injection + fallback | Feature flags back to native |
| 6. NPC and public safety | Traffic pilot, law-code data, dispatch workflows | Parking/junction/2-client/pursuit tests pass | Native NPC fallback |
| 7. Economy and civilian life | Money ledger, store, businesses, jobs, housing/logistics | Idempotent pay, inventory custody, quit/rejoin tests | Isolated ledger reversal and DB restore plan |
| 8. UX, visuals and audio | UI design, maps/minimap, FGVO optimization, voice/chat, weapons | Performance and client compatibility tests pass | Per-feature visual/audio rollback |
| 9. Operations handoff | Full staff moderation/supervision parity and Discord integrations | txAdmin parity and out-of-band recovery observed | Keep legacy admin available |
| 10. Release | Cross-domain peak-load, disaster and security tests | EDP release report, signoff and restore rehearsal | Versioned release rollback |
No phase is considered accepted merely because a source file is present, a command responds, or the UI shows a green status.
RegisterProfile mismatch and ignition role before writing new consumers.ws_fuel nil WSFuelCatalog, then test authoritative catalog load, pump targeting, engine-off enforcement, payment atomicity and stale telemetry.ws_physics v7 outputs separately from real handling changes; Phantom acceleration and truck brake timing need controlled measurement.ws_dispatch command nonresponse and prove dispatch/managed-officer lifecycle rather than just resource start.ws_traffic from observing to actual safe control; address NPC parking-lot behavior and player interference.ws_map / ws_minimap geotransform accuracy, remove duplicate minimap and user-unwanted marker decorations.ws_staff ACE grants after repaired authorization, then build rather than assume full txAdmin replacement.No national-scale map declared feasible from an illustration. No oxmysql retirement before DB parity. No txAdmin retirement before infrastructure recovery parity. No stock baseevents/chat removal before full behavioral parity. No working resource renamed in place without mapping all imports/exports and CFG; no weapon audio replacement assumed based only on mounting a wavepack; no physics authority claimed from shadow output.
Retained: the 18 project-control decisions from the October 20 record (appendix), except newer owner instructions take precedence after verified reconciliation. Newly proposed decisions:
ARCH-01: National 12-state terrain is constructed and validated through geospatial sectors with native LOD/SLOD, not drawn only on atlas.ARCH-02: ws_world is identity/territory authority; spatial/route/asset ownership stays separate.ARCH-03: All gameplay state changes are server-authoritative; temporary read models do not become canonical storage.ARCH-04: Build a domain registry and compatibility adapters before renaming/deleting live resources.ARCH-05: Current installed ws_vehicle / ws_vehicle_ignition and wheel/input boundaries must be inspected before resource renaming.ARCH-06: Staff administrative modules consolidate under ws_staff pending operational evidence; no parallel staff permissions engine.ARCH-07: Detailed sector simulation follows player relevance; remote economies and populations may run bounded aggregate updates, not networked NPC fleets.ARCH-08: FiveM physical scale and performance are acceptance gates; no greenlighting 235-mile corridors based on LOD projections alone.ARCH-09: Jobs, businesses, work, inventory and property belong to Society/Economy plane; the earlier employment architecture is a subordinate proposal.ARCH-10: FGVO:Performance remains internal to a single fgvo resource; never spawn another competing visual authority.These ARCH-* labels are proposed architecture decisions, not proof of being written to the owner's live project tracker or server.
ensure list with physical resource folders; record hash, version, fxmanifest metadata, Lua/JS exported names and client/server scripts.exports.*, RegisterNetEvent/AddEventHandler, state keys and SQL table usage. Flag undefined RegisterProfile, duplicate vehicle/fuel/wind/character owners and stale hard-coded resource names.The architecture redesign is ready for review; code migration remains dependent on a fresh audit of installed server resources and explicit deployment authority. It would be misleading to label all 60 historical resources "rebuilt" without reading and testing the current installation.
This inventory is a starting point, not a source of current version truth. Reported active, Offline tested and Live behavior confirmed are the workbook's dated categories, not a universal health assertion. Recent notes beneath individual entries reflect user reports, not inspected files.
| ID | Resource/component | Role | Oct20 evidence | Redesign disposition |
|---|---|---|---|---|
CORE-01 |
ws_core | Logic foundation | Reported active | Retain and reconcile current installed source |
CORE-02 |
ws_database | Database transport & transactions | Design / planned | Adapter migration; oxmysql stays until parity |
CORE-03 |
ws_security | Incident/security authority | Offline tested | Retain and reconcile current installed source |
CORE-04 |
ws_events | Lifecycle observation | Offline tested | Retain and reconcile current installed source |
OPS-01 |
ws_status | Status publisher | Live behavior confirmed | Retain and reconcile current installed source |
OPS-02 |
ws_presence | Presence reporter | Live behavior confirmed | Retain and reconcile current installed source |
OPS-03 |
WorldStead Discord Bot | External integration | Live behavior confirmed | Retain and reconcile current installed source |
OPS-04 |
ws_page | Scope to define | Reported active | Retain and reconcile current installed source |
OPS-05 |
ws_staff | Staff operations | Reported active | Retain and reconcile current installed source |
OPS-06 |
ws_admin | Proposed auxiliary module | Design / planned | Fold proposed functions into ws_staff modules after scope audit |
OPS-07 |
ws_access | Proposed auxiliary module | Design / planned | Fold proposed functions into ws_staff modules after scope audit |
OPS-08 |
ws_moderation | Proposed auxiliary module | Design / planned | Fold proposed functions into ws_staff modules after scope audit |
OPS-09 |
ws_monitor | Proposed auxiliary module | Design / planned | Fold proposed functions into ws_staff modules after scope audit |
ONB-01 |
ws_identity | Identity authority | Reported active | Retain and reconcile current installed source |
ONB-02 |
ws_character | Character lifecycle | Reported active | Retain and reconcile current installed source |
ONB-03 |
ws_state | State persistence | Reported active | Retain and reconcile current installed source |
ONB-04 |
ws_spawn | Spawn authority | Reported active | Retain and reconcile current installed source |
ONB-05 |
ws_loading | Loading experience | Live behavior confirmed | Retain and reconcile current installed source |
ONB-06 |
ws_clothes | Clothing interaction | Offline tested | Retain and reconcile current installed source |
UI-01 |
ws_interaction | Interaction interface | Reported active | Retain and reconcile current installed source |
UI-02 |
ws_mainmenu | Menu/UI | Design / planned | Design only; do not invent deployment |
UI-03 |
chat (custom legacy) | Legacy chat transport | Live behavior confirmed | Compatibility baseline until ws_chat accepts commands/RP |
UI-04 |
ws_chat | Chat provider | Offline tested | Retain and reconcile current installed source |
COM-01 |
ws_voice | Voice foundation | Reported active | Retain and reconcile current installed source |
COM-02 |
ws_radio | Radio domain | Design / planned | Design only; do not invent deployment |
COM-03 |
ws_phone | Telephone domain | Design / planned | Design only; do not invent deployment |
AI-01 |
ws_npc | NPC behavior authority | Offline tested | Retain and reconcile current installed source |
AI-02 |
ws_npc_guard | Guard/watchdog | Reported active | Retain and reconcile current installed source |
AI-03 |
ws_coordinates | Spatial facts provider | Design / planned | Design only; do not invent deployment |
AI-04 |
ws_navigations | Path / route authority | Design / planned | Design only; do not invent deployment |
AI-05 |
ws_traffic | Traffic simulation | Design / planned | Design only; do not invent deployment |
AI-06 |
ws_dispatch | Dispatch domain | Offline tested | Retain and reconcile current installed source |
AI-07 |
ws_gameplay | Gameplay scene rules | Offline tested | Retain and reconcile current installed source |
AI-08 |
ws_law | Law domain | Live behavior confirmed | Retain and reconcile current installed source |
AI-09 |
ws_cad | CAD domain (candidate) | Design / planned | Design only; do not invent deployment |
VEH-01 |
ws_vehicle | Universal vehicle contracts | Offline tested | High-risk naming/ignition reconciliation; audit exports before migration |
VEH-02 |
ws_vehicles | Road vehicles | Offline tested | Retain and reconcile current installed source |
VEH-03 |
ws_commercial | Heavy-vehicle domain | Offline tested | Retain and reconcile current installed source |
VEH-04 |
ws_motorcycle | Proposed vehicle category | Design / planned | Design only; do not invent deployment |
VEH-05 |
ws_wheel | Wheel-state provider | Reported active | Retain and reconcile current installed source |
VEH-06 |
ws_physics | Physical simulation | Offline tested | Retain and reconcile current installed source |
VEH-07 |
ws_trailers | Trailer domain | Offline tested | Retain and reconcile current installed source |
VEH-08 |
ws_trailer_trial | Legacy experiment | Reported active | Migration candidate; retain until ws_trailers parity |
VEH-09 |
ws_plane | Aircraft authority | Offline tested | Retain and reconcile current installed source |
VEH-10 |
ws_helicopter | Rotorcraft authority | Offline tested | Retain and reconcile current installed source |
VEH-11 |
ws_boats | Marine domain | Design / planned | Design only; do not invent deployment |
VEH-12 |
ws_emergency | Equipment / role layer | Design / planned | Design only; do not invent deployment |
VEH-13 |
ws_fuel | Fuel simulation authority | Reported active | Retain and reconcile current installed source |
VEH-14 |
ws_dashboard | Read-only instrumentation | Reported active | Retain and reconcile current installed source |
WORLD-01 |
ws_weather | Weather authority | Reported active | Retain and reconcile current installed source |
WORLD-02 |
ws_environment | Environment authority | Reported active | Retain and reconcile current installed source |
WORLD-03 |
ws_wind | Wind authority | Reported active | Retain and reconcile current installed source |
WORLD-04 |
ws_smoke | Smoke authority | Reported active | Retain and reconcile current installed source |
WORLD-05 |
ws_fire | Fire authority | Offline tested | Retain and reconcile current installed source |
WORLD-06 |
ws_explosions | Explosion domain | Design / planned | Design only; do not invent deployment |
VIS-01 |
fgvo | Visual presentation | Reported active | Single modular visual resource; current build audit |
VIS-02 |
fcgvo | Client visual stack | Design / planned | Design only; do not invent deployment |
VIS-03 |
ws_audio | Audio playback/mapping | Reported active | Retain and reconcile current installed source |
ECON-01 |
ws_economy | Economy authority | Design / planned | Design only; do not invent deployment |
ECON-02 |
ws_store | Retail domain | Design / planned | Design only; do not invent deployment |
fxmanifest.lua manifest and dependencies: https://docs.fivem.net/docs/scripting-reference/resource-manifest/The full technical migration path is constrained by the real installed resource graph. All named additions not present in the existing 60-resource workbook are candidates, not asserted files.