The private Lemonade runtime

Current runtime path

The Windows core uses a private pinned Embeddable Lemonade instance. Electron’s main process owns its configuration, data directory, credentials, loopback port and process tree. The sandboxed renderer communicates through a narrow preload bridge; it does not receive the runtime key or directly fetch the inference endpoint.

The qualified release uses Lemonade 2026.42.1. Its bundled CUDA archive is labeled b11395, while the executable reports b11394-bf79dbbcd. Record archive identity and engine-reported identity separately; an archive name is not an independently verified source revision.

Lifecycle and ownership

app initialization → private service ready
  → explicit model load → generation → stop/completion
  → explicit unload → app close → owned service stopped

Ready, loaded and generating are different states. An installed backend is not a loaded model. The native host serializes mutations and tracks the active generation. Closing the application stops only its owned service, and tests check that its private endpoint refuses connections afterward.

A user-managed shared Lemonade instance would require a different ownership contract. RegesARC must not terminate it as a recovery shortcut. Current qualification does not make that shared-service mode a supported native option.

Protected settings

The runtime adapter binds the selected local path, exact context and explicit GPU layers. The qualified path disables automatic fit, preserving requested context. Credentials, ports, model paths and ownership flags must not be overridden by an unreviewed arbitrary-arguments field.

Lemonade upstream exposes broader inference and management capabilities. Those capabilities do not automatically become supported RegesARC APIs. In particular, an upstream internal cancellation flag does not prove that a public model-load request can be canceled safely. Generation Stop has been exercised; a native Cancel load control has not.

Extension boundary

An executable override for a registered backend is not a universal plugin interface. No claim is made that Strata is already a Lemonade recipe or that this native baseline uses Strata. The development branch adds a separate private JSONL Strata adapter under native qualification; it must independently pass protocol, ownership, context, cancellation and correctness gates for the exact artifact.

Primary references: Lemonade documentation, official source, and the pinned backend implementation.