entitlement required · C++

Embedded Linux supervisor starter

A proprietary-runtime-neutral C++ seam with boot, health, degraded, stopped, and teardown states for entitled Linux distributions.

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

CMakeLists.txtDependency-neutral native build

src/runtime_adapter.hppEntitled runtime boundary

src/main.cppBounded fixture entrypoint

Embedded Linux supervisor starter

{
  "schemaVersion": "mappls.starter-kit.v1",
  "slug": "linux-embedded-starter",
  "platform": "Linux",
  "quickstartSlug": "linux-embedded",
  "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.

Use device/workload identity and entitlement delivered through the approved provisioning channel; never bake fleet-wide secrets into an image or package.

Evidence boundary

Source before syntax.

The public snapshot has no platform-specific Linux distribution guide. The runtime, ABI, compiler, graphics, activation, and data contract must come from the entitled private distribution.

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

Release evidence

What must be true after the scaffold.

Every test leaves exactly one bootable active runtime/data set and health reports the selected versions without leaking device credentials.

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.

Runtime/data compatibility is enforced

Activation can rotate

Updates are signed and reversible

Health survives process restart