Atamyuz Navigator

Atamyuz Alaley

Atamyuz Navigator

Data Health

Adminpilotcpanel · 20260704-0143

Modules

Admin modules

Open the right workspace instead of crowding Map Studio.

Core workspaces

FacilitiesVenues, buildings, floors Map StudioVisual floorplan editing

Map object managers

DestinationsPOIs, categories, searchable visitor stops ZonesRooms, corridors, departments, tracking areas BarriersWalls, blocked lines, route constraints Route NetworkPath repair, route authority Device RegistryQR starts and detected devices

Platform administration

Journey OperationsLive trips, cohorts, incidents, rerouting Control AnalyticsHeatmaps, KPIs, pressure, confidence Field TestingQR walks, signal calibration, route acceptance Publish CenterValidation gates and release history IntegrationsAPI bridge, mobile contracts, security Data HealthBackend mode, MySQL readiness, stale records Users & AccessAdmins, staff, roles, scopes

Next modules

3D Maps2.5D floors, extrusions, and landmark view

JSON Health MySQL State

Atamyuz Navigator

Data Health

Audit the platform source of truth, MySQL readiness, stale references, and pilot/demo storage before going deeper into production use.

Data Backend

demo

pilot JSON store

MySQL

not configured

missing 4

State Repo

missing

not exported

Consistency

clean

0 warnings

Storage

local

memory realtime

Source Of Truth

This explains whether the platform is using pilot JSON, in-memory test data, or a configured MySQL backbone.

pilot mode

Requested backend

demo

Active backend

demo

App root

/home/higherat/atamyuz-navigator

Data root

/home/higherat/atamyuz-navigator/.local-data

JSON store

/home/higherat/atamyuz-navigator/.local-data/demo-store.json

Store persisted

yes

Data version

Current store hash

1235c78ed248

Live Data Consistency

Deleted venues, stale POIs, orphan route links, and duplicate records are detected here before they confuse Map Studio or mobile.

clean

Venues

Floors

POIs

Zones

Devices

Journeys

No stale references or duplicate IDs were found in the current store.

MySQL Readiness

MySQL is the practical next production database path on cPanel. This first bridge stores one clean platform snapshot before we migrate each module into normalized tables.

Configured

Connection

not checked

State table

missing

Stored snapshot

missing

Current hash

1235c78ed248

Stored hash

none

Host

not set

Database

not set

User

not set

SSL

Missing env: MYSQL_HOST, MYSQL_DATABASE, MYSQL_USER, MYSQL_PASSWORD

State Transfer

Use these controlled API actions during deployment. Export requires a clean consistency report.

Export clean server state

POST /api/v1/admin/mysql-state/export

Import stored MySQL state

POST /api/v1/admin/mysql-state/import

Stored source

none

Stored updated

never

Warnings

Runtime is using the local JSON store. Use this for pilot/testing only, then migrate through the MySQL repository stage.

Floor assets are stored on the local app filesystem. Move to object storage before multi-server deployment.

Next Practical Action

Do not switch production to MySQL blindly.

First confirm consistency is clean, run `database/mysql/schema.sql`, export the clean server state to MySQL, then verify the stored hash matches. After that, we can migrate Facilities, Destinations, Devices, Users, and Journeys one module at a time.