Sample apps/Advanced

Offline Release Control

Operate an entitled offline or automotive runtime as one compatible, dual-slot release across manufacture, activation, installation, qualification, update, interruption, rollback, and retirement.

JourneyAdvanced
Manufacture → activate → install → qualify → update → recover → retire
Node.jsResponsive fleet release UIA/B slot controllerManifest and qualification ledger

A small app with production bones.

The download separates browser experience, command API, Mappls adapter, aggregate state, audit history, transactional outbox, fixtures, tests, and deployment guidance.

01Experience
02Mappls adapter
03Journey state
04Events + recovery
05Observability

Implemented and verified.

22 implemented capabilitiesResponsive fleet release console · Public and local evidence-generation separation · No runtime, map package, binary, license, activation key, credential, or URL input · Non-secret entitlement evidence · Runtime/data/configuration/voice manifest unit · Exact CPU/ABI/OS/graphics compatibility · SHA-256 manifest and component identities · Independent signature and observed-digest attestations · Dual-slot active and known-good invariants · Download, verify, stage, switch, and qualify checkpoints · Seven-lane deterministic qualification suite · Power-loss recovery before atomic switch · Power-loss rollback after switch · Post-qualification regression rollback · Activation expiry and offline-grace gate · Retirement without history deletion · Idempotent commands · Optimistic concurrency · Append-only audit events · Transactional outbox · Atomic restart recovery · Credential-free fixture mode
Browser application

A responsive operations console backed by the included JSON API.

Durable domain

Aggregate snapshots, audit events, idempotency records, evidence, and outbox entries are committed together.

Fixture adapter

A credential-safe provider boundary aligned to named Mappls endpoint contracts.

Executable tests

10 tests covering lifecycle, HTTP, replay, conflicts, domain recovery, and restart behavior.

Architecture notes

Trust boundaries, aggregate invariants, adapter ownership, evidence lineage, and recovery design.

Deployment guide

Database, identity, secrets, outbox, privacy, observability, migration, and rollback work.