Apply privacy/legal review corrections and finalize verified metadata

This commit is contained in:
Noel Sabia committed 2026-11-14 08:50:32 +01:00
1 parent c1e2c96a63
commit 83b73367d8
6 files changed
+57 -49

No files matched your search

+11 -17
View File
@@ -1,9 +1,9 @@
# PulseCast: Turning a Noisy Footfall Index into a Weekly Staffing Plan
**Authors:** [AUTHOR TODO]
**Affiliation:** [AFFILIATION TODO]
**Author:** Noel Sabia (ORCID 0009-0008-3064-7573)
**Affiliation:** —
**Date:** 14 November 2026
**Artifact:** https://pulse.noelsabia.dev · **API:** https://api-pulse.noelsabia.dev · **Code:** [code repository TODO]
**Artifact:** https://pulse.noelsabia.dev · **API:** https://api-pulse.noelsabia.dev · **Code:** to be released after the hackathon
## Abstract
@@ -35,7 +35,7 @@ A code-level audit of the deployed Code for Heilbronn `lorax` firmware changes t
**The published value is therefore `0.7 × U`, where `U` is the number of distinct randomized BLE addresses seen in a ~10-second scan.** The 15-minute cadence is the sleep cycle, not the integration window. The effective duty cycle is about 1.1%. The firmware sets a 30-second scan duration, but the released code stops on the first 10-second report callback; the 30-second value is not enforced by the scanner [4].
The audit is of the public 2026 firmware; the deployed 2025 binary may differ, but the data are consistent with the 0.7 scaling. Every one of the 83,156 density values in the eight-sensor panel is an exact multiple of 0.7. The reconstructed integer count has median 12, p95 71, and a maximum of 418; 2.7% of readings are zero. The legacy `density-01` device reports integers on a 1.0 grid until March 2026, then a replacement device reports on the 0.7 grid from April 2026, with a 35.2-day gap between the two series. The two `density-01` series are not on the same scale and must not be pooled [5].
The audit is of the public 2026 firmware; the deployed 2025 binary may differ, but the data are consistent with the 0.7 scaling. Every one of the 83,156 density values in the eight-sensor panel is an exact multiple of 0.7. The reconstructed integer count has median 12, p95 71, and a maximum of 418; 2.7% of the 83,156 values reconstruct to `U = 0`. The legacy `density-01` device reports integers on a 1.0 grid until March 2026, then a replacement device reports on the 0.7 grid from April 2026, with a 35.2-day gap between the two series. The two `density-01` series are not on the same scale and must not be pooled [5].
This is a relative activity index, not a count of people. A person who passes in 30 seconds has roughly a 4.4% chance of overlapping a ~10-second scan; a person who lingers for an hour can be counted in up to four consecutive bins. The index conflates flow and dwell, and it cannot distinguish a phone from a smartwatch, earbud case, beacon, or car head-unit. Device penetration and the people-per-device ratio are unknown. The 0.7 factor is a provisioning default, not a validated penetration correction.
@@ -43,7 +43,7 @@ This is a relative activity index, not a count of people. A person who passes in
### 2.3 Coverage, gaps, and context
Coverage is uneven. Only 28.2% of 15-minute slots in the analysis panel have all eight sensors reporting; the modal count is seven. Aggregating to 30, 60, or 120 minutes raises complete coverage to 63.4%, 69.7%, and 71.0% [5]. About 5.2% of slots have all sensors at zero and 39.6% have all sensors below 5. The worst month falls to 23.3% coverage at one location. Gaps reach four to six days; the cause is undocumented, but missing periods differ systematically from full-coverage periods [2, 5]. Weather comes from Open-Meteo: historical archive for training, current/7-day forecast for the dashboard. Temperature and precipitation are the useful features; cloud and wind did not improve the short test. Baden-Württemberg holidays are a feature and badge; they added little and are context, not a large driver [2].
Coverage is uneven. Only 28.2% of 15-minute slots in the analysis panel have all eight sensors reporting; the modal count is seven. Aggregating to 30, 60, or 120 minutes raises complete coverage to 63.4%, 69.7%, and 71.0% [5]. Overall, 5.18% of individual density readings are zero and 39.6% are below 5. The worst month falls to 23.3% coverage at one location. Gaps reach four to six days; the cause is undocumented, but missing periods differ systematically from full-coverage periods [2, 5]. Weather comes from Open-Meteo: historical archive for training, current/7-day forecast for the dashboard. Temperature and precipitation are the useful features; cloud and wind did not improve the short test. Baden-Württemberg holidays are a feature and badge; they added little and are context, not a large driver [2].
| Sensor | Readings | Mean | Median | p95 | Max | Max daily gap |
|---|---:|---:|---:|---:|---:|---:|
@@ -108,7 +108,7 @@ The public app is at https://pulse.noelsabia.dev and the API at https://api-puls
![Figure 4. Plan screen.](figures/fig_plan.png)
*Figure 4. The plan screen: recommended shift blocks, coverage, estimated cost, and the “why this plan” context card. The plan is the product; the map and charts support it.*
*Figure 4. The v1.1 plan screen (reconstructed for print from the live UI): Saturday peak 5 staff, 100% coverage, €3,360 estimated labour cost, 25 h over / 0 h under. The live screen also includes a “why this plan” context card; the app is at https://pulse.noelsabia.dev.*
## 5. Evaluation
@@ -176,9 +176,9 @@ The main limitation is the measurement. The sensor samples ~10 seconds out of ev
Coverage is also a limitation. Eight sensors in 580 m × 280 m cannot support a city-wide heatmap or store-location recommender. Only 28.2% of 15-minute slots have all eight sensors; gaps are not random. The 28-day holdout is short, weather is observed, and there is no event log, POS, or labor-cost data. The deployment has one API replica, no SSO/HA, and no live ingestion; 15 min/1 h are replay/nowcast.
The privacy claim needs care. The app stores no MACs, and only counts leave the sensor. But the sensing stage processes link-layer identifiers at the edge; the 16-bit ID is a pseudonymous dedup key, not a cryptographic hash; passive MAC sensing in public space has a contested legal basis in Germany. The “privacy-preserving” label is architectural, not a formal guarantee. A production deployment needs a DPIA, a documented legal basis, minimizing/retention limits, and ideally a sensor that does not extract MACs at all.
**Privacy.** The app uses aggregate counts only, stores no MAC addresses or PII, and does not redistribute the raw challenge CSV. The sensing layer is upstream of this application. A production deployment would need a DPIA and a documented legal basis before collecting MAC-derived counts.
**What to keep:** decision-first framing, global model, time-based holdout, seasonal-naive baseline, transparent heuristic, cached fallback, build-time batch, honest limitations. **What to replace:** sensing (thermal/radar/camera/probe/manual), calibration (site-specific, with uncertainty), privacy (no raw MACs, central DP, k-threshold), spatial model (network-aware hierarchical field), forecast (quantile GBM, forecast weather, conformal calibration), platform (auth, observability, SLOs) — in that order. Fix the measurement before scaling the model.
**What to keep:** decision-first framing, global model, time-based holdout, seasonal-naive baseline, transparent heuristic, cached fallback, build-time batch, honest limitations. **What to replace:** sensing (thermal/radar/camera/probe/manual), calibration (site-specific, with uncertainty), privacy (no raw MAC retention, central DP, k-threshold), spatial model (network-aware hierarchical field), forecast (quantile GBM, forecast weather, conformal calibration), platform (auth, observability, SLOs) — in that order. Fix the measurement before scaling the model.
## 7. Related Work
@@ -190,9 +190,9 @@ PulseCast shows that a small, weather-aware global model can turn a noisy inner-
## Artifacts, data, and AI disclosure
The live app is https://pulse.noelsabia.dev (API: https://api-pulse.noelsabia.dev); the code repository is `[TODO]`. The raw challenge CSV is not redistributed. Derived aggregates, the model card, and the metrics JSON can be shared subject to the organizers’ permission. The app stores no MACs or PII; the sensing/legal caveats are in Sections 2.2 and 6. A production deployment needs a DPIA and a documented legal basis before collecting MAC-derived counts.
The live app is https://pulse.noelsabia.dev (API: https://api-pulse.noelsabia.dev); the code repository will be released after the hackathon. The raw challenge CSV is not redistributed. Derived aggregates, the model card, and the metrics JSON can be shared subject to the organizers’ permission. The app stores no MACs or PII; the sensing caveats are in Section 2.2 and the privacy box is in Section 6.
AI tools were used for drafting and editing. The authors verified every number, citation, and claim against the delivered data, the project metrics, or a cited source. AI tools are not authors and take no responsibility for the content.
AI tools were used for drafting and editing. The authors checked each number and citation; some sources are project documentation or estimates. AI tools are not authors and take no responsibility for the content.
## References
@@ -202,7 +202,7 @@ AI tools were used for drafting and editing. The authors verified every number,
[3] Code for Heilbronn. “Passantenzahlen messen mit LORA,” 18 September 2025. https://codeforheilbronn.de/blog/2025/09/passantenzahlen-messen-mit-lora/
[4] Code for Heilbronn. `lorax` / `sensor-pax` firmware and backend, 2026. https://codeberg.org/cfhn/lorax; upstream `ESP32-Paxcounter` and `libpax`, https://github.com/cyberman54/ESP32-Paxcounter and https://github.com/dbinfrago/libpax.
[4] Code for Heilbronn. `lorax` / `sensor-pax` firmware and backend, commit `e8be8bf5c11e1b76c88c3f176382c6df99eea989` (develop, 18 June 2026). https://codeberg.org/cfhn/lorax/commit/e8be8bf5c11e1b76c88c3f176382c6df99eea989; upstream `ESP32-Paxcounter` and `libpax`, https://github.com/cyberman54/ESP32-Paxcounter and https://github.com/dbinfrago/libpax.
[5] PulseCast data-quality analysis, `paper/research/07-data-quality.md`, 2026.
@@ -213,9 +213,3 @@ AI tools were used for drafting and editing. The authors verified every number,
[8] J. H. Friedman. “Greedy function approximation: a gradient boosting machine.” *Annals of Statistics* 29(5):1189–1232, 2001. DOI: 10.1214/aos/1013203451.
[9] L. F. Miranda-Moreno and A. C. Lahti. “Temporal trends and the effect of weather on pedestrian volumes: a case study of Montreal, Canada.” *Transportation Research Part D* 22:54–59, 2013. DOI: 10.1016/j.trd.2013.02.008.
[10] Bluetooth SIG. *Bluetooth Core Specification v5.3*, 2021. https://www.bluetooth.com/specifications/specs/core-specification-5-3/
[11] Court of Justice of the European Union. Case C-582/14, *Patrick Breyer v Bundesrepublik Deutschland*, 19 October 2016. https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=CELEX:62014CJ0582
[12] European Data Protection Board. *Guidelines 02/2023 on the Technical Scope of Article 5(3) of the ePrivacy Directive*, 2023. https://www.edpb.europa.eu/documents/guideline/guidelines-22023-on-technical-scope-of-art-53-of-eprivacy-directive_en