A frontier proposal with a validation plan, not an implemented detector.
Intended capability
Research whether the field could support this proposed outcome: Platform-edge crowd density bands and boarding-surge pulses per train arrival — feeds headway decisions and platform-edge staffing without station cameras' privacy burden.
This describes the intended outcome. Readiness is research concept, evidence is class C, and a catalog mapping or recording is not proof of this outcome at a real site.
Solution blueprint
See the environment before installing it.
This exact kit is one of 191 first-class designs. It includes geometry, objects, nodes, wording, scenarios, installation, limitations, and catalog-bound readiness.
No rendered revision is available yet.
Bundled recording
A related Frontier scene
This is one recorded vertical scenario. It is not separate validation of every capability in the catalog.
01 The physics
Platform occupancy scales aggregate perturbation (r=0.9 lineage); train arrival creates a characteristic surge signature (mass coherent motion toward doors — a brief high-energy directional band pulse) that segments the timeline into dwell/board cycles automatically.
02 Shared processing path
Eigen-mode crowd_index banded per platform segment -> arrival-surge detector from the coherent motion pulse -> per-cycle boarding-load estimate + inter-arrival density accumulation rate.
This is a capability design path. Components may be shared with other catalog entries; it is not presented as a unique algorithm.
03 Validation plan
Own-hardware pilot on one platform vs automatic passenger counting (APC) on trains; report band accuracy per segment and surge-detection alignment with door-open telemetry.
04 Commercial hypothesis
For the operator: 'Live platform-load truth per segment, cheap enough for every station — not just the flagship ones with camera analytics.'