01 · Organizer creates a ride and begins discovery

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

One-second advertisements/root pulses; platform attach callbacks are asynchronous.

Resource lifetime

Identity/preferences persist. Ride token, roster and discovery session are ephemeral; new ride receives new namespace.

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 ride namespace.

Evidence boundary

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