MapplsAutoBuild your program
IF-10 · Cloud interface

Program identity, credential and entitlement

Bind organization, program, vehicle line, application, device, user, environment, territory, product and quota rights.

Allocate this contract →All interfaces →
Authority model

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

The developer and entitlement control plane owns effective rights; product services enforce those exact rights independently.

Degraded behavior

Unknown environment, territory, platform, role or product fails closed; one-time credential material is never persisted in public evidence.

Outcome boundary

An entitlement request, credential issue or conformance result does not imply production promotion or customer acceptance.

Product allocation

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.

Producers

SAAS-10Automotive Developer & Entitlement CloudSaaS & cloudAPP-09Automotive Developer ConsoleNative application
versioned→fail-closed

Consumers

SAAS-01Connected Vehicle CloudSaaS & cloudSAAS-02InTouch & Fleet Control TowerSaaS & cloudSAAS-03RouteNet OptimizationSaaS & cloudSAAS-04Map & Content CloudSaaS & cloudSAAS-05EV Journey & Charging CloudSaaS & cloudSAAS-06eHorizon & HD Map CloudSaaS & cloudSAAS-07Mobility Orchestration PlatformSaaS & cloudSAAS-08Geoanalytics & Command CenterSaaS & cloudSAAS-09AI Cockpit Orchestration CloudSaaS & cloudSAAS-11Charging Intelligence OperationsSaaS & cloudAPP-01Embedded NavigationNative applicationAPP-02OEM Owner CompanionNative applicationAPP-03EV Cockpit & CompanionNative applicationAPP-04AI Cockpit AssistantNative applicationAPP-05Fleet & Operations PortalNative applicationAPP-06Driver & Field ExecutionNative applicationAPP-07Rider & Passenger AppNative applicationAPP-08Dealer, Service & RoadsideNative applicationFW-04Connectivity & Telemetry AgentEmbedded softwareFW-05Content & Map Update ManagerEmbedded softwareFW-06Device Lifecycle & OTA AgentEmbedded software
Transport allocation

Choose transport after semantics are fixed.

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

OAuth/OIDC or entitled authService and device credentialsEntitlement API and signed artifact metadata

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 Program identity, credential and entitlement contract before integration.

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

Build your program Open developer hub ↗