Preserve technical failure classes without leaking paths, prompts, credentials, or private environment data.
Failure classes
Separate path/root, identity, GGUF parse, architecture, tokenizer, tensor binding, memory, backend probe, selection, model load, generation, cancellation, and disposal.
Display-safe details
Show stable codes, a bounded human message, operation stage, recoverable action, and evidence state. Keep stack traces and private paths out of public UI.
No weakening retries
Never respond to verification failure by disabling hash, size, root, or reparse checks. Require a new reviewed intake record.
Operator evidence
Retain full diagnostic chains locally under an application privacy policy while exporting a path-free review record.
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
- An error message should not claim the model is globally unsupported.
- Suppressing an exception is not recovery.
Operational boundary
What this page covers: Preserve technical failure classes without leaking paths, prompts, credentials, or private environment data.
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