# DPS-001.2 — Movement Telemetry

## Purpose

Collect basic design telemetry to support movement tuning.

This is not player surveillance.  
It is prototype design feedback.

---

## Required Telemetry Events

### movement_session_started

Fields:

- timestamp
- build_version
- scene_id

### movement_state_changed

Fields:

- from_state
- to_state
- timestamp
- velocity_x
- velocity_y
- grounded

### jump_performed

Fields:

- timestamp
- grounded
- used_coyote_time
- used_jump_buffer
- velocity_x
- velocity_y

### dash_performed

Fields:

- timestamp
- grounded
- facing
- velocity_before
- velocity_after
- air_dash_used

### landing_performed

Fields:

- timestamp
- fall_duration_ms
- velocity_x_on_land
- velocity_y_on_land
- continued_horizontal_input

### movement_chain_completed

Fields:

- chain
- duration_ms
- max_speed
- air_time_ms

---

## Required Aggregates

Write summary to:

```text
production/status/movement-telemetry-summary.json
```

With:

- total_jumps
- total_dashes
- average_speed
- max_speed
- average_air_time
- average_chain_length
- hard_stops_after_landing
- dash_usage_per_minute

---

## Privacy

No personal data.

No external analytics.

All telemetry stays local in the repository during prototype development.