Coverage Ratio Trend (%)
Response Latency (sec)
TACTICAL TELEMETRY STABLE: 92.0% COVERAGE | 3.8s MEAN LATENCY
The canonical fixture assigns eight field agents and four detail teams with a five kilometer response radius. Eight divided by four is two field agents per detail on average, but the code does not assign teams equally or constrain simultaneous capacity. At thirty pixels per count field agents measure two hundred forty, teams one hundred twenty and that average sixty. Placement is randomized near fixed map coordinates. The dashboard is a geometric teaching simulation, not real personnel dispatch, security advice or a verified protection service. An agent is counted covered whenever at least one detail lies within the response radius. In a hypothetical eight-agent fixture, six covered means seventy five percent while eight covered means one hundred percent. At thirty pixels per agent the bars measure one hundred eighty, two hundred forty and uncovered two sixty. The coverage calculation ignores staffing contention, travel routes and multiple simultaneous incidents. Raising the threat threshold changes alert classification, not the distance condition for covered status. Initial ninety two percent displayed coverage is a seeded metric and should not be mistaken for a calculated random map result. The response estimate is the larger of one point two seconds and nearest distance in kilometers times zero point eight five. At one kilometer it stays one point two, at five it becomes four point two five, and at ten eight point five seconds. At thirty pixels per second the bars measure thirty six, one hundred twenty seven point five and two hundred fifty five. These are illustrative constants, not plausible measured city travel guarantees. Threat exposure adds random events during animation and charts begin with randomized history. Leaflet map initialization precedes all native control binding; when the library is blocked offline, controls and export remain inert and seeded telemetry stays visible.