Back to corpus
research noteexperiment writeup candidatescore 22

Mobile Client Specification - Episode 1

This document specifies requirements for mobile sensor clients (iOS/Android) that stream data to the Episode 1 host system via WebSocket.

Open full HTMLDownload HTMLCorpus JSONPaper schema

Full HTML reader

Read the full artifact

Open in new tab

Extracted abstract or opening context

This document specifies requirements for mobile sensor clients (iOS/Android) that stream data to the Episode 1 host system via WebSocket. | Sensor | Rate (Hz) | Priority | Notes | |--------|-----------|----------|-------| | Accelerometer | 100 | **Required** | Device acceleration (m/s²) | | Gyroscope | 100 | **Required** | Angular velocity (rad/s) | | Gravity | 100 | Recommended | Gravity vector (m/s²) | | Barometer | 10 | Optional | Atmospheric pressure (hPa) | | GPS/Location | 1 | Optional | Lat/lon/alt/speed/bearing | | Microphone RMS | 50 | Optional | Audio envelope (unitless) | **Accelerometer/Gyro:** - Use device coordinate system - X: Right - Y: Up - Z: Forward (out of screen) **Gravity:** - If available from device, send as-is - Otherwise, host will estimate via low-pass filter **Connection Flow:** 1. Client connects to WebSocket 2. Send first packet with `device_id` 3. Host acknowledges and begins logging 4. Stream packets continuously

Promotion decision

What has to happen next

Attach run IDs, datasets, metrics, and reproduction commands.

Why this is not always a full paper yet

Corpus pages are public-safe readers for discovered workspace artifacts. They are not automatically final papers. A corpus item becomes a polished paper only after the editable source, evidence checkpoints, references, figures, render path, and release status are attached through the paper schema.