Use executed-path records rather than package or hardware labels when presenting acceleration.
Managed CPU lane
The documented LocalEndpoint path selects the managed CPU lane represented by Backends.CpuManaged. Present this as the current explicit application path, not as a universal performance claim.
GPU packages
Treat GPU registration package identity as a dependency fact. Require probe, selection, model load, and inference evidence before presenting GPU execution.
Environment record
Retain OS, architecture, runtime framework, processor or adapter identity, driver/runtime information when applicable, and measurement method.
UI state
Use text labels for registered, probe pending, probe failed, available, selected, fallback active, and execution observed. Never rely on color alone.
Available now
- The public UAIX.LmRuntime package family and canonical package documentation.
- The host-facing workflow and evidence distinctions described on this page.
Host responsibilities
- Select and trust inputs, define policy and limits, integrate the UI or service, retain application evidence, and test the exact deployment.
Not claimed
- A detected device is not an executed adapter.
- No platform support claim is made without a tested build.
Operational boundary
What this page covers: Use executed-path records rather than package or hardware labels when presenting acceleration.
Available now: The documented package surfaces and this host-facing guidance are public.
Host responsibility: Own acquisition, trust, configuration, presentation, persistence, transport, policy, tests, and deployment.
Not claimed: Universal compatibility, production certification, safety certification, hidden fallbacks, or behavior beyond retained evidence.
Canonical sources: Canonical package documentation · Current release metadata
Last reviewed UTC:
Source and review record
Prerequisites
- Read Get Started
- Review host/runtime boundaries