IF-11 · Mobile/web interface

Mobility demand, quote, assignment, pickup and trip lifecycle

Preserve revisions and authority across rider, driver, orchestration, vehicle and support surfaces.

Name the source—and name what it cannot prove.

The same message can be observation, projection, plan, receipt or physical evidence. This contract keeps those meanings separate.

Authority

Mobility orchestration owns quote, booking and trip state; driver and rider apps supply scoped receipts; physical pickup requires matched evidence.

Degraded behavior

Expired quote, stale assignment, pickup mismatch, offline journal conflict or driver decline remains explicit and recoverable.

Outcome boundary

Quote is not booking; offer is not acceptance; arrival is not pickup; completion is not payment or customer satisfaction.

Producer and consumer responsibilities are explicit.

A product can appear on both sides when it transforms one authority into another; each transformation retains its own evidence.

Choose transport after semantics are fixed.

The program can select one or more transports without changing the source authority or failure contract.

Rider and driver APIsAssignment event streamPush notificationOffline execution journal

Compatibility vector

  • schema or ABI version
  • producer release
  • consumer release
  • policy and entitlement revision
  • content/configuration revision
  • territory/platform profile

Acceptance evidence

  • contract compatibility
  • nominal and negative scenarios
  • ordering, replay and idempotency
  • latency, capacity and resource bounds
  • security, privacy and role enforcement
  • offline, recovery and rollback
  • target or operational acceptance
OEM program workshop

Freeze the Mobility demand, quote, assignment, pickup and trip lifecycle contract before integration.

Allocate owners, transport, schema, releases, policy, content, degradation, replay and target acceptance in one controlled baseline.