PROTOCOL NOTES / 12

01 · Organizer creates a ride and begins discovery

Participants: UI, Service, Engine, Aware

Implemented software · Physical qualification pending

Starting state

Local engine idle; persisted identity loaded; required platform permissions and Aware availability checked.

Ordered events

  1. UI → Service

    create with ride and rider names

  2. Service → Engine

    create validates names and resets previous ride

  3. Engine → Engine

    Generate ride ID and admission token; sign initial roster

  4. Engine → Aware

    transportConfig supplies service, passphrase and signed advertisement

  5. Aware → Service

    Attach and publish/subscribe callbacks update capability state

Fields and messages

create name/riderName; invitation v,ride,organizer,publicKey,token; advertisement root=0 and path=[0].

Authorization and invariants

Persistent identity signs roster/discovery; token stays native. Creating a ride never starts microphone capture.

Timers

Root pulse advances each second; advertisement refresh 1 s while the topology is unsettled, 3 s when settled, immediately on route-shape change; platform attach callbacks are asynchronous.

Resource lifetime

Identity/preferences persist. Ride token, roster and discovery session are ephemeral; a new ride receives a new ride tag, passphrase and advertisement under the same fixed service name.

What the rider sees

Lobby shows organizer, pending membership and native invitation actions.

Failure branches

Unavailable Aware/permissions produces explicit capability or permission guidance. Failed attach cannot be reported as an installed data path.

Resulting state

Organizer is lobby member index 0; invitation is available; discovery publishes the fixed service _rideweave._tcp with the signed advertisement (carrying the ride tag) sealed under a ride-token key.

Evidence boundary

Host engine/protocol tests and JVM capability policy; physical discovery remains unqualified.

← All scenarios

Authority: RWCP v2 reviewed scenario catalogue, scenario 01. Public examples are synthetic. This guide is maintained against the private implementation; it does not imply access to its source.