entitlement required · C++ + JSON

Automotive release-manifest starter

A protected-artifact-neutral release skeleton for runtime/data/configuration/voice compatibility, qualification, atomic switch, and rollback.

Download project Follow the quickstart

Inside the archive

A project you can inspect before installing.

The canonical file manifest is also the archive contract. Common evidence, environment, manifest, and acceptance files accompany platform-specific source.

README.mdSetup and first-success boundary

STARTER_MANIFEST.jsonMachine-readable project scope

.env.exampleBlank non-secret configuration

EVIDENCE.mdSource and selection boundary

ACCEPTANCE.mdSuccess and hostile-path proof

release-manifest.example.jsonCompatible release unit

src/release_controller.hppAtomic update contract

QUALIFICATION.mdVehicle and interruption matrix

Automotive release-manifest starter

{
  "schemaVersion": "mappls.starter-kit.v1",
  "slug": "automotive-navigation-starter",
  "platform": "Automotive",
  "quickstartSlug": "automotive-navigation",
  "readiness": "entitlement-required",
  "liveProviderCallsEnabled": false,
  "sourceGuideSlugs": [],
  "credentialRule": "Blank environment placeholders only; enable a live adapter only after account, package, host, auth, region, and entitlement review."
}

Credential boundary

Secrets have one owner.

Provision per-device identity, activation, regions, runtime, and map data through the approved vehicle/fleet control plane. Avoid shared embedded credentials.

Evidence boundary

Source before syntax.

The public snapshot does not establish an automotive SDK or safety contract. Obtain the entitled runtime, data, activation, vehicle-interface, HMI, and regulatory requirements before binding an adapter.

This platform requires an entitled or company-selected distribution before live binding.

Release evidence

What must be true after the scaffold.

The session recovers to a safe explainable state with compatible runtime/data and never presents stale guidance as current after a reset.

A blocked, missing, or unentitled provider produces a useful explicit failure rather than a blank surface or fabricated result.

No server credential, bearer value, precise private fixture, or provider response body appears in client bundles, logs, screenshots, or test artifacts.

Resources, listeners, sessions, processes, or requests stop cleanly when the owning screen, request, or application ends.

Driver-distraction rules are testable

Power/connectivity recovery is proven

Runtime and data roll out together

Simulation precedes road evidence