// 05 // NETWORK LAYER //

Bandwidth-Disciplined Fleet Network

One shared realtime channel carrying GPS telemetry and social mapping, engineered so the cost per rider falls as the crowd grows.

Naive coordinate broadcasting costs the square of the crowd — everyone talks to everyone. StreetWizard attacks that cost by sending less, not by routing differently: riders share one realtime channel, and heavy identity travels through presence exactly once.

The position stream is then deliberately starved. Emission is gated on elapsed time AND distance moved, and both thresholds step up with fleet size — a convoy of twelve emits about twice a second, a swarm past two hundred backs off to once every four seconds. Density becomes an asset rather than a liability: bandwidth per rider falls as the crowd grows.

PRESENCE / STREAM SPLITADAPTIVE EMISSIONCLIENT-SIDE PREDICTION

EMISSION RATE

2/s → 1/4s

adaptive, by fleet size (param)

MARKER CAP

nearest vehicles drawn (param)

PREDICTION

1.4s

dead-reckoning horizon (param)

IDENTITY COST

once

avatar via presence, not per fix (param)

05.2 // CORE FEATURE

Global Community Odometer

GLOBAL COMMUNITY ODOMETER SERVER-SIDE AGGREGATE

,,KM

Every kilometer driven by every rider, ever, never reset. The client measures its own distance from the GPS trail and banks it against its own row; the community figure is a single privileged server-side aggregate over those rows. No client ever submits the total — the number on screen is a sum of what was actually driven.

MEASURED

ON DEVICE

AGGREGATED

SERVER-SIDE

ACTIVE DRIVERS

LIVE COUNT

05.3 // OBSERVABILITY

System Diagnostics & State Hydration

An automated bug reporting engine sits under the entire application. When an error boundary catches a failure it serializes what is needed to reproduce it — the failing view, the active route state and the current peer list — and packages it for the desk.

The report ships with the last stretch of raw GPS, because a navigation bug is rarely reproducible without the path that triggered it. Reports are routable to lead@seub.net, so a production crash reaches engineering while the drive it came from is still fresh.

[+] State snapshot on crash
[+] Recent GPS trail attached
[+] Failing view + route state
[+] Routed to the desk

/var/log/streetwizard/diagnostics.log SAT SYNC: NOMINAL

streetwizard@edge:~$ █