Developer view
Endpoint diagnostics
Simulation only. Activity is observed at the existing adapter and validation boundary.
How the simulation flows
Architecture explanation — separate from observations below.
- Step 1: Stations / Geocode→ incident
- Step 2: Ranking→ chosen station
- Step 3: Start→ route initialization
- Step 4: Request→ in-process simulated ITS controller
- Step 5: Controller decision / reported state→ SSE
- Step 6: SSE→ validated telemetry
- Step 7: Validation / state→ Map and HUD
- Step 8: Stop→ terminal summary
ITS requests and feedback run inside the simulation process. They are not HTTP controller calls. Dataset quality describes the source dataset.
Observed in this browser session
Browser durations only. Repeated ticks are coalesced; counts show sampled activity. Bodies and endpoint queries are retained temporarily for JSON inspection in this browser only. Clear history removes them. Each tick is one simulated second, independent of playback speed. Several events can share a tick; tick numbers do not count messages.
- Stations
- Not observed
- Geocode
- Not observed
- Ranking
- Not observed
- Start
- Not observed
- Comparison start
- Not observed
- SSE
- Not observed
- Stop
- Not observed
- Dataset quality
- Not observed
- ITS · outgoing simulated request
- Not observed
- ITS · incoming controller feedback
- Not observed
Recent activity
- Not observed
Source data checksData quality
Loading data quality summary…
0 of at most 200 retained entries.