PROTOCOL NOTES / 12

Scenarios & evidence

Follow complete scenarios and read evidence at the right level.

Android and iOS software implemented · Apple Wi-Fi Aware, Bluetooth LE and mixing tested on hosts and emulators only · Physical qualification pending

Twenty-two views of the same system

Each scenario connects the starting state, ordered events, ownership, failure branches, and evidence. Read them as worked examples alongside the explanatory chapters. Scenarios marked as tested on hosts and emulators only describe the Apple, Bluetooth LE and mixing extension, which has not yet run on physical phones.

  1. Organizer creates a ride and begins discovery
  2. Invitation import, discovery and first connection
  3. NDP through IPv6, TLS, greeting and hello
  4. Join approval, index assignment and signed roster
  5. Multiple direct and relayed admissions
  6. Admission closure, source descriptors and readiness
  7. Local helmet audio activation and first frame
  8. Single-hop and multi-hop authenticated media
  9. Silence, speaking, feedback and voice-activated transmission
  10. Graceful departure and organizer-local termination
  11. Network failure, half-open detection and repair
  12. Abrupt relay disappearance and descendant reconnection
  13. Partition, temporary root and later merge
  14. Parent improvement, handoff, abort, rollback and drain
  15. Duplicates, stale media, hop exhaustion and rejected membership
  16. Background operation, interruption, suspension and recovery
  17. Capacity exhaustion and break-before-make fallback
  18. Shared-NDI ownership and independent teardown
  19. Apple device joins over Wi-Fi Aware pairing and advert discovery · implemented software; host and emulator verification only
  20. Apple and Android bridged over BLE with mixing · implemented software; host and emulator verification only
  21. Android 10 leaf over a single BLE link · implemented software; host and emulator verification only
  22. Parent change from a BLE edge to Wi-Fi Aware with make-before-break · implemented software; host and emulator verification only

Observe without recording the conversation

RideWeave persists bounded local diagnostics for rides, failed join attempts, and headset checks. A background writer records events, periodic counters, and device measurements. Ordinary records exclude speech and packet content. Shared reports also omit names, ride labels, invitations, keys, and raw network addresses. Bluetooth LE and mixing records add link and mixer counters, never Bluetooth device identifiers or audio.

Correlation pseudonyms support comparison across phones within a ride; they are not an anonymity guarantee against someone who already knows the source identities. Quota eviction can remove detail while retaining summaries. Recorder gaps and missing observations must remain explicit instead of being filled with invented values.

Keep evidence at its actual level

EvidenceWhat it can establish
Deterministic hostState transitions, authorization and ownership invariants
TLS/UDP loopbackReal socket framing and software duplex behavior
JVM / Android emulatorAdapter policy, JNI, UI and lifecycle behavior
Spike measurementsBluetooth LE throughput, mixing cost and stack defects on specific phones: design input, not qualification
Physical phones and helmetsWi-Fi Aware and Bluetooth LE range, motion, wind acoustics, coexistence with headset calls, heat and battery: still requires qualification

A requirement mapped to a test is not itself a passing execution. A scenario tested on hosts and emulators only has no physical evidence. Recorded test results apply only to the revision they were run against. The documentation describes current implementation; cited software evidence does not qualify later radio behavior.

Deliberate boundaries

The Android and iOS apps are implemented. The Apple Wi-Fi Aware path, Bluetooth LE links and bridge mixing are implemented software tested on hosts, emulators and the iOS simulator only; Wi-Fi Aware between Apple and Android phones needs an Android phone with NAN Pairing. Hotspot fallback, remote member eviction, and global authenticated termination are unimplemented. Moving-group range and reliability, Bluetooth LE range, coexistence with headset calls, screen-off survival, helmet acoustic quality, mixed-speech quality, and battery duration are not qualified. Members share source keys, and a bridge re-encodes the voices of its side. Parent coordination rejects known cycles but is not distributed consensus. Voice-activated transmission is on by default and can be turned off; its acoustic quality is unqualified.

Authority: Scenario catalogue; diagnostics; human qualification. Public examples are synthetic. This guide is maintained against the private implementation; it does not imply access to its source.