Display backend package, registration, declarations, probes, selection, fallback, and execution as separate states.
Registration
A registration package can make a backend factory and declarations available. This state is narrower than local compatibility.
Probe
A local probe inspects the current environment and returns diagnostics. Preserve unavailable, failed, and indeterminate states rather than converting them to a generic unsupported badge.
Selection
Apply an explicit allowlist and policy. Record why a lane was selected or rejected.
Fallback
If CPU fallback is allowed, make the lane change visible before execution and retain it in evidence. If fail-closed is required, stop rather than changing lanes silently.
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
- Registration does not prove inference.
- Compatibility declarations do not prove device probing.
Operational boundary
What this page covers: Display backend package, registration, declarations, probes, selection, fallback, and execution as separate states.
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