Scenarios & evidence

Eighteen 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.

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 experimental DTX
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

Observe without recording the conversation

RideWeave 0.2.1 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.

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

A requirement mapped to a test is not itself a passing execution. Historical results apply to their recorded revisions. The documentation describes current implementation; cited software evidence does not qualify later radio behavior.

Deliberate boundaries

iOS, hotspot fallback, NAN Pairing interoperability, remote member eviction, and global authenticated termination are unimplemented. Moving-group range and reliability, screen-off survival, helmet acoustic quality, and battery duration are not qualified. Members share source keys. Parent coordination rejects known cycles but is not distributed consensus. DTX is optional and defaults off.